linux-mips
[Top] [All Lists]

Re: Can't build a CONFIG_CPU_NEVADA kernel

To: Ralf Baechle <ralf@oss.sgi.com>
Subject: Re: Can't build a CONFIG_CPU_NEVADA kernel
From: Jun Sun <jsun@mvista.com>
Date: Wed, 14 Mar 2001 11:48:52 -0800
Cc: Daniel Jacobowitz <dan@debian.org>, linux-mips@oss.sgi.com
References: <20010314084633.A25674@nevyn.them.org> <20010314195919.A1911@bacchus.dhis.org> <20010314140529.A29525@nevyn.them.org> <20010314202058.B1911@bacchus.dhis.org>
Sender: owner-linux-mips@oss.sgi.com
Ralf Baechle wrote:

> > If it does, I can probably whip up a -mmad patch to binutils to allow
> > those opcodes - or I could introduce -mnevada, or whatever the
> > appropriate term would be, to mean "r8000 with the mad* extensions".
> > In fact, that would probably be easiest, and sounds like the most
> > correct.
> 
> Don't think of the r8000; the kernel only uses the -mcpu=r8000 option
> because the Nevada CPUs have _somewhat_ similar scheduling properties
> to the R8000.  This of it as an independant ISA expension which can
> be used with an arbitrary MIPS processor - even a R3000 processor.
> 

Although -mmad is generic, why do we need it for kernel compiling?  If no good
reason, I propose to remove -mmad from the Makefile for Nevada chip.

Of course, we still need to fix the -mmad implying -m4650 bug ...

Jun

<Prev in Thread] Current Thread [Next in Thread>