From: davidw@linuxcare.com (David N. Welton)
To: linuxppc-dev@lists.linuxppc.org
Subject: MPC405 - supported?
Date: 26 Sep 2000 15:34:01 +0200 [thread overview]
Message-ID: <87aecvmg52.fsf@eugene.prosa.it> (raw)
In-Reply-To: Dan Bethe's message of "Tue, 8 Feb 2000 17:44:10 -0800 (PST)"
I've been having a look at the mailing lists, searching sites for
information and so on, but I haven't been able to find anything that
indicates one way or another whether it is or not, and how well.
Thankyou,
--
David N. Welton, Responsabile Progetti Open Source, Linuxcare Italia spa
tel +39.049.8043411 fax +39.049.8043412 cel +39.348.2879508
davidw@linuxcare.com, http://www.linuxcare.com/
Linuxcare. Support for the revolution.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-09-26 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-26 13:34 David N. Welton [this message]
2000-09-26 14:33 ` MPC405 - supported? David Edelsohn
2000-09-26 14:53 ` David N. Welton
2000-09-26 16:35 ` David A. Gatwood
2000-09-26 17:33 ` Frank Rowand
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=87aecvmg52.fsf@eugene.prosa.it \
--to=davidw@linuxcare.com \
--cc=linuxppc-dev@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).