On 09/19/2012 06:05:22 PM, Marek Vasut wrote:
Dear Scott Wood,
> 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 <tr...@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.
Like doc/README.scrapyard ?
Heh. Yes, except maybe more prominent so people would know it exists.
:-)
That file does seem a bit board-centric; drivers and other things can
die off too.
-Scott
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
