-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 21-10-10 10:43, Frans Meulenbroeks wrote:
> PS: my opinion is that machine maintainers generally know better what > kernel works best for their machines than distro owners; And what's stopping them to put DEFAULT_PREFERENCE_machine and COMPATIBLE_MACHINE in the kernel recipes? There is no technical reason for setting it in machine.conf, so why should we break the orthogonality for that? > PPS: what's next? removing the PREFERRED_PROVIDER_virtual/kernel from > the machine configs because you feel you know better ? That is actually an option these days since most kernel recipes set COMPATIBLE_MACHINE correctly :) But seriously, there are use cases for one distro to use a different kernel for a given machine for whatever reasons. This whole situation is a mess because recipes/linux is a mess. It would be a nice topic for OEDEM to see if we should switch to a poky BSP model. It would boils down to: 1 bblayer per machine or SOC_FAMILY containing: * machine.conf * first and second stage bootloaders * kernel I can see some serious issues with that, but that's for another thread to discuss. regards, Koen -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMwAb7MkyGM64RGpERAuYSAKCaGnOasoXFk0Cb9xvcASP211PU0gCfaacw 850xksIBon0+M5P9rbt4mOo= =5mO/ -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
