[Yocto-builds] meta-yocto-bsp changes and 3.14
bruce.ashfield at windriver.com
Sun Mar 30 07:46:33 PDT 2014
On 2014-03-29, 7:12 PM, Richard Purdie wrote:
> On Fri, 2014-03-28 at 15:58 -0400, Bruce Ashfield wrote:
>> 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.
> Ok, I've dropped that. It does mean we get more restricted coverage with
> the -dev kernel though...
Right now the 3.14 tree and -dev are identical, which is why I'm not worried
about the bbappend. When I move -dev to 3.15, I'll send it out for
>> 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.
> I don't mind them in the bbappend of the kernel tree. My concern is that
> if the machine definition is in the repository, someone will try and
> build it. That means before we ship it, we need to build and test it and
> we don't have resources for it. I'd ideally therefore prefer to have
> only the selected machine in there.
Understood. I'll figure out a good place to stash it. I was more commenting
that it wasn't a missed commit, it was on purpose .. but we can decide
that the 'on purpose' part of it was wrong :)
>> Attached is the bbappend that I used for testing. If it matches yours
>> we are good to go.
> I tried it but I had trouble on beaglebone since the referenced commit
> doesn't match anything the beaglebone branch. Using
> fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c as with the others (and as per
> the branch head) is hopefully going to work better.
I really did mean 58b6d33dd898f901afbed10cfdec96b9d3148a00, but that was
me flipping the beagleboard and beaglebone. fecc really is the right commit
for the BBB, so your update is correct (and I've fixed my update
> I've also been having "fun" with the edgerouter BSP since we can't build
> qt4 for mips64. I think I've come up with the right set of magic changes
> to avoid the build failures with that.
> One remaining issue is that u-boot may be breaking for beaglebone. I'm
> hoping Denys can help there.
More information about the yocto-builds