What does "ls /home/chris/yocto/ebox3300-build/tmp/deploy/ipk" say? Cheers, Richard

chris@ubuntu:~/yocto/ebox3300-build$ bitbake -e |grep "PACKAGE_ARCHS" # PACKAGE_ARCHS=all any noarch ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH} PACKAGE_ARCHS="all any noarch x86 Vortex86DX" ipkg_archs

Yes, I suspect something about your machine config is resulting in this but its hard to me to say what. You can do things like "bitbake -e | grep ^PACKAGE_ARCHS" to see the contents of variables. I'm

Thanks, but that's way over my head at the moment ;-) I've searched through the meta data for PACKAGE_ARCHS, but that's not thrown anything up to make me think there was anything I should look

Can we not fix the X scripts so that if an fbdev X server is in use and the framebuffer device node does not exist, it just exits cleanly with a suitable message and doesn't timeout on

This sounds like the machine specific packages are failing to be found so it sounds like a package feed issue. Is sounds like PACKAGE_ARCHS isn't listing everything it needs to (such as the machine

Saul, can you either Ack or NAK this patchset - it's been out there for a week now and I'd like to be able to pull it in... Thanks, Tom

Acked-by: Darren Hart <dvhart@...> -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

I'd like to move beyond this in the future, but for the 1.1 release I think this is the right call: Acked-by: Darren Hart <dvhart@...> -- Darren Hart Intel Open Source Technology

Because qemuppc has no graphic emulation, remove console=tty0 and make it run into 3 run level. This can reduce boot time for qemuppc booting. Signed-off-by: Liming Wang

From: Liming Wang <liming.wang@...> apmd daemon needs this option to work, so add this to beagleboard kernel config file. Signed-off-by: Liming Wang <liming.wang@...> ---

I've got a configuration that builds ok under 4.0.1, but when I build under 5.0.1 I get the following right at the end: Installing task-poky-boot (1.0-r7) to root... Downloading

In my understanding 2.6 has now become 3 and .40 became .0 making it 3.0 therefore versions should be 3.0+gitrXXXX 3.1+gitrXXXX etc. 3.0.1 is similar to naming scheme 2.6.39.1 in olden days

Pushed to Poky/Master Sorry about this one, just got lost in the flood. Sau!

When adding dates to the whiteboard, please use the following format: (DD-MMM-YYYY) eg. (18-AUG-2011) It can be very confusing when people use DD-MM and MM-DD, depending on their locale. For DD <

The meta-yocto atom-pc is a more generic BSP than is needed for the Intel n450. Decouple the n450.conf from the meta-yocto atom-pc.conf. Add a linux-yocto_3.0.bbappend recipe. In the process: o

The following changes since commit fa92a44396b16be74f0de10256b0d42e52cf0bb6: meta-intel: update linux-yocto 3.0 kernel SRCREVs (2011-08-17 07:50:46 -0500) are available in the git repository at:

I'll give it a try (will be a while as I've moved to the 5.0.1 release and the build has just started!). Thanks for the suggestion :-) Chris Tapp opensource@... www.keylevel.com

I asked Sarah Sharp if she had any thoughts, she responded in part: One thing I might suspect is a problem with the host controller going into suspend. I think 2.6.34 didn't have support for USB

I haven't seen this merged yet, been a week. Is there a concern with the series, or maybe it just got lost in the mix? Thanks, Darren -- Darren Hart Intel Open Source Technology Center Yocto