From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dan.rpsys.net ([93.97.175.187]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1UBRQq-0005jr-Cv for openembedded-core@lists.openembedded.org; Fri, 01 Mar 2013 15:59:34 +0100 Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r21EoSoB021584; Fri, 1 Mar 2013 14:50:29 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NPlkUYlpZusT; Fri, 1 Mar 2013 14:50:28 +0000 (GMT) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r21EoJSB021581 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 1 Mar 2013 14:50:22 GMT Message-ID: <1362148961.1055.57.camel@ted> From: Richard Purdie To: Bruce Ashfield Date: Fri, 01 Mar 2013 14:42:41 +0000 In-Reply-To: References: <51309549.8010502@communistcode.co.uk> X-Mailer: Evolution 3.6.3-1 Mime-Version: 1.0 Cc: the oe-core layer , Patches Subject: Re: [RFC] U-Boot Recipes X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 14:59:37 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2013-03-01 at 08:33 -0500, Bruce Ashfield wrote: > On Fri, Mar 1, 2013 at 6:47 AM, Jack Mitchell wrote: > > Today I was building an image for the beaglebone with oe-core + > > meta-beagleboard. meta-beagleboard pretty much provides the machine > > definition and the kernel. In order to build the correct u-boot (2013.01+) I > > had to add u-boot 2013.01 to oe-core. Whilst during this I noticed the mess > > that the u-boot directory had become, I think we need to have a show of > > hands who uses what u-boot recipes and can they migrate to newer (common) > > versions. > > The mpc8315e-rdb reference uses v2012.04, and a quick survey didn't turn up > any other explicit preferred versions in the layers that I have around my > development machine. > > So for now v2012.04 needs to stay, but as we bump that board to the 3.8 kernel, > we can give another bootloader a test run. > > > > > When I submit a patch to get 2013.01 supported, that would make 4 different > > releases of u-boot; which seems a bit excessive. > > Most releases that I've ever used have kept compatibility fairly well, so I'm > all for keeping the number of active versions to a minimum. I'd say three is > a good number, since that matches the number of active kernel versions in > oe-core as well. I think one u-boot would be nice. Lets see if we can bump up the mpc8315e-rdb version... Cheers, Richard