linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Cort Dougan <cort@persephone.cs.nmt.edu>
Cc: Rick Kwan <kenobi@coruscant.lightsaber.com>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: platform specs (was: PReP spec)
Date: Fri, 12 Feb 1999 19:11:35 -0500	[thread overview]
Message-ID: <9902130011.AA72862@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Cort Dougan <cort@persephone.cs.nmt.edu> of "Fri, 12 Feb 1999 15:35:44 MST." <Pine.LNX.3.96.990212153508.18857A-100000@persephone.cs.nmt.edu>


>>>>> Cort Dougan writes:

Cort> }A list of current CHRP machines would indeed be interesting,
Cort> }if for nothing else, to show the breadth and flexibility of the
Cort> }architecture.  (Or lack thereof.)

Cort> All new rs6000s.

	Not all new RS/6000 systems are CHRP.  I believe that most or all
current 32-bit PowerPC systems are CHRP (43P, F50, etc.).  64-bit Model
S70 might be CHRP.  Newest RS/6000 models are not CHRP, including Power3
Model 260.

David

[[ 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 ]]

      parent reply	other threads:[~1999-02-13  0:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-12  9:13 platform specs (was: PReP spec) Rick Kwan
1999-02-12 22:35 ` 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 [this message]

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=9902130011.AA72862@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=cort@persephone.cs.nmt.edu \
    --cc=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).