All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: ggs@shiresoft.com
Cc: paubert@iram.es, linuxppc-dev@lists.linuxppc.org
Subject: Re: Apple Job Posting and Good News for LinuxPPC developers
Date: Sat, 27 Mar 1999 15:44:54 -0500	[thread overview]
Message-ID: <9903272044.AA52736@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Guy Sotomayor <ggs@shiresoft.com> of "Fri, 26 Mar 1999 22:27:59 PST." <199903270627.WAA18114@aragorn.shiresoft.com>


>>>>> Guy Sotomayor writes:

Guy> Actually I think the 64bit PPCs are called PowerPC II.  They're reasonably
Guy> nice chips last time I looked.  They are expensive to put together in a
Guy> system (ie 8MB L2, 128bit data bus, etc).  Also the 6xx bus is a split
Guy> transaction bus, so the bus controllers are a bit more complex too.  I
Guy> also think that all the data paths are ECC'd with parity on addresses. 
Guy> For a good example on what type of systems are built using these things,
Guy> look at the S70 Advanced server.

	64-bit PowerPC is an architecture, not a single chip.  The first
implementation was the PPC620 from Somerset, eventually only used by
Groupe Bull.  The S70 and S7A use a chip from IBM Rochester also used in
AS/400s.  The Power3 (aka PPC630fp) is yet a third 64-bit PowerPC
implementation.  IBM's recent 64-bit PowerPC chips are augmented to
support additional requirements of AS/400 systems.

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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-03-27 20:44 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-14 13:35 Blue G3 and machine check Benjamin Herrenschmidt
1999-03-15 16:42 ` Ryuichi Oikawa
1999-03-15 17:09   ` Geert Uytterhoeven
1999-03-24  9:30 ` Gabriel Paubert
1999-03-24 23:12   ` Paul Mackerras
1999-03-25 11:20     ` Gabriel Paubert
1999-03-25 16:46       ` Apple Job Posting and Good News for LinuxPPC developers Kevin B. Hendricks
1999-03-25 19:12         ` David Edelsohn
1999-03-26 11:31           ` Gabriel Paubert
1999-03-26 16:13             ` David Edelsohn
1999-03-27  6:27               ` Guy Sotomayor
1999-03-27 20:44                 ` David Edelsohn [this message]
1999-04-02 12:11             ` Holger Bettag
1999-04-02 17:11               ` David Edelsohn
1999-04-02 22:19                 ` Douglas Godfrey
1999-04-03 17:42                 ` Holger Bettag
1999-04-05 16:11                   ` Gabriel Paubert
1999-04-05 16:06               ` Gabriel Paubert
1999-04-06  5:53                 ` Douglas Godfrey
1999-03-26  6:08         ` Nathan Hurst
1999-03-26 13:51           ` sean o'malley
1999-03-28  5:08             ` Cort Dougan
1999-03-26 20:33           ` N.G. Temme
1999-03-29 23:44       ` Blue G3 and machine check Paul Mackerras
1999-03-30 11:41         ` Gabriel Paubert
1999-03-31 16:20           ` Ryuichi Oikawa
1999-03-31 18:39             ` Gabriel Paubert
1999-04-05 16:36               ` Ryuichi Oikawa
1999-04-05 17:11                 ` Gabriel Paubert
1999-04-04  1:17             ` Joel Klecker
1999-04-09  5:58               ` Joel Klecker
1999-04-09 16:12                 ` Ryuichi Oikawa
1999-03-25 12:10     ` Benjamin Herrenschmidt

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=9903272044.AA52736@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=ggs@shiresoft.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.