Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Oliver M . Bolzer" <oliver@gol.com>
To: linux-mips@oss.sgi.com
Subject: Re: MIPS processor identification register
Date: Tue, 17 Jul 2001 22:46:17 +0200	[thread overview]
Message-ID: <20010717224617.A4132@magi.sukisuki.org> (raw)
In-Reply-To: <1114092660.995374763@[192.168.1.117]>; from naren@clearwaternetworks.com on Tue, Jul 17, 2001 at 12:59:23PM -0700

Hi!

On Tue, Jul 17, 2001 at 12:59:23PM -0700, Narendra Sankar <naren@clearwaternetworks.com> wrote...
 
> Is there a complete list somewhere of the different PRID (CP0 register 15) 
> values across the entire MIPS family - including all the different vendors?

Not that I know of any, but for reference, the PlayStation2's EmotionEngine
Processor (R5900) has a fixed Impl value of 0x2E.

[oliver@asuka tmp]$ cat /proc/cpuinfo 
cpu                     : MIPS
cpu model               : R5900 V1.4
system type             : EE PS2
BogoMIPS                : 392.40
byteorder               : little endian
unaligned accesses      : 0
wait instruction        : no
microsecond timers      : no
extra interrupt vector  : yes
hardware watchpoint     : no
VCED exceptions         : not available
VCEI exceptions         : not available


# If anybody is interested in poking around a PlayStation2 running Linux
# by SSH. send me a mail. I got a non-NDA fully GPL/LGPL compliant unit.
# It's running an 2.2.1 kernel that looks more like a 2.2.1{8,9} when
# looked under the hood. It was delivered that way by SCEI and somebody
# despeartely needs to update it. Unfortunatly I'm a userspace guy.
  
-- 
	Oliver M. Bolzer
	oliver@gol.com

GPG (PGP) Fingerprint = 621B 52F6 2AC1 36DB 8761  018F 8786 87AD EF50 D1FF

  reply	other threads:[~2001-07-17 20:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 19:59 MIPS processor identification register Narendra Sankar
2001-07-17 20:46 ` Oliver M . Bolzer [this message]
2001-07-17 20:48 ` Kevin D. Kissell
2001-07-17 20:48   ` Kevin D. Kissell

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=20010717224617.A4132@magi.sukisuki.org \
    --to=oliver@gol.com \
    --cc=linux-mips@oss.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