From: "William J. Earl" <wje@fir.engr.sgi.com>
To: Ralf Baechle <ralf@mailhost.uni-koblenz.de>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Magnum 4000 caches
Date: Thu, 23 Oct 1997 11:47:43 -0700 [thread overview]
Message-ID: <199710231847.LAA12820@fir.engr.sgi.com> (raw)
In-Reply-To: <199710231825.UAA26628@informatik.uni-koblenz.de>
Ralf Baechle writes:
...
> > The R6000 is a real challenge. It is substantially different
> > from the R3000 and R4000. In particular, it uses part of the cache
> > as a sort of second level TLB. ES/IX is the CDC version of MP RISC/os.
> > (MIPS worked on MP RISC/os, but never shipped it to customers; CDC took
> > it over as a product.) The I/O is fairly straightforward, being mostly
> > VME devices, but it does include I/O address mapping hardware which must
> > be configured.
>
> Is the information in newer releases of Kane's MIPS bible sufficient to
> do the R6000 part of the job? I guess the company (BIT ???) that made the
> R6000 is no longer around, so it would make sense if Roman'd ask them
> for a manual ...
BIT made the parts originally, but we later got the parts from NEC.
The latter were faster, more reliable, and much cheaper. CDC might still
provide the manuals. As far as I know, the R6000 is not well documented
in the regular MIPS documentation. I might, however, be able to get you
some information about processor issues.
prev parent reply other threads:[~1997-10-23 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-23 17:05 Magnum 4000 caches Ralf Baechle
1997-10-23 17:21 ` William J. Earl
1997-10-23 17:56 ` Ralf Baechle
1997-10-23 17:56 ` Ralf Baechle
1997-10-23 18:08 ` William J. Earl
1997-10-23 18:23 ` Ralf Baechle
1997-10-23 18:23 ` Ralf Baechle
1997-10-23 18:47 ` William J. Earl [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=199710231847.LAA12820@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@mailhost.uni-koblenz.de \
/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