|
I've been using the Intel meta-cedartrail layer with Danny 8.0.1. Is this
layer likely to be unusable with Dylan 9.0? Or unusable without lots of
tinkering that's probably beyond my abilities?
And if I were to try Dylan, is it best to start from scratch, in a
completely new directory?
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@...
|
|
|
Tom Zanussi <tom.zanussi@...>
On Mon, 2013-06-17 at 16:56 -0700, Paul D. DeRocco wrote: I've been using the Intel meta-cedartrail layer with Danny 8.0.1. Is this
layer likely to be unusable with Dylan 9.0? Or unusable without lots of
tinkering that's probably beyond my abilities?
And if I were to try Dylan, is it best to start from scratch, in a
completely new directory?
Hi, I believe the main problem would be the graphics driver - it would need porting to the 3.8 kernel - the rest would probably be straightforward. The cedartrail BSP was discontinued following danny, but I'm cc:ing the maintainers in case they might have any further input. I was thinking of creating a meta-intel/staging area for things like this i.e. discontinued BSPs that people are still using, which would contain best-effort updates but completely without promise of any kind of support. If there's enough interest, and there seems to be judging from the number of questions about cedartrail we continue to keep getting, I'll try to find some free time to take a stab at moving it to dylan... Thanks, Tom
|
|
|
From: Tom Zanussi
I believe the main problem would be the graphics driver - it
would need
porting to the 3.8 kernel - the rest would probably be
straightforward.
The cedartrail BSP was discontinued following danny, but I'm
cc:ing the maintainers in case they might have any further input. Is this graphics issue likely to be a problem if I'm making the non-graphics image? My app is headless. -- Ciao, Paul D. DeRocco Paul mailto:pderocco@...
|
|
|
Tom Zanussi <tom.zanussi@...>
On Tue, 2013-06-18 at 09:17 -0700, Paul D. DeRocco wrote: From: Tom Zanussi
I believe the main problem would be the graphics driver - it
would need
porting to the 3.8 kernel - the rest would probably be
straightforward.
The cedartrail BSP was discontinued following danny, but I'm
cc:ing the maintainers in case they might have any further input. Is this graphics issue likely to be a problem if I'm making the non-graphics
image? My app is headless.
I wouldn't think so - my guess would be that the -nopvr wouldn't be a problem. Tom
|
|
|
Hi Tom, On 18 Jun 2013, at 15:04, Tom Zanussi wrote: On Mon, 2013-06-17 at 16:56 -0700, Paul D. DeRocco wrote:
I've been using the Intel meta-cedartrail layer with Danny 8.0.1. Is this
layer likely to be unusable with Dylan 9.0? Or unusable without lots of
tinkering that's probably beyond my abilities?
And if I were to try Dylan, is it best to start from scratch, in a
completely new directory?
Hi,
I believe the main problem would be the graphics driver - it would need
porting to the 3.8 kernel - the rest would probably be straightforward.
The cedartrail BSP was discontinued following danny, but I'm cc:ing the
maintainers in case they might have any further input.
I was thinking of creating a meta-intel/staging area for things like
this i.e. discontinued BSPs that people are still using, which would
contain best-effort updates but completely without promise of any kind
of support. If there's enough interest, and there seems to be judging
from the number of questions about cedartrail we continue to keep
getting, I'll try to find some free time to take a stab at moving it to
dylan... I'm certainly interested and happy to help out if I can. I also see that ASRock are now making a board ( http://www.asrock.com/IPC/overview.asp?Model=DN2800MT) that looks exactly the same as the Intel one with the same name aimed at signage and thin-client applications, so hardware will be about for a good few years yet, Thanks,
Tom
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto Chris Tapp opensource@... www.keylevel.com
|
|
|
Tom Zanussi <tom.zanussi@...>
On Tue, 2013-06-18 at 20:50 +0100, Chris Tapp wrote: Hi Tom,
On 18 Jun 2013, at 15:04, Tom Zanussi wrote:
On Mon, 2013-06-17 at 16:56 -0700, Paul D. DeRocco wrote:
I've been using the Intel meta-cedartrail layer with Danny 8.0.1. Is this
layer likely to be unusable with Dylan 9.0? Or unusable without lots of
tinkering that's probably beyond my abilities?
And if I were to try Dylan, is it best to start from scratch, in a
completely new directory?
Hi,
I believe the main problem would be the graphics driver - it would need
porting to the 3.8 kernel - the rest would probably be straightforward.
The cedartrail BSP was discontinued following danny, but I'm cc:ing the
maintainers in case they might have any further input.
I was thinking of creating a meta-intel/staging area for things like
this i.e. discontinued BSPs that people are still using, which would
contain best-effort updates but completely without promise of any kind
of support. If there's enough interest, and there seems to be judging
from the number of questions about cedartrail we continue to keep
getting, I'll try to find some free time to take a stab at moving it to
dylan... I'm certainly interested and happy to help out if I can.
I also see that ASRock are now making a board (http://www.asrock.com/IPC/overview.asp?Model=DN2800MT) that looks exactly the same as the Intel one with the same name aimed at signage and thin-client applications, so hardware will be about for a good few years yet,
OK, good to know. The only Cedar Trail hardware I have access to is the Acer Aspire One I have here - let me see if I can get something going on that... Tom Thanks,
Tom
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto Chris Tapp
opensource@...
www.keylevel.com
|
|
|
From: Tom Zanussi
On Tue, 2013-06-18 at 20:50 +0100, Chris Tapp wrote:
Hi Tom,
On 18 Jun 2013, at 15:04, Tom Zanussi wrote:
On Mon, 2013-06-17 at 16:56 -0700, Paul D. DeRocco wrote:
I've been using the Intel meta-cedartrail layer with Danny 8.0.1. Is this
layer likely to be unusable with Dylan 9.0? Or unusable
without lots of
tinkering that's probably beyond my abilities?
And if I were to try Dylan, is it best to start from
scratch, in a
completely new directory?
Hi,
I believe the main problem would be the graphics driver -
it would need
porting to the 3.8 kernel - the rest would probably be
straightforward.
The cedartrail BSP was discontinued following danny, but
I'm cc:ing the
maintainers in case they might have any further input.
I was thinking of creating a meta-intel/staging area for
things like
this i.e. discontinued BSPs that people are still using,
which would
contain best-effort updates but completely without
promise of any kind
of support. If there's enough interest, and there seems
to be judging
from the number of questions about cedartrail we continue to keep
getting, I'll try to find some free time to take a stab
at moving it to
dylan... I'm certainly interested and happy to help out if I can.
I also see that ASRock are now making a board
(http://www.asrock.com/IPC/overview.asp?Model=DN2800MT) that
looks exactly the same as the Intel one with the same name
aimed at signage and thin-client applications, so hardware
will be about for a good few years yet,
OK, good to know. The only Cedar Trail hardware I have
access to is the
Acer Aspire One I have here - let me see if I can get
something going on
that... My first attempt to build cedartrail-nopvr finds that meta-intel has an unmatched mesa_9.1.3.bbappend, but I suppose I can configure it to ignore that since I'm not building graphics. However, meta-cedartrail contains an unmatched linux-yocto_3.0.bbappend and linux-yocto-rt_3.0.bbappend. I don't know how to fix that. -- Ciao, Paul D. DeRocco Paul mailto:pderocco@...
|
|
|
Tom Zanussi <tom.zanussi@...>
On Wed, 2013-06-19 at 16:09 -0700, Paul D. DeRocco wrote: From: Tom Zanussi
On Tue, 2013-06-18 at 20:50 +0100, Chris Tapp wrote:
Hi Tom,
On 18 Jun 2013, at 15:04, Tom Zanussi wrote:
On Mon, 2013-06-17 at 16:56 -0700, Paul D. DeRocco wrote:
I've been using the Intel meta-cedartrail layer with Danny 8.0.1. Is this
layer likely to be unusable with Dylan 9.0? Or unusable
without lots of
tinkering that's probably beyond my abilities?
And if I were to try Dylan, is it best to start from
scratch, in a
completely new directory?
Hi,
I believe the main problem would be the graphics driver -
it would need
porting to the 3.8 kernel - the rest would probably be
straightforward.
The cedartrail BSP was discontinued following danny, but
I'm cc:ing the
maintainers in case they might have any further input.
I was thinking of creating a meta-intel/staging area for
things like
this i.e. discontinued BSPs that people are still using,
which would
contain best-effort updates but completely without
promise of any kind
of support. If there's enough interest, and there seems
to be judging
from the number of questions about cedartrail we continue to keep
getting, I'll try to find some free time to take a stab
at moving it to
dylan... I'm certainly interested and happy to help out if I can.
I also see that ASRock are now making a board
(http://www.asrock.com/IPC/overview.asp?Model=DN2800MT) that
looks exactly the same as the Intel one with the same name
aimed at signage and thin-client applications, so hardware
will be about for a good few years yet,
OK, good to know. The only Cedar Trail hardware I have
access to is the
Acer Aspire One I have here - let me see if I can get
something going on
that... My first attempt to build cedartrail-nopvr finds that meta-intel has an
unmatched mesa_9.1.3.bbappend, but I suppose I can configure it to ignore
that since I'm not building graphics. However, meta-cedartrail contains an
unmatched linux-yocto_3.0.bbappend and linux-yocto-rt_3.0.bbappend. I don't
know how to fix that.
You should just be able to delete those 3.0 .bbappends - they're of no use at this point. I actually used yocto-bsp to create a brand new cedartrail BSP, called meta-cdt, with just a vesa graphics machine called 'cdt-vesa': http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=tzanussi/meta-cdt-v0It built fine here, but it wouldn't boot on my Aspire One, but I couldn't boot either of the official 'danny' cedartrail (cedartrail and cedartrail-nopvr) images I built either. I'd be curious if the meta-cdt layer would work for you, though. Tom
|
|
|
From: Tom Zanussi
I actually used yocto-bsp to create a brand new cedartrail BSP, called
meta-cdt, with just a vesa graphics machine called 'cdt-vesa':
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=tzanussi/meta-cdt-v0
It built fine here, but it wouldn't boot on my Aspire One, but I
couldn't boot either of the official 'danny' cedartrail
(cedartrail and
cedartrail-nopvr) images I built either.
I'd be curious if the meta-cdt layer would work for you, though.
This builds and boots fine on an Intel DN2800MT. Now to start modifying it, and seeing what happens. -- Ciao, Paul D. DeRocco Paul mailto:pderocco@...
|
|
|
Tom Zanussi <tom.zanussi@...>
On Thu, 2013-06-20 at 10:26 -0700, Paul D. DeRocco wrote: From: Tom Zanussi
I actually used yocto-bsp to create a brand new cedartrail BSP, called
meta-cdt, with just a vesa graphics machine called 'cdt-vesa':
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel-contrib/log/?h=tzanussi
/meta-cdt-v0
It built fine here, but it wouldn't boot on my Aspire One, but I
couldn't boot either of the official 'danny' cedartrail
(cedartrail and
cedartrail-nopvr) images I built either.
I'd be curious if the meta-cdt layer would work for you, though.
This builds and boots fine on an Intel DN2800MT. Now to start modifying it,
and seeing what happens.
Great, glad to hear it! Now I need to figure out what's going on with the Aspire One, now that I know it should work.. Thanks, Tom
|
|
|
