Hello, On Mon, Nov 29, 2010 at 9:05 PM, Bruce Ashfield <bruce.ashfi...@windriver.com> wrote: > In message: [yocto] [PATCH] meta-bsp-kirkwood: created layer for > Marvellkirkwood > on 28/11/2010 Frans Meulenbroeks wrote: > >> This layer is a first attempt to create a layer for kirkwoord. > > On this topic. Is there any reason to not use linux-yocto > for the kernel ? Whenever possible, I'd like to get everyone > pulling in the same direction for these platforms. We have > ... > It also helps us review and push for platforms to be merged > upstrea if things go into a common kernel repository. > ... > It would also mean that the BSP would be kept up to date with > bug/security fixes and be considered for updating to > ... > at these patches in a 2.6.37 context (but obviously I don't > have the hardware to use for boot testing). > These are good points, but we have experienced *lots* of (old) vendor kernel patch dumps when I new machine is released.
Surely most patches would not be accepted upstream, or have become obsolete (need only much forward porting work in the most ideal case). In OpenEmbedded, the linux/ directory is wildly populated for this practical reason. How are we going to shove every machine from OpenEmbedded linux/ into linux-yocto? Or, better: who decides when it matches linux-yocto or should be linux-something else? It's mainly a problem originated by vendors working for years on their port and then dumping their 2.6.32 kernel in 2.6.39 times, not blaming anyone else here :) Regards, -- Leon _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto