From: Matthew Wilcox <willy@debian.org>
To: Derek Engelhaupt <derekengelhaupt@rocketmail.com>
Cc: Joel Soete <soete.joel@tiscali.be>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] L2000/N4000 smp devices/boot compare??
Date: Fri, 3 Oct 2003 01:18:10 +0100 [thread overview]
Message-ID: <20031003001810.GH24824@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20031002233801.23113.qmail@web12508.mail.yahoo.com>
[Derek, could you possibly wrap your mails around 70 columns? It's hard
to read/reply to your mails.]
On Thu, Oct 02, 2003 at 04:38:01PM -0700, Derek Engelhaupt wrote:
> First off, since the N, L, and A class are of the same generation
> of machines they are similar in some respects. Different in others.
> The L1000 and L2000 have a system card unique to that set of machines.
> Being that as it is, the L1000/2000 probably use a different I/O
> interface chip. The L1500 and L3000 are in essence an N Class system
> card cut in half and therefore use the same I/O interface as the N.
> The GSP in the L Class resides in the PCI card cage with the GSP in the
> N Class is a seperate card attaching directly to the system card via the
> hot swap disk backplane. The extra unknown system buses probably reside
> on the GSP of the N Class. That would be my educated guess of what the
> unknown system buses are. The N has two IKEs since it has both a left
> and a right PCI card cage attached directly to the system board.
According to the IO-ACD, these are actually the processors:
Prelude W+ 540 | NPROC | 00004 91 | 5D3
A500/L1000/L2000 use Astro/Elroy just like the B/C/J class. L1500/L3000/N
use Ike and Stretch in place of Astro. I once downloaded an N-class PDF
which I've subsequently lost. If I remember correctly, it looked like:
CPU --+-- CPU RAM CPU --+-- CPU
DEW ||||| DEW
+--------+--------+---- Stretch ----+--------+------+
IKE DEW DEW IKE
||||| CPU --+-- CPU CPU --+-- CPU |||||
Ropes Ropes
(Elroys on the end of the ropes, of course).
My understanding is that Stretch is the problem. We don't follow the
rules for non-coherent aliases and Stretch isn't as lenient as other
memory controllers.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
next prev parent reply other threads:[~2003-10-03 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 16:53 [parisc-linux] L2000/N4000 smp devices/boot compare?? Joel Soete
2003-10-02 23:38 ` Derek Engelhaupt
2003-10-03 0:18 ` Matthew Wilcox [this message]
[not found] ` <3F704CAF0000522B@ocpmta2.freegates.net>
2003-10-03 11:49 ` Matthew Wilcox
2003-10-14 16:59 ` Joel Soete
2003-10-15 4:52 ` Grant Grundler
2003-10-15 6:02 ` Joel Soete
2003-10-06 14:31 ` Grant Grundler
[not found] <3F8A29A2000021FB@ocpmta1.freegates.net>
[not found] ` <20031017023038.GA12379@colo.lackof.org>
[not found] ` <3F9193E7.9010504@tiscali.be>
[not found] ` <20031018220048.GC10704@colo.lackof.org>
2003-10-18 23:30 ` Joel Soete
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=20031003001810.GH24824@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=derekengelhaupt@rocketmail.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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