From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tom <Tom.Rix@windriver.com>
Date: Sun, 06 Sep 2009 17:30:15 -0500
Subject: [U-Boot] ARM Pull Request
In-Reply-To: <20090906211836.0B3AE832E8DE@gemini.denx.de>
References: <20090905013643.GK30118@game.jcrosoft.org>
	<4AA1F8FF.4090206@googlemail.com>
	<20090905153750.GC18844@game.jcrosoft.org>
	<4AA360F8.5040209@googlemail.com>
	<20090906131658.GE18844@game.jcrosoft.org>
	<4AA3F86D.4040403@googlemail.com>
	<1252262241.25403.7.camel@ptyser-laptop>
	<4AA4020C.8080200@googlemail.com> <4AA419D7.2010406@windriver.com>
	<20090906211836.0B3AE832E8DE@gemini.denx.de>
Message-ID: <4AA437F7.9060900@windriver.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:
> Dear Tom,
>
> In message <4AA419D7.2010406@windriver.com> you wrote:
>   
>> I know i may be muddying this up but..
>> The devkit8000 looks a lot like the beagle.
>> Have you already thought of just rolling devkit8000 into beagle?
>>     
>
> That's actually a good idea, if possible.
>
>   
>> My opinion on naming is to keep omap3_ prefix consistent.
>> People used to building with their favorite omap3_* config should continue.
>> For now, new omap3 boards to use the omap3_ prefix.
>>     
>
> NAK. This violates the current naming scheme.
>
>   
>> If we want to break the config names, we should do it after a release.
>>     
>
> This what he have now: merge window time. Time for restructuring.
>
>   
>> A good time for that will be when the omap4 versions come in and we
>> have to figure out how to put them in.
>>     
>
> NAK. Rather do it immediately, before that grows even further.
>
> Best regards,
>
> Wolfgang Denk
>
>   
Ok
I will take care of making the changes if they don't already exist.
Tom