From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp-out11.han.skanova.net ([195.67.226.200]) by linuxtogo.org with esmtp (Exim 4.69) (envelope-from ) id 1P93IS-0003SK-OF for openembedded-devel@lists.openembedded.org; Fri, 22 Oct 2010 00:07:42 +0200 Received: from [10.28.3.142] (83.91.92.154) by smtp-out11.han.skanova.net (8.5.124.10) (authenticated as u82406562) id 4C7E127001452BB8 for openembedded-devel@lists.openembedded.org; Fri, 22 Oct 2010 00:01:04 +0200 Message-ID: <4CC0B81F.6030706@atmel.com> Date: Fri, 22 Oct 2010 00:01:03 +0200 From: Ulf Samuelsson User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <1287233406-8778-1-git-send-email-ulf.samuelsson@atmel.com> <201010181520.30454.marcin@juszkiewicz.com.pl> <4CBC4DD4.3010908@atmel.com> <4CBC7F6A.9040000@atmel.com> <4CBCD3FC.5090305@atmel.com> <4CBF81FC.3040803@atmel.com> In-Reply-To: X-SA-Exim-Connect-IP: 195.67.226.200 X-SA-Exim-Mail-From: ulf.samuelsson@atmel.com X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on discovery X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_SOFTFAIL autolearn=ham version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:20:07 +0000) X-SA-Exim-Scanned: Yes (on linuxtogo.org) Subject: Re: [PATCH 1/5] Use common files for AT91SAM9 configuration X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2010 22:07:42 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Koen Kooi skrev: > -----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 have already come to the conclusion that we could have a single linux.bb recipe. This assumes that you define things like KERNEL_VERSION, SOC_FAMILY etc. outside the recipe and then include files with include filenames containing approproate ENVIRONMENT variables. I.E: include $(KERNEL_VERSION)/kernel_source include $(SOC_FAMILY)/$(KERNEL_VERSION)/kernel_patch etc. > > 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 > Openembedded-devel@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel BR Ulf Samuelsson