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

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMwAjgMkyGM64RGpERAs3LAKCBtFoOPe49JO/K3SlC0euYs8XOCgCeKLsF
UMRKOIhRMMwUgrh5RsQ8dEw=
=nlIb
-----END PGP SIGNATURE-----