Re: [RFC] turning conf/machine into a set of bblayers

[Graeme Gregory <dp@xora.org.uk>]

On 21/10/2010 10:33, Koen Kooi wrote:
> Hi,
>
> Recipes/linux is a mess and recipes/u-boot is as well. It would be a
> nice topic for OEDEM to see if we discuss switching to a poky BSP model.
> It would boil down to:
>
> 1 base bblayer with shared files:
> * conf/machine/include
> * recipes/linux/*.inc
>
> 1 bblayer per machine or SOC_FAMILY containing:
> * machine.conf
> * first and second stage bootloaders
> * kernel
>
> So, what are peoples thoughts on this? I haven't thought this through
> myself, so feel free to point out any show stoppers.
> I do not want this to turn into a "splitting the metadata" discussion,
> while I'm all for that, it really is a seperate effort and discussion.
> But any bblayer style split would benefit from OE being a collection of
> git submodules instead of a monolithic tree[1].
>
> Regards,
>
> Koen
>
> [1] Provided git submodules stop sucking so hard in future git versions
This is something I have advocated before but never formally presented a
RFC to OEDEM.

With this model it quickly becomes clear which machines have support.

The only problem comes with BLAH_machine type overides. Are they done as
amend.inc (or whatever the current method is) in overlay or are they
allowed into main repo. I think amend.inc in this case is probably the
way to go.

Probably some form of dummy machine (maybe x86) needs to be defined in
main repo just so main repo can be parsed.

Graeme