From: Matt Porter <mporter@kernel.crashing.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Obsolete and unmaintained 4xx boards in 2.5
Date: Mon, 25 Aug 2003 09:41:13 -0700 [thread overview]
Message-ID: <20030825094113.A28149@home.com> (raw)
Hi all,
At OLS, Paul and I had a discussion about the overwhelming
number of 4xx boards in the tree. Recently, I decided to
do a bit of research on which ones are obsolete and/or
unmaintained. The goal is to remove some of these board ports
since they are in a constant state of brokenness due to the
lack of a maintainer.
If anyone has objections about any of the following boards being
removed, then please volunteer to maintain them. Several were
maintained long ago by mvista folks but that is no longer the
case.
cedar (np405l)- obsolete (replaced by ash) and unmaintained
redwood4 (stb3) - obsolete (replaced by redwood 5-6) and unmaintained
np4gs3 (np4gs) - unmaintained
oak (403gcx) - unmaintained. Last devel discussion on this one
was Sept. 2001, last query in Nov. 2001. It would
be nice if someone (with hardware) would volunteer
to maintain this since the old Tivo is based on 403.
-Matt
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-08-25 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030825094113.A28149@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).