From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Wed, 19 Sep 2012 18:03:44 -0500
Subject: [U-Boot] [PATCH 32/71] serial: powerpc: Implement
 CONFIG_SERIAL_MULTI into bmw serial driver
In-Reply-To: <201209200057.56699.marex@denx.de> (from marex@denx.de on Wed
	Sep 19 17:57:56 2012)
References: <1347837696-3192-1-git-send-email-marex@denx.de>
	<505A4928.2080004@ti.com>
	<CALButCKy6YLq3tbgKm8b7pBnLny=yDPoR8YoVqyyNqeXfWnX7w@mail.gmail.com>
	<201209200057.56699.marex@denx.de>
Message-ID: <1348095824.22800.14@snotra>
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

On 09/19/2012 05:57:56 PM, Marek Vasut wrote:
> Dear Graeme Russ,
> 
> > Hi Tom,
> >
> > On Thu, Sep 20, 2012 at 8:37 AM, Tom Rini <trini@ti.com> wrote:
> > > A more elaborate set of statements on my feelings about "old"  
> boards
> > > and what needs to happen, in light of the facts that the code is
> > > messy, will require updating for DM and likelyhood of a small but
> > > devoted community around some of them.
> >
> > My gut feeling on this is to either move unmaintained / inactive
> > boards to a separate board directory
> 
> And hoard crap? No, you can dig them from git history, the objects  
> will still be
> there.
> 
> > or add a flag to boards.cfg (If
> > we add a flag to boards.cfg then we can specify that MAKEALL should
> > skip those boards)
> >
> > Either way, we can then let them bit-rot
> 
> I disagree
> 
> > (I know, bad words) but at
> > least if someone comes along with an actual board, they have a place
> > to start.
> 
> They can retrieve it from git history and re-add it in such unlikely  
> case.
> 
> > This is what happened to me with the x86 arch - the existing
> > code was horribly broken, but at least I had a solid foundation to
> > start reinvigorating it.
> 
> It's still horribly broken, but that's partly because of x86 itself  
> is a
> horribly broken CPU :-)

Maybe have a GRAVEYARD file that lists hardware support and other  
notable features that have been removed, so it's easy for someone to  
tell whether digging through the git history might be fruitful.

-Scott