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

Just so I'm clear. You are asking about the switch to 3.0 as the default ? If so, that was only done in master for the upcoming 1.2 release and not on the edison branch, so you wouldn't pick it up by

On 11/01/12 15:20, Brian Hutchinson wrote: I can chime in here. I am currently trying to get my Beagleboard running on the master branch, and it is pulling in kernel 3.0.12. However

<bruce.ashfield@...> wrote: Would I get that change if I just did a git pull or do I have to do something else? I did a git pull to update my Edison checkout last night realizing that I

It will. I sent patches recently to make that the preferred version in the master branch. Cherry picking that change would probably be all you would need. Should be. Bruce

Hi, I followed the example in the "Yocto Project Development Manual" for setting up a local kernel repo and it didn't go so well. A month or two ago I checked out Edison and was able to build all

It should be. I just need to look at the fallback modes, and how this impacts different host systems. That being said, I've run with similar configs in the past (depending on the workload) with no

The problem is that even when you set the date, your Poky system does not use it when the system is rebooted because of this bug. The simplest work-around (until the bug fix is finalized) is to add

I agree, in general, the more community/group discussion that goes on the better the resulting effort will be. If the call was streamed live, there could be people listening and noting ideas which

Bruce, Can we enable SMP and virtio by default for qemux86/x86-64? This can achieve huge perf boost for workload inside qemu. E.g. we enabled self-hosted image, where we build yocto inside