From: Pete Popov <ppopov@mvista.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: CPU Nevada
Date: Wed, 10 Jan 2001 16:48:06 -0800 [thread overview]
Message-ID: <3A5D02C6.FA7B9B06@mvista.com> (raw)
In-Reply-To: 012301c07b67$19b95c40$0deca8c0@Ulysses
"Kevin D. Kissell" wrote:
>
> C'mon Pete, it's obviously a typo! It predates my involvement
> with the code - hell, I never even knew that "Nevada" was the
> QED code name for the R5200 family before I started hacking
> on the MIPS Linux kernel, even though I had an R5230 system
> in my lab. The "6" is probably shifted left one position from
> "R5260", which was, I believe, the first chip of the Nevada
> family to ship.
That's what I figured, but hey, it doesn't hurt to make sure. I'm
working with a 5231 and wanted to make sure I don't need to add another
cpu type.
Pete
> ----- Original Message -----
> From: "Pete Popov" <ppopov@mvista.com>
> To: <linux-mips@oss.sgi.com>
> Sent: Wednesday, January 10, 2001 11:03 PM
> Subject: CPU Nevada
>
> >
> > I can't find any information on a CPU Nevada, which supposedly is a 56x0
> > type. Is "R56x0 CONFIG_CPU_NEVADA" really meant to be "R52x0
> > CONFIG_CPU_NEVADA"? The product id code of 0x2800 matches the QED 52xx
> > processors (at least the 5231) -- I can't find anything on a 56x0 CPU.
> >
> > Pete
next prev parent reply other threads:[~2001-01-11 0:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 22:03 CPU Nevada Pete Popov
2001-01-11 0:40 ` Kevin D. Kissell
2001-01-11 0:40 ` Kevin D. Kissell
2001-01-11 0:48 ` Pete Popov [this message]
2001-01-11 4:06 ` Ralf Baechle
2001-01-11 4:06 ` Ralf Baechle
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=3A5D02C6.FA7B9B06@mvista.com \
--to=ppopov@mvista.com \
--cc=kevink@mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.