Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "William J. Earl" <wje@fir.esd.sgi.com>
To: Ralf Baechle <ralf@Julia.DE>
Cc: shaver@neon.ingenia.ca, linux@cthulhu.engr.sgi.com,
	kneedham@ottawa.sgi.com
Subject: Re: It booooooooooots!
Date: Wed, 9 Apr 1997 11:37:30 -0700	[thread overview]
Message-ID: <199704091837.LAA27718@fir.esd.sgi.com> (raw)
In-Reply-To: <199704090525.HAA06508@kernel.panic.julia.de>

Ralf Baechle writes:
 > > ...
 > >  > Checking for 'wait' instruction...  unavailable.
 > > ...
 > > 
 > >      This appears to be a bug.  The R5000 does have the wait instruction.
 > 
 > Linux doesn't really check; instead it has encoded which CPU types
 > have a wait instruction.  I add the R500 to that list.

     As far as I know, all QED processors have the "wait" instruction.
All the 0x2???  processor ID values are QED processors.  Here are the current
values:

#define C0_IMP_NEVADA	0x28
#define C0_IMP_RM7000	0x27
#define C0_IMP_MAGIC	0x25
#define C0_IMP_SONIC	0x24
#define	C0_IMP_R5000 	0x23
#define	C0_IMP_R4650 	0x22 
#define	C0_IMP_R4700 	0x21
#define	C0_IMP_R4600 	0x20

I don't know which processors are SONIC, MAGIC, or NEVADA, but I think NEVADA
is the new RM5260 (a low-cost R5000).  

  parent reply	other threads:[~1997-04-09 18:38 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
1997-04-09  5:25   ` Ralf Baechle
1997-04-09  5:25     ` Ralf Baechle
1997-04-09 18:37     ` William J. Earl [this message]
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=199704091837.LAA27718@fir.esd.sgi.com \
    --to=wje@fir.esd.sgi.com \
    --cc=kneedham@ottawa.sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=ralf@Julia.DE \
    --cc=shaver@neon.ingenia.ca \
    /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