Re: [PATCH] Intel clock speed detection

Dave Cinege (dcinege@psychosis.com)
Wed, 31 Dec 97 11:16:32 -0500


On Tue, 30 Dec 1997 17:26:48 -0800 (PST), Robert Woodcock wrote:

My results --

Dual P100:
Schizo# root [~] (while :; do ./mhz.estimate; done)
99.716670 MHz processor.
99.716779 MHz processor.
99.716606 MHz processor.

Cyrix 6x86MX P200 (150MHz):
worldwithin# root [~] (while :; do ./mhz.estimate; done)
0.389905 MHz processor.
0.422032 MHz processor.
0.280823 MHz processor.

Kooky...let's make it do somthing:
worldwithin# root [~] (while :; do ./mhz.estimate; done)
0.497011 MHz processor.
36.334751 MHz processor.
147.476782 MHz processor.
149.089824 MHz processor.
96.968480 MHz processor.
6.109385 MHz processor.

Ahhh....it's a the set6x86 halt power saving mode I have on.
Reset the chip with virgin regs:
worldwithin# root [~] (while :; do ./mhz.estimate; done)
150.342652 MHz processor.
150.342862 MHz processor.
150.342978 MHz processor.

Dual PPro 180s:
Zen-Machine# [/usr/src] (while :; do ./mhz.estimate; done)
119.752978 MHz processor.
119.753089 MHz processor.
119.753087 MHz processor.

This is because you are using the normal time instead of a constant (like the RTC)
This box has a custom bus speed hack. The jumpers refer to the 120MHz setting
but the chips are actually cranking at 180MHz, thus the reported time is 1.5x faster
then it really is. (The value above adjusted is 179.6296305)

As far as I can tell this is a BIOS setting corisponding to the position of the
jumpers. If I had the BIOS source I could fix this in 30 seconds.
(or 45 seconds according to my box : >)

-------------------------------------------------------------------------
http://www.psychosis.com/emc/ Elite MicroComputers 908-541-4214
http://www.psychosis.com/linux-router/ Linux Router Project