Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.esd.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: It booooooooooots!
Date: Tue, 8 Apr 1997 17:02:14 -0700	[thread overview]
Message-ID: <199704090002.RAA14801@fir.esd.sgi.com> (raw)
In-Reply-To: <9704091140.ZM8508@windy.wellington.sgi.com>

Alistair Lambie writes:
 > On Apr 9, 11:38am, William J. Earl wrote:
 > > Subject: Re: It booooooooooots!
 > > Mike Shaver writes:
...
 > >  > Checking for 'wait' instruction...  unavailable.
 > > ...
 > >
 > >      This appears to be a bug.  The R5000 does have the wait instruction.
 > 
 > I don't think David ever worked on an R5000.  The only platforms were R4600 &
 > R4400...soooo, there may be some issues to be resolved.
...

     On an Indy, the R5000 and R4600 are basically equivalent, except
for the MIPS IV extensions and larger caches (32 KB versus 16 KB) on the R5000.
The R5000 does have built-in secondary cache control, which is used on the O2,
but it is not used on the Indy.  On the Indy, the R5000 uses the same off-chip
secondary cache controller as the R4600.  The wait instruction operates the
same on both processors.  The wait instruction is not really essential in any
case, since its main purpose is to save power, and the R5000 and R4600 don't
use much power anyway.

  parent reply	other threads:[~1997-04-09  0:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-08 22:23 It booooooooooots! Mike Shaver
1997-04-08 23:37 ` William J. Earl
     [not found]   ` <9704091140.ZM8508@windy.wellington.sgi.com>
1997-04-09  0:02     ` William J. Earl [this message]
1997-04-09  5:25   ` Ralf Baechle
1997-04-09  5:25     ` Ralf Baechle
1997-04-09 18:37     ` William J. Earl
1997-04-09 11:48 ` Alistair Lambie
1997-04-08 23:56   ` Mike Shaver
1997-04-08 23:56     ` Mike Shaver
1997-04-09 12:06     ` Alistair Lambie
1997-04-09  0:00   ` William J. Earl

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=199704090002.RAA14801@fir.esd.sgi.com \
    --to=wje@fir.esd.sgi.com \
    --cc=linux@cthulhu.engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox