[Yocto-builds] meta-yocto-bsp changes and 3.14

Bruce Ashfield bruce.ashfield at windriver.com
Fri Mar 28 12:58:08 PDT 2014

On 14-03-28 02:24 PM, Richard Purdie wrote:
> I've merged Bruce's 3.14 patches into master-next. With the yocto-bsp
> parts that I could pull together, there seemed to be some pieces
> missing, specifically:
> * the yocto-linux-dev.bbappend was underpopulated
> * the yocto-linux-3.14.bbappend was missing
> * no removal of beagleboard
> * no addition to the README for beaglebone
> * local.conf.sample needs updates
> * missing edgerouter configuration in linux-yocto*
> * should we be removing a mips BSP?
> * need a layer version bump so beth can handle this on the autobuilder

After suffering through two rounds of the entire kernel being fetched,
I've confirmed that the bbappend I've been using works for the reference
BSPs on 3.14.

As I mentioned before, my plan was to leave the untested reference BSPs
on 3.10 (particularly the FSL board) and update them once I get confirmation
that they work with 3.14.

I hadn't planned on adding the linux-yocto-dev.bbappend to meta-yocto-bsps,
since the hardware reference boards (unlike qemu) have a greater carrying
cost in terms of testing. So I keep that bbappend slightly out of
sight. At this point, it shouldn't be needed since all the boards
that support 3.14, set that explicitly in their config files.

As we rambled on in the thread, I was looking for a parking lot for
the retiring BSPs that work in 1.6, with the 3.10 kernel, but are not
the first choice. I won't fight to hard from it, and we can simply
pull them out of the 3.10 bbappend if there's no better option.

Attached is the bbappend that I used for testing. If it matches yours
we are good to go.


> I added commits for some of these, the 3.14 kernel bbappend is missing
> SRCREVs though for example. The state of where I got to is:
> http://git.yoctoproject.org/cgit.cgi/meta-yocto/log/?h=master-next
> Beth: Your AR is to figure out the autobuilder side of this and build
> the two new replacement BSPs (beaglebone and edgerouter) instead of the
> old ones. When that and the current build on the AB is done, can we run
> a build of master-next please?
> Denys: I'm hoping you can help out with the README
> Bruce: can you look at the linux-yocto-* changes, particularly the 3.14
> SRCREVs and that linux-yocto-dev looks right?
> Cheers,
> Richard

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-meta-yocto-bsp-populate-3.14-bbappend.patch
Type: text/x-patch
Size: 1725 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto-builds/attachments/20140328/63db1169/attachment-0002.bin>

More information about the yocto-builds mailing list