From: Rick Kwan <kenobi@coruscant.lightsaber.com>
To: linuxppc-dev@lists.linuxppc.org
Cc: rick.kwan@lightsaber.com
Subject: PReP spec
Date: Wed, 10 Feb 1999 11:53:09 -0800 [thread overview]
Message-ID: <199902101953.LAA01696@coruscant.lightsaber.com> (raw)
Hello, list... I have never posted here before. These are sorta
more hardware questions, but I'm not sure where else to ask.
My motivation is that I inherited a PReP box a year ago, and
intermittently play with it (e.g., Valentine's Day release); I'm
trying to migrate into serious play.
How does one get a copy of the PReP specification?
Is PReP still considered a viable commercial architecture or is it
reaching end-of-life?
--Rick Kwan
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-10 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-10 19:53 Rick Kwan [this message]
1999-02-11 3:17 ` PReP spec Ken Roberts
1999-02-11 4:29 ` David Edelsohn
1999-02-12 2:31 ` Ken Roberts
1999-02-11 3:55 ` Troy Benjegerdes
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=199902101953.LAA01696@coruscant.lightsaber.com \
--to=kenobi@coruscant.lightsaber.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rick.kwan@lightsaber.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).