Skip to contentSkip to conversation

86xx: e600 and cputable.c

DISCUSSION Régis Odeyé 2 participants 2 messages Feb 23, 2009

lore
Share & tools
lore
#0 lore raw

Hi,

On our board based on 8641D, cat /proc/cpuinfo gives:
-bash-3.2# cat /proc/cpuinfo
processor : 0
cpu : 7448, altivec supported
clock : 1000.000000MHz
revision : 0.2 (pvr 8004 0202)
bogomips : 199.68

processor : 1
cpu : 7448, altivec supported
clock : 1000.000000MHz
revision : 0.2 (pvr 8004 0202)
bogomips : 199.68

total bogomips : 399.36
timebase : 100000000
platform : VM6250
Vendor : Kontron Modular Computers
Machine : VM6250
SVR : 0x80900121
Memory : 1024 MB

Is there a plan to deal with e600 core as it is done for e500 in cputable.c to be able to discriminate "classic" ppc against freescale cores ? Already a patch ?

Regards.

Signature · 6 lines
Régis ODEYE

Kontron Modular Computers SA
150, rue M. Berthelot / ZI Toulon Est / BP 244 / Fr 83078 TOULON Cedex 9
Phone: (33) 4 98 16 34 86           Fax: (33) 4 98 16 34 01
E-mail: [email protected]  Web : www.kontron.com
#1 lore raw
Quoted 24 lines · On Feb 23, 2009, at 10:48 AM, R=E9gis Odey=E9 wrote:

Hi,

On our board based on 8641D, cat /proc/cpuinfo gives:
-bash-3.2# cat /proc/cpuinfo
processor : 0
cpu : 7448, altivec supported
clock : 1000.000000MHz
revision : 0.2 (pvr 8004 0202)
bogomips : 199.68

processor : 1
cpu : 7448, altivec supported
clock : 1000.000000MHz
revision : 0.2 (pvr 8004 0202)
bogomips : 199.68

total bogomips : 399.36
timebase : 100000000
platform : VM6250
Vendor : Kontron Modular Computers
Machine : VM6250
SVR : 0x80900121
Memory : 1024 MB

Quoted 5 lines

Is there a plan to deal with e600 core as it is done for e500 in =20 cputable.c to be able to discriminate "classic" ppc against =20 freescale cores ?
Already a patch ?

what kernel version. I believe this is fixed:

commit a501d8f30e4fcca563e4ee462be00f96e51181d5

Author: Martin Langer <[email protected]>
Date:   Sun Sep 7 17:51:32 2008 +1000

powerpc: Fix major revision number for Freescale cores

Some 74xx cores by Freescale are using the configuration field =20
instead
of the major revision field for their revision number. This =20
corrects
the wrong behaviour for those ppc cores including my one.
...

- k=