Yet another follow up. I finally found my C3 Beagleboard and the default kernel built off master yesterday works on that platform too. I was able to do another build with the tips you guys gave and

I think you are correct now that I look more closely at the meta-n450/conf/layer.conf file. It has: BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \

Bruce, Thanks for your efforts! Edwin

Look at the how the layers are parsed - this info is in <layer>/conf/layer.conf Try putting your .bbappend file in .../meta-intel/meta-n450/recipes-jfa/images/core-image-sato.bbappend --

There seems to be some sensitivity to where I put the statement IMAGE_INSTALL += "web-webkit". At first I just modifed the meta/receipes-sato/image/core-image-sato.bb file to include it. That caused

[YOCTO #1555] 1. Changed default signature handler to 'basichash' in poky.conf. 2. Added comment about PRservice settings in local.conf.extened. Signed-off-by: Lianhao Lu <lianhao.lu@...> ---

Fixed bug #1555. Changed the default handler to basic hash for poky distro. Also added some descriptive comment in local.conf.extended. The following changes since commit

Hi all, In my wanderings as a community manager, evidently I found time last year to set up both a "page" and a "group" on Facebook, and then proceeded to neglect both of them. I am shutting down the

Ah, very good! Yes, good to know information. I'm coming from OE-Angstrom/Arago and so far most things have been pretty familiar but it always helps to know how it fits together. I need to make

Thanks a lot for putting these together on the wiki, Beth! It really helps. Song

<bruce.ashfield@...> wrote: Will do. I also have a C3 Beagleboard around here somewhere and I'll verify that the images I built today work on that platform too. Regards, Brian

In meta-yocto/conf/distro/poky.conf there's a line which sets: PREFERRED_VERSION_linux-yocto ?= "2.6.37+git%" Which is then overridden for the qemu machines

Excellent! If you still want the default (which you likely do here), you can leave KMACHINE untouched in your bbappend and the inherited value from the core layers will take care of everything. Get

Thanks Bruce for pointing me in the right direction. I just wanted to follow up. I switched to master branch and did a clean build for Beagleboard. I can confirm that it worked. I blew my SD Card

I've done some initial wikification of this: https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Live_Debugging_Process Michael Halstead, as the SA, should probably be included on this

Intel at least have chosen to provide bootable images for their boards with a time-limited kernel to encourage people to do a build of their own for an actual product, rather than just pass through

Simple reason, the creator of the BSP wants you to configure and build your own kernel. The time limited kernel is for evaluation purposes to see if this is what you want, before you build it

What is the purpose of building the provided images with time limited kernel? Can I assume that a standard build of the unchanged meta-cedartrail BSP will use the non-tlk kernel? Jim A On Wed,

<bruce.ashfield@...> wrote: Thanks! I did a git checkout -b master origin/master and will try again. Regards, Brian

Interesting. You can open a bug on this, boot and sanity/peripheral tests were performed before I made the switch. So if this is broken, that's a bug and we can look into it. As you hinted, including