linux-mips
[Top] [All Lists]

Re: deletion of boards

To: Sylvain Munaut <tnt@246tNt.com>
Subject: Re: deletion of boards
From: Pete Popov <ppopov@embeddedalley.com>
Date: Tue, 13 Sep 2005 12:51:04 -0700
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
In-reply-to: <43272A02.7030603@246tNt.com>
Organization: Embedded Alley Solutions, Inc
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1126575034.11755.85.camel@localhost.localdomain> <43272A02.7030603@246tNt.com>
Reply-to: ppopov@embeddedalley.com
Sender: linux-mips-bounce@linux-mips.org
On Tue, 2005-09-13 at 21:35 +0200, Sylvain Munaut wrote:
> Pete Popov wrote:
> > The AMD Pb1000, Pb1100, Pb1500, and Hydrogen3 boards are not up to date
> > in 2.6 and seem to be of very little interest to anyone. Any objections
> > if I remove them to reduce the clutter?
> > 
> > Pete
> > 
> > 
> 
> Theses files were of some help when bringing up new board based on thos
> processors.

Why not use the Db1x equivalent? If you have an au1000 based board, you
should probably base your port on the db1000 board, not the pb1000
anyway.

I didn't get a clear answer on whether it's ok to remove those boards
but I guess that's normal. The problem with keeping boards around that
very few people are interested in is that no one maintains them, the
code is broken, and quite honestly I think it creates confusion for
developers that have a custom board based on, let's say, the Au1500.
Unless that developer knows that the pb1000 code is broken, how would he
know to base his code on the db1000 instead of the pb1000? If the
support for these boards is broken now, it will only get worst. Anytime
someone makes mods to supported boards, it's bound to break something in
the already unsupported ones and make that code even more unusable.

Pete


<Prev in Thread] Current Thread [Next in Thread>