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
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
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
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
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 select our
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
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 uses
On Tue, Dec 13, 2011 at 12:36 PM, Joshua Lock j...@linux.intel.com 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,
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 a
On Tue, Dec 13, 2011 at 2:36 PM, Richard Purdie
richard.pur...@linuxfoundation.org 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
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
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
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
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
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
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 je...@jefro.net 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
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
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
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
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 against
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
22 matches
Mail list logo
