On Fri, 2011-07-15 at 09:51 -0400, Bruce Ashfield wrote: > On Fri, Jul 15, 2011 at 9:21 AM, Phil Blundell <p...@pbcl.net> wrote: > > The other day I was working on a BSP layer for a fairly generic i586 > > system and I was struck by the fact that we don't appear to have any > > vanilla kernel recipes in oe-core. I had sort of expected that, to get > > a standard bzImage out, I would just need to ship an appropriate > > defconfig in my layer and everything else would "just work". > > Hmm. Perhaps it isn't documented clearly enough as such, but the linux-yocto > kernel base can work in this mode, since that was a design goal of > 1.0. > > You pick a branch, throw in a config fragment (or defconfig if you really > want) and build. The base branches in the tree are generic enough to > sort a range of boards out of the box, and should form a base.
Okay, cool. I'll give it a go and see how I get on. Is there a description anywhere of what the functional differences are between the code in linux-yocto git and the upstream kernel.org tree? p. _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core