-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02-11-10 22:14, Eric Bénard wrote: > Hi, > > Le 02/11/2010 21:46, Koen Kooi a écrit : >> I do fear that pulling things into seperate layers too much will make it >> harder to propagate fixes... >> > yes, in your example, the fines in conf/machine/include are common to > all omap boards (and even all cortexa8 for tune-cortexa8.inc) and thus > when fixing one BSP you have to think to fix the others (and to > communicate the fix to other BSP maintainers). > The same apply for most of the .inc in recipes-bsp/*/. > > Do you think the following setup is possible ? > > - ARM overlay (containing all generic files for ARM achitecture : > conf/machines/include for example) > > - OMAP3 overlay (containing all generic files for OMAP3 SOC : > conf/machines/include/omap* + recipes/linux u-boot x-load base files for > omap3 architecture, > > - specific board overlay (conf/machine/themachine.conf + board specific > additions in recipes/linux u-boot & x-load (with patches based on top of > the OMAP3 overlay).
That was pretty much what I was thinking, the angstrom-layers stuff is something I need to get working before thursday, so it is a bit hacky. It will get cleaned up after I get back from my holiday :) Hopefully more people have tried different setups and we can bang out a decent RFC. regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFM0IBFMkyGM64RGpERAhVvAJ98xHlzrMSjH/d6a5//GQimg89j0wCgnVIs ASfxeRULybqKbDAjBMlwkXg= =tE/N -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
