From: Pete Popov <ppopov@embeddedalley.com>
To: Sylvain Munaut <tnt@246tNt.com>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: deletion of boards
Date: Tue, 13 Sep 2005 12:51:04 -0700 [thread overview]
Message-ID: <1126641064.11755.166.camel@localhost.localdomain> (raw)
In-Reply-To: <43272A02.7030603@246tNt.com>
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 parent reply other threads:[~2005-09-13 19:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 1:30 deletion of boards Pete Popov
2005-09-13 7:14 ` Thomas Sailer
2005-09-13 7:22 ` Matej Kupljen
2005-09-13 7:26 ` Pete Popov
2005-09-13 7:35 ` Matej Kupljen
2005-09-13 15:57 ` Pete Popov
2005-09-13 12:24 ` Ralf Baechle
2005-09-13 11:42 ` sjhill
2005-09-13 19:35 ` Sylvain Munaut
2005-09-13 19:51 ` Pete Popov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1126641064.11755.166.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=linux-mips@linux-mips.org \
--cc=tnt@246tNt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox