From: Rick Kwan <kenobi@coruscant.lightsaber.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: platform specs (was: PReP spec)
Date: Fri, 12 Feb 1999 01:13:04 -0800 [thread overview]
Message-ID: <199902120913.BAA14181@coruscant.lightsaber.com> (raw)
Thanks to Ken Robert's reply to my PReP spec query, I found the
PowerPC FAQ, dated 27 February 1997 at
http://www.mot.com/SPS/PowerPC/library/ppc_faq/ppc_faq.html
and from there, found my way to
ftp://ftp.austin.ibm.com/pub/technology/spec
In this FTP site, the PReP documents are dated Oct 28, 1994, but
there is a "chrp" directory there with documents dated Nov 20, 1995
thru Oct 2, 1996.
In my sporadic reading, it does indeed appear that CHRP has
superceded PReP. However, the above CHRP specs seem either pretty
old or pretty stable. Or am I looking in the wrong place?
>From the FAQ, I also made the journey to Yellowknife, at
http://www.mot.com/SPS/PowerPC/teksupport/refdesigns/yk.html
The design manual is dated 98 Feb 20, and clearly states that it
is a PowerPC/CHRP reference design.
A list of current CHRP machines would indeed be interesting,
if for nothing else, to show the breadth and flexibility of the
architecture. (Or lack thereof.)
--Rick Kwan, Lightsaber Computing
rick.kwan@lightsaber.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-02-12 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-12 9:13 Rick Kwan [this message]
1999-02-12 22:35 ` platform specs (was: PReP spec) Cort Dougan
1999-02-13 0:00 ` Matt Porter
1999-02-13 0:55 ` Cort Dougan
1999-02-13 4:45 ` Matt Porter
1999-02-13 0:11 ` David Edelsohn
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=199902120913.BAA14181@coruscant.lightsaber.com \
--to=kenobi@coruscant.lightsaber.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).