From: Bruno Ducrot <ducrot@poupinou.org>
Subject: Re: powernow-k7 for XP-M 2400+ CPU
Date: Fri, 28 May 2004 12:34:03 +0200
Sender: cpufreq-bounces@www.linux.org.uk
Message-ID: <20040528103403.GV4933@poupinou.org>
References: <20040525225007.2DCE949C52@nathan.muc.de>
	<20040526102057.GK4933@poupinou.org>
	<20040526171938.1920049C55@nathan.muc.de>
	<20040526185434.GP4933@poupinou.org>
	<20040528061524.7A75649C4D@nathan.muc.de>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20040528061524.7A75649C4D@nathan.muc.de>
Errors-To: cpufreq-bounces+glkc-cpufreq=gmane.org@www.linux.org.uk
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: Harald Milz <milz@seneca.muc.de>
Cc: cpufreq@www.linux.org.uk

Hi Harald,

On Fri, May 28, 2004 at 08:15:24AM +0200, Harald Milz wrote:
> Bruno Ducrot <ducrot@poupinou.org> wrote:
> > Yes, I can probably help you somehow.  But send the dmesg at
> > first.  You only waste my time if you don't post that damn log.
> 
> My CPU says,
> 
> powernow: PowerNOW! Technology present. Can scale: frequency and voltage.
> powernow: Found PSB header at c00f0810
> powernow: Table version: 0x12
> powernow: Flags: 0x1 (Desktop voltage regulator)
> powernow: Settling Time: 100 microseconds.
> powernow: Has 1 PST tables. (Only dumping ones relevant to this CPU).
> powernow: No PST tables match this cpuid (0x7a0)
> powernow: This is indicative of a broken BIOS.
> powernow: See http://www.codemonkey.org.uk/projects/cpufreq/powernow-k7.shtml

Ok.  Then the bios detect somehow that the processor is powernow capable
but is buggy in regard to generate the PST table at POST.
It should be helpfull that you run that little toy:

http://poup.poupinou.org/cpufreq/powernow-k7/dump_psb.c

Just to see what's there in this PST.

Also the flags from the bios indicate that there is a desktop voltage
regulator, and AFAIK it's not possible to change voltage from that.

> and the CPU is seen by the BIOS as
> 
> processor       : 0
> vendor_id       : AuthenticAMD
> cpu family      : 6
> model           : 10
> model name      : AMD Athlon(TM) MP
> stepping        : 0
> cpu MHz         : 1800.924
> cache size      : 512 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 1
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mp mmxext 3dnowext 3dnow
> bogomips        : 3563.52
> 
> But it is a 2400+ XP-M with a Barton core. I suspect the BIOS says Athlon
> MP because the MP's and the XP-M's L5.3 bridges are open which confuses the
> BIOS. The CPU runs at 133x13,5, i.e. within its specs. I do not intend to
> overclock it although the mobiles are said to be well overclockable. 

I suspect more that the BIOS is not able to says if an Athlon is mobile,
or not.  Actually there is very few differences (in detection code, I
mean) to sort a MP from a mobile one.

> The only thing I need is the powernow-dmesg output of a similar CPU on
> whatever machine, and then I will patch the powernow-k7 module to have it
> fake a similar PST. Simple enough as it seems. 

Cheers,

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.