[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-developers] CUBE 2 make config, which CPU ?



Tom,
Thanks a lot you pointed me in the right direction. Nevada is not showing up in "make config" R56x0 is pointing to NEVADA.

jakob


At 11:51 03.04.2001 -0500, you wrote:
Jakob Strebel wrote
Type 'cat /proc/cpuinfo' and you'll get something like this.

cpu                     : MIPS
cpu model               : Nevada V10.0
system type             : Cobalt Networks Server
BogoMIPS                : 249.86
byteorder               : little endian
unaligned accesses      : 100
wait instruction        : yes
microsecond timers      : yes
extra interrupt vector  : yes
hardware watchpoint     : no

On my Qube 2, that means to use Nevada.  From /usr/src/linux/.config, I have:
#
# CPU selection
#
# CONFIG_CPU_R3000 is not set
# CONFIG_CPU_R6000 is not set
# CONFIG_CPU_R4300 is not set
# CONFIG_CPU_R4X00 is not set
# CONFIG_CPU_R5000 is not set
CONFIG_CPU_NEVADA=y
# CONFIG_CPU_R8000 is not set
# CONFIG_CPU_R10000 is not set

Tom

On Tue, 03 Apr 2001, you wrote:
> Dear List readers,
>
> Searching in the List I see the Qube 2 I read: the Qube-2 uses QED RM RM5231.
> Looking at the log file I see: loading R4000 MMU routines.
>
> CPU selection
> CPU type (R3000, R6000, R4300, R4x00, R5000, R56x0, R8000, R10000)
>
> Which CPU is recommended?
>
> Thanks in advance for your answer.
>
> jakob strebel
> Rebenhuebelstr.9
> CH5707 Seengen
> Switzerland
>
> _______________________________________________
> cobalt-developers mailing list
> cobalt-developers@xxxxxxxxxxxxxxx
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
--
--------------------
Tom A. Cox
Senior Programmer
Tri-Pacific Software
972-620-2520 ext. 23
www.tripac.com

_______________________________________________
cobalt-developers mailing list
cobalt-developers@xxxxxxxxxxxxxxx
http://list.cobalt.com/mailman/listinfo/cobalt-developers