I built the "crownbay" (not crownbay-noemgd) image as outlined in the
E660 development kit (link
http://www.yoctoproject.org/download/bsp/intel-atom-processor-e660-intel-platform-controller-hub-eg20t-development-kit-1)
I used poky-edison-6.0.tar.bz2 and crownbay-edison-6.0.0.tar.bz2 and
followed t
On Tue, 2011-12-13 at 11:13 -0500, autif khan wrote:
> I built the "crownbay" (not crownbay-noemgd) image as outlined in the
> E660 development kit (link
> http://www.yoctoproject.org/download/bsp/intel-atom-processor-e660-intel-platform-controller-hub-eg20t-development-kit-1)
>
> I used poky-edis
I think that I did. Included is an excerpt that says that I need not
do anything except bitbake core image sato when MACHINE="crownbay".
As instructed, I followed the steps in section one (Building the
meta-crownbay BSP layer) and ignored everything in section two
(Special notes for building the m
On Tue, 2011-12-13 at 08:13 -0800, autif khan wrote:
> I built the "crownbay" (not crownbay-noemgd) image as outlined in the
> E660 development kit (link
> http://www.yoctoproject.org/download/bsp/intel-atom-processor-e660-intel-platform-controller-hub-eg20t-development-kit-1)
>
> I used poky-edis
On Tue, 2011-12-13 at 11:37 -0500, autif khan wrote:
> I think that I did. Included is an excerpt that says that I need not
> do anything except bitbake core image sato when MACHINE="crownbay".
>
> As instructed, I followed the steps in section one (Building the
> meta-crownbay BSP layer) and igno
Attendees:
Sean, Beth, Tom, Richard, Darren, Bruce, Dave, Joshua, Mark, ScottR, Saul
New Action Item List:
* Action item Review - 5 min
1. Mark will review unsorted features from Wind River team and try to
have them scheduled (WIP)
Focus of the current week:
M1 Stabilization, M2 Planning
On 11/12/11 21:20, Sathishkumar Duraisamy wrote:
> Hi,
>
> Today, I tried to reproduce the problem and magically, today, hob
> works as expected. So, I started once again with new config, and
> again I tried to reproduce the problem. But the problem exists.
>
> The reason for this, once we selec
I'm trying to wrap up my work on meta-tiny and integrate it into poky
proper. I'm having some difficulty drawing a line between the
responsibility of the distro definition versus that of the image definition.
For example, if I define a distro which uses tmpdevfs (no udev or mdev)
and specifies KMA
On 13/12/11 12:23, Darren Hart wrote:
> I'm trying to wrap up my work on meta-tiny and integrate it into poky
> proper. I'm having some difficulty drawing a line between the
> responsibility of the distro definition versus that of the image definition.
>
> For example, if I define a distro which u
On Tue, Dec 13, 2011 at 12:36 PM, Joshua Lock wrote:
>
>> As for images, I might be able to reuse core-image-minimal - but it
>> oddly contains "${POKY_EXTRA_INSTALL}" in the IMAGE_INSTALL. Since
>> core-image-minimal.bb is defined in oe-core and POKY is a distro notion
>> of meta-yocto, this cont
On Tue, 2011-12-13 at 12:23 -0800, Darren Hart wrote:
> I'm trying to wrap up my work on meta-tiny and integrate it into poky
> proper. I'm having some difficulty drawing a line between the
> responsibility of the distro definition versus that of the image definition.
>
> For example, if I define
On Tue, Dec 13, 2011 at 2:36 PM, Richard Purdie
wrote:
> Not all images can be built with a given distro, our base config is
> rather ride ranging though for obvious reasons. You could "enforce" this
> by adding some anonymous python to the distro which does something like:
>
> if inherits("image"
Hi,
I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
Darren told that it was fixed and merged to master.
I wanted to bring to the list about this error message.
ERROR: Function 'do_kernel_configme' failed (see
/usr/local/src/yocto_1_1_release/poky/build1/tmp/work/crys
I'm still very new and very clueless but I humbly submit what looks like a bug
to me..
"routerstationpro.conf" in meta-yocto/conf/machine/ lists machine features the
hardware does not have.
http://www.ubnt.com/wiki/RouterStation_Pro lists the hardware specs and it
lacks a display adapter (henc
On 11-12-13 5:50 PM, Bodke, Kishore K wrote:
Hi,
I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
Darren told that it was fixed and merged to master.
This shouldn't be happening on edison at all. The changes to the
kernel recipes/tools to use the merge_config.sh sho
On 12/13/2011 03:05 PM, Bruce Ashfield wrote:
> On 11-12-13 5:50 PM, Bodke, Kishore K wrote:
>> Hi,
>>
>> I get failure for the linux-yoctort_3.0.bb file for the poky Edison branch.
>>
>> Darren told that it was fixed and merged to master.
>
> This shouldn't be happening on edison at all. The chan
Yeah. I am using local bare clone for the linux-yocto-3.0 and using
poky-extras/meta-kernel-dev in my bblayers.conf for my build.
Sorry for not mentioning this before.
Thanks
Kishore.
-Original Message-
From: Hart, Darren
Sent: Tuesday, December 13, 2011 3:15 PM
To: Bruce Ashfield
Cc:
On 11-12-13 6:17 PM, Bodke, Kishore K wrote:
Yeah. I am using local bare clone for the linux-yocto-3.0 and using
poky-extras/meta-kernel-dev in my bblayers.conf for my build.
Sorry for not mentioning this before.
Aha. This is completely different then. As Darren mentioned, the bbappend
should
Yes.
Its with poky Edison with poky-extras/meta-kernel-dev master branch I am using
for my build.
Thanks
Kishore.
-Original Message-
From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com]
Sent: Tuesday, December 13, 2011 3:25 PM
To: Bodke, Kishore K
Cc: Hart, Darren; yocto@yoctopro
On 11-12-13 6:05 PM, David Smoot wrote:
I'm still very new and very clueless but I humbly submit what looks like
a bug to me..
"routerstationpro.conf" in meta-yocto/conf/machine/ lists machine
features the hardware does not have.
http://www.ubnt.com/wiki/RouterStation_Pro lists the hardware spe
We currently build at least some MACHINES with 2.6.37 of
linux-libc-headers. This can cause problems for newer packages (such as
connman) that expect more recent headers (if_alg.h is missing prior to
2.6.39). While the proper fix is to ensure these packages can cope with
older headers, for MACHINES
On 11-12-13 6:33 PM, Darren Hart wrote:
We currently build at least some MACHINES with 2.6.37 of
linux-libc-headers. This can cause problems for newer packages (such as
connman) that expect more recent headers (if_alg.h is missing prior to
2.6.39). While the proper fix is to ensure these packages
On 12/13/2011 03:41 PM, Bruce Ashfield wrote:
> On 11-12-13 6:33 PM, Darren Hart wrote:
>> We currently build at least some MACHINES with 2.6.37 of
>> linux-libc-headers. This can cause problems for newer packages (such as
>> connman) that expect more recent headers (if_alg.h is missing prior to
We hit another lock-step SRCREV bug earlier on the FRI2 BSP. This was
due mostly to my pushing the efi changes to meta-intel too early - but,
it highlights a maintenance step that I believe could be eliminated for
most boards.
We have a yocto/standard/fri2 branch, but it doesn't contain any
additi
Only 2 more days left to respond if you haven't, and then I'll quit bugging
you. :)
On Sat, Dec 3, 2011 at 10:10 AM, Jeff Osier-Mixon wrote:
> Hi Yoctoids - if you have a spare 2 minutes, we would really appreciate it
> if you would fill out a short end-of-year survey for the project. This will
On 11-12-13 6:26 PM, Bodke, Kishore K wrote:
Yes.
Its with poky Edison with poky-extras/meta-kernel-dev master branch I am using
for my build.
This is likely the problem. I use and test meta-kernel-dev everyday,
but that's always against master. I keep them in lockstep, since
meta-kernel-dev n
On 11-12-13 6:43 PM, Darren Hart wrote:
On 12/13/2011 03:41 PM, Bruce Ashfield wrote:
On 11-12-13 6:33 PM, Darren Hart wrote:
We currently build at least some MACHINES with 2.6.37 of
linux-libc-headers. This can cause problems for newer packages (such as
connman) that expect more recent heade
On 11-12-13 6:46 PM, Darren Hart wrote:
We hit another lock-step SRCREV bug earlier on the FRI2 BSP. This was
due mostly to my pushing the efi changes to meta-intel too early - but,
it highlights a maintenance step that I believe could be eliminated for
most boards.
We have a yocto/standard/fri2
On 12/13/2011 09:13 PM, Bruce Ashfield wrote:
> On 11-12-13 6:26 PM, Bodke, Kishore K wrote:
>> Yes.
>> Its with poky Edison with poky-extras/meta-kernel-dev master branch I am
>> using for my build.
>
> This is likely the problem. I use and test meta-kernel-dev everyday,
> but that's always agai
On 12/13/2011 09:27 PM, Bruce Ashfield wrote:
> On 11-12-13 6:46 PM, Darren Hart wrote:
>> We hit another lock-step SRCREV bug earlier on the FRI2 BSP. This was
>> due mostly to my pushing the efi changes to meta-intel too early - but,
>> it highlights a maintenance step that I believe could be e
30 matches
Mail list logo
