* Re: CPU Nevada
2001-01-11 0:40 ` Kevin D. Kissell
@ 2001-01-11 0:40 ` Kevin D. Kissell
2001-01-11 0:48 ` Pete Popov
2001-01-11 4:06 ` Ralf Baechle
2 siblings, 0 replies; 6+ messages in thread
From: Kevin D. Kissell @ 2001-01-11 0:40 UTC (permalink / raw)
To: Pete Popov, linux-mips
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.
Kevin K.
----- 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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: CPU Nevada
2001-01-11 0:40 ` Kevin D. Kissell
2001-01-11 0:40 ` Kevin D. Kissell
@ 2001-01-11 0:48 ` Pete Popov
2001-01-11 4:06 ` Ralf Baechle
2 siblings, 0 replies; 6+ messages in thread
From: Pete Popov @ 2001-01-11 0:48 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: linux-mips
"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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU Nevada
2001-01-11 0:40 ` Kevin D. Kissell
2001-01-11 0:40 ` Kevin D. Kissell
2001-01-11 0:48 ` Pete Popov
@ 2001-01-11 4:06 ` Ralf Baechle
2001-01-11 4:06 ` Ralf Baechle
2 siblings, 1 reply; 6+ messages in thread
From: Ralf Baechle @ 2001-01-11 4:06 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: Pete Popov, linux-mips
On Thu, Jan 11, 2001 at 01:40:28AM +0100, 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.
No idea how the 6 ended up there; I wrote the Nevada support for Cobalt's
Qube which originally using a R5230, the small brother of the 5260 with
just a 32 bit external bus. Anyway, I fixed that buglet.
Ralf
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: CPU Nevada
2001-01-11 4:06 ` Ralf Baechle
@ 2001-01-11 4:06 ` Ralf Baechle
0 siblings, 0 replies; 6+ messages in thread
From: Ralf Baechle @ 2001-01-11 4:06 UTC (permalink / raw)
To: Kevin D. Kissell; +Cc: Pete Popov, linux-mips
On Thu, Jan 11, 2001 at 01:40:28AM +0100, 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.
No idea how the 6 ended up there; I wrote the Nevada support for Cobalt's
Qube which originally using a R5230, the small brother of the 5260 with
just a 32 bit external bus. Anyway, I fixed that buglet.
Ralf
^ permalink raw reply [flat|nested] 6+ messages in thread