Skip to contentSkip to conversation

/proc/cpuinfo output from some arch

OT Witek Kręcicki 12 participants 19 messages Jul 6, 2002 – Jul 11, 2002

lore
Share & tools
lore
#0 lore raw

I'm looking for /proc/cpuinfo output from following architectures: arm m68k mips s390 sparc.
I need it but I don't have access to any of them :/
TIA
Witek Krecicki

#1 lore raw
Quoted 3 lines · Witek Krêcicki

I'm looking for /proc/cpuinfo output from following architectures: arm m68k mips s390 sparc.
I need it but I don't have access to any of them :/

# cat /proc/cpuinfo 
CPU:            68060
MMU:            68060
FPU:            68060
Clocking:       65.7MHz
BogoMips:       131.48
Calibration:    657408 loops

Variations: CPU:68020,68030,68040,68060

	    MMU:68851,Sun-3,Apollo (CPU 020 only),68040,68060
     	    FPU:68881,68882 (CPU 020 and 030 only)
		"none(soft float)",68040,68060
#2 lore raw
In reply to Witek Kręcicki
Quoted 2 lines · * Witek Kr?cicki ([email protected]) wrote:

I'm looking for /proc/cpuinfo output from following architectures: arm m68k mips s390 sparc.

Well here are mips and m68k; I don't have an ARM box bootable at the moment:

This is from my SG Indy (Dino):

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

cpu : MIPS
cpu model : R4600 V2.0
system type : SGI Indy
BogoMIPS : 132.71
byteorder : big endian
unaligned accesses : 0
wait instruction : yes
microsecond timers : yes
extra interrupt vector : no
hardware watchpoint : no
VCED exceptions : not available
VCEI exceptions : not available

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

And the following shows the stunning computing power of my Sun 3/60:

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

CPU: 68020
MMU: Sun-3
FPU: 68881
Clocking: 19.3MHz
BogoMips: 4.83
Calibration: 24192 loops

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Dave
---------------- Have a happy GNU millennium! ----------------------

/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM, SPARC and HP-PA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/
#3 lore raw
In reply to Witek Kręcicki

Witek Kręcicki <[email protected]> writes:

|> I'm looking for /proc/cpuinfo output from following architectures: arm m68k |> mips s390 sparc.

This is arm:

Processor : Intel StrongARM-110 rev 4 (v4l)
BogoMIPS : 185.95
Features : swp half 26bit fastmult

Hardware : Rebel-NetWinder
Revision : 58ff
Serial : 0000000000001910

Andreas.

Signature · 4 lines
Andreas Schwab, SuSE Labs, [email protected]
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
#4 lore raw
Quoted 1 line · Andreas Schwab

Processor : Intel StrongARM-110 rev 4 (v4l)

Note that this could also be something like:

Processor : ARM/VLSI Arm1020id(wb)BRR rev 1 (v4)

or:

Processor : ARM ARM926EJ-Sid(wb)RR rev 2 (v5)

It might change further if the manufacturer decides to have a space in their name. Basically, /proc/cpuinfo was never meant to be passed by programs, and its not something I'd like to support with the current format.

Signature · 2 lines
Russell King ([email protected])                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
#5 lore raw

Hi,

Quoted 9 lines · Russell King

Processor : Intel StrongARM-110 rev 4 (v4l)

Note that this could also be something like:

Processor : ARM/VLSI Arm1020id(wb)BRR rev 1 (v4)

or:

Processor : ARM ARM926EJ-Sid(wb)RR rev 2 (v5)

I wonder if it's possible w/all those different formats. It's looking completely different on alpha, arm, i386, sparc and s/390x...

Regards, Thunder

Signature · 7 lines
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o?  K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y- 
------END GEEK CODE BLOCK------
#6 lore raw
In reply to Russell King
Followup to:  <[email protected]>
By author:    Russell King <[email protected]>
In newsgroup: linux.dev.kernel
Quoted 8 lines · Andreas Schwab
Quoted 1 line

Processor : Intel StrongARM-110 rev 4 (v4l)

Note that this could also be something like:

Processor : ARM/VLSI Arm1020id(wb)BRR rev 1 (v4)

Quoted 9 lines

or:

Processor : ARM ARM926EJ-Sid(wb)RR rev 2 (v5)

It might change further if the manufacturer decides to have a space in their name. Basically, /proc/cpuinfo was never meant to be passed by programs, and its not something I'd like to support with the current format.

/proc/cpuinfo was *definitely* meant to be parsed by programs. Unfortunately, lots of architectures seems to have completely missed that fact.

-hpa

Signature · 3 lines
<[email protected]> at work, <[email protected]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt	<[email protected]>
#7 lore raw
Quoted 3 lines · H. Peter Anvin

/proc/cpuinfo was *definitely* meant to be parsed by programs. Unfortunately, lots of architectures seems to have completely missed that fact.

Sigh, its a shame such things aren't documented somewhere in the kernel tarball.

Signature · 2 lines
Russell King ([email protected])                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
#8 lore raw
Quoted 9 lines · Russell King
Quoted 3 lines · H. Peter Anvin

/proc/cpuinfo was *definitely* meant to be parsed by programs. Unfortunately, lots of architectures seems to have completely missed that fact.

Sigh, its a shame such things aren't documented somewhere in the kernel tarball.

No kidding...

-hpa

#9 lore raw
In reply to Russell King
Quoted 8 lines · Russell King
Quoted 3 lines · H. Peter Anvin

/proc/cpuinfo was *definitely* meant to be parsed by programs. Unfortunately, lots of architectures seems to have completely missed that fact.

Sigh, its a shame such things aren't documented somewhere in the kernel tarball.

Ah, but you're supposed to remember the history! The colons were added to make parsing easier. I think that was done after somebody added spaces on the left, and lots of app developers screamed that the format had become hopeless.

Right now I'm looking to get the temperature, clock speed, and voltage. I get the first two on PowerPC hardware, but it's not obvious what mess an SMP system would spit out.

#10 lore raw
Quoted 6 lines · Albert D. Cahalan

Right now I'm looking to get the temperature, clock speed, and voltage. I get the first two on PowerPC hardware, but it's not obvious what mess an SMP system would spit out.

Alpha Quad:

cpu : Alpha
cpu model : EV56
cpu variation : 7
cpu revision : 0

cpu serial number       :
system type             : Rawhide
system variation        : Dodge
system revision         : 0
system serial number    : BT00000000
cycle frequency [Hz]    : 400000000
timer frequency [Hz]    : 1200.00
page size [bytes]       : 8192
phys. address bits      : 40
max. addr. space #      : 127
BogoMIPS                : 747.36
kernel unaligned acc    : 0 (pc=0,va=0)
user unaligned acc      : 416 (pc=12008d8d0,va=4463)
platform string         : AlphaServer 7310 5/400 4MB
cpus detected           : 4
cpus active             : 4
cpu active mask         : 000000000000000f                                    

Intel Quad:

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 1
cpu MHz : 701.636
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat \pse36 mmx fxsr sse
bogomips : 1399.19

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 1
cpu MHz : 701.636
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat \pse36 mmx fxsr sse
bogomips : 1402.47

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 1
cpu MHz : 701.636
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat \pse36 mmx fxsr sse
bogomips : 1402.47

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 10
model name : Pentium III (Cascades)
stepping : 1
cpu MHz : 701.636
cache size : 2048 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat \pse36 mmx fxsr sse
bogomips : 1402.47

Enjoy,

--George

#11 lore raw
In reply to Albert D. Cahalan

Hi!

Quoted 13 lines
Quoted 6 lines
Quoted 3 lines

/proc/cpuinfo was *definitely* meant to be parsed by programs. Unfortunately, lots of architectures seems to have completely missed that fact.

Sigh, its a shame such things aren't documented somewhere in the kernel tarball.

Ah, but you're supposed to remember the history! The colons were added to make parsing easier. I think that was done after somebody added spaces on the left, and lots of app developers screamed that the format had become hopeless.

Quoted 4 lines

Right now I'm looking to get the temperature, clock speed, and voltage. I get the first two on PowerPC hardware, but it's not obvious what mess an SMP system would spit out.

I thought that cpuinfo was ment to be non-chaning after boot?

Perhaps we want /proc/cpu/0/temperature containing single int?

Pavel

Signature · 2 lines
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
#12 lore raw
Quoted 5 lines · Pavel Machek

I thought that cpuinfo was ment to be non-chaning after boot?

Perhaps we want /proc/cpu/0/temperature containing single int?

/proc/cpu/<number>/<datapoint> would be a lot better for a whole bunch of things.

-hpa

#13 lore raw
Quoted 9 lines · H. Peter Anvin
Quoted 5 lines · Pavel Machek

I thought that cpuinfo was ment to be non-chaning after boot?

Perhaps we want /proc/cpu/0/temperature containing single int?

/proc/cpu/<number>/<datapoint> would be a lot better for a whole bunch of things.

What about /proc/sys/cpu/<number>/<datapoint> ?

We decided on the above path for cpufreq after mulling it over for several weeks... it might be a good idea if we can all agree to put stuff in one place, rather than spreading it out across /crap^w/proc

Signature · 2 lines
Russell King ([email protected])                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
#14 lore raw
Quoted 1 line

What about /proc/sys/cpu/<number>/<datapoint> ?

What happens if the cpus are hot plugged and change ID while doing the config 8)

#15 lore raw
Quoted 4 lines · Alan Cox
Quoted 1 line

What about /proc/sys/cpu/<number>/<datapoint> ?

What happens if the cpus are hot plugged and change ID while doing the config 8)

As far as SMP systems and cpufreq is concerned, we're going to have a /proc/sys/cpu/all/ as well - you can't control the clock rate of each cpu independently on such systems (otherwise they wouldn't be very symetric.)

Signature · 2 lines
Russell King ([email protected])                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html
#16 lore raw

Hi,

Quoted 4 lines · Russell King

As far as SMP systems and cpufreq is concerned, we're going to have a /proc/sys/cpu/all/ as well - you can't control the clock rate of each cpu independently on such systems (otherwise they wouldn't be very symetric.)

Yes, asymmetric multiprocessing is a much more diffcult field, but it's not currently an issue to us. (Well, we had this issue long ago, but the SMP approach won, because even though it's uncool, it's still easier to handle. Maybe AMP will return one day...)

Regards, Thunder

Signature · 7 lines
(Use http://www.ebb.org/ungeek if you can't decode)
------BEGIN GEEK CODE BLOCK------
Version: 3.12
GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$
N--- o?  K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G
e++++ h* r--- y- 
------END GEEK CODE BLOCK------
#17 lore raw
Quoted 4 lines

Yes, asymmetric multiprocessing is a much more diffcult field, but it's not currently an issue to us. (Well, we had this issue long ago, but the SMP approach won, because even though it's uncool, it's still easier to handle. Maybe AMP will return one day...)

Per CPU clock ratios are supported in several places. There is also a whole research field into SMP power management that goes with it

#18 lore raw
In reply to Alan Cox
Quoted 4 lines · Alan Cox
Quoted 1 line

What about /proc/sys/cpu/<number>/<datapoint> ?

What happens if the cpus are hot plugged and change ID while doing the config 8)

<driverfs_mount>/root/cpu/<number>/<datapoint>

That can handle dynamic data just fine :)

greg k-h