All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kirk Bresniker <kirkb@chrome.rose.hp.com>
To: davinp@celltech.com (Davin Petersen)
Cc: parisc-linux@thepuffingroup.com
Subject: RE: [parisc-linux] H60
Date: Wed, 30 Jun 1999 14:38:23 PDT	[thread overview]
Message-ID: <199906302138.OAA20302@chrome.rose.hp.com> (raw)
In-Reply-To: <BF0601275C6FD211B04900A0C9E9205241D107@mailsrvr.hq.celltech.com>; from "Davin Petersen" at Jun 30, 99 10:26 am

The letter in the [GHI][567] systems refers to the number of I/O slots
on the backplane. The number designates the processor board. The

50 = Uni 96MHz PA-7100, 256K I$, 256K D$
60 = Uni 96MHz PA-7100, 1024K I$, 1024K D$
70 = Dual 96MHz PA-7100, 1024K I$, 1024K D$ per processor

I wrote an article in the HP Journal about the I70 development, which
has block diagrams which descibe the system at a high level.

PA-RISC Symmetric Multiprocessing in Midrange Servers 
  http://www.hp.com/hpj/94jun/jun94_31.pdf

KMB
--
+============================================================+
|       Kirk Bresniker    	(916) 785-5677		     |
|       8000 Foothills Blvd                                  |
|       Roseville, CA 95747-5649                             |
|       kirkb@rose.hp.com                                    |

  reply	other threads:[~1999-06-30 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-30 17:26 [parisc-linux] H60 Davin Petersen
1999-06-30 21:38 ` Kirk Bresniker [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-07-01  1:20 Kevin Carson
1999-06-30 15:54 Davin Petersen
1999-06-30 17:27 ` Stan Sieler
1999-06-30  5:20 Mike Hibler
1999-06-29 23:51 Davin Petersen
1999-06-30  0:13 ` Stan Sieler
1999-06-30  0:43   ` Alex deVries
1999-06-30  0:53     ` Stan Sieler
1999-06-30  5:51     ` Rich Rauenzahn
1999-06-30  6:34       ` Alex deVries
1999-06-30  6:55         ` Richard J. Rauenzahn

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=199906302138.OAA20302@chrome.rose.hp.com \
    --to=kirkb@chrome.rose.hp.com \
    --cc=davinp@celltech.com \
    --cc=parisc-linux@thepuffingroup.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 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.