Re: Can't build a CONFIG_CPU_NEVADA kernel

[Jun Sun <jsun@mvista.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