From: andrew may <acmay@acmay.homeip.net>
To: David Updegraff <dave@cray.com>
Cc: linuxppc-embedded@lists.linuxppc.org,
Stefan Roese <stefan.roese@esd-electronics.com>
Subject: Re: 405GPr
Date: Thu, 6 Jun 2002 16:25:55 -0700 [thread overview]
Message-ID: <20020606162555.B28991@ecam.san.rr.com> (raw)
In-Reply-To: <3CFFDDFF.6070407@cray.com>
On Thu, Jun 06, 2002 at 05:11:11PM -0500, David Updegraff wrote:
>
> Anyone playing with adding IBM 405GPr to the cputable?
Stephan said on the PPCboot list that he will have boards with
them soon. He has done patches for PPCBoot so the kernel may not
be far off. It will still be a couple of weeks before I get a
board with one yet.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-06 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 20:48 Ebony 440 board Brian Kuschak
2002-06-06 22:11 ` 405GPr David Updegraff
2002-06-06 23:25 ` andrew may [this message]
2002-06-07 7:40 ` 405GPr Stefan Roese
2002-06-10 13:11 ` 405GPr David Updegraff
2002-06-10 14:23 ` 405GPr Stefan Roese
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=20020606162555.B28991@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=dave@cray.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.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;
as well as URLs for NNTP newsgroup(s).