Op 4 mei 2012, om 02:12 heeft Denys Dmytriyenko het volgende geschreven: > On Thu, May 03, 2012 at 07:20:47PM +0200, Koen Kooi wrote: >> >> Op 3 mei 2012, om 19:15 heeft Denys Dmytriyenko het volgende geschreven: >> >>> It's a heavy patch, but my question is - how is it different from linux-3.0 >>> we >>> already have, besides the version upgrade to 3.2? Why is it called >>> linux-mainline, the old linux recipe is also mainline with beagle patches. >>> >>> Basically, I'm trying to understand 2 things here: >>> - what's the difference between this beagle patch set and the one applied >>> on >>> top of e.g. 3.0.28? Is it a different dev model, goals, owner or anything >>> else >> >> Pretty much the same, with less PM. The goal is to keep moving closer to >> mainline and to a recent mainline version. With this update we'll be using >> the same kernel Robert Nelson uses for his ubuntu builds. > > Ok, the whole series is now in.
Crap, it was still RFC. I'll try to get the wifi and audio fixes done ASAP now. > >>> - why the name change with -mainline suffix? >> >> To namespace it like we planned for our u-boot recipes, a number of layers >> have linux_3.2.bb recipes that would clash :( I'm not really fond of it, but >> that's the price we pay for all these layers. > > Wouldn't linux-mainline_3.2.bb clash as well with another layer? I thought > the > agreement was to have TI-specific namespacing, such as SoC family in the > name... having the SoC name was just a side effect of using the tree-name (-psp-am335x, -denx, etc). _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
