From: Dave Jones <davej@redhat.com>
To: Bruno Ducrot <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: [PATCH] powernow-k7: example use for powernow_acpi_init()
Date: Mon, 22 Mar 2004 14:27:40 +0000 [thread overview]
Message-ID: <20040322142740.GG29733@redhat.com> (raw)
In-Reply-To: <20040322123614.GP28592@poupinou.org>
On Mon, Mar 22, 2004 at 01:36:14PM +0100, Bruno Ducrot wrote:
> Indeed. And making ACPI perflib in case of known broken BIOS via
> DMI may be good (the ASUS should work with that patch, if I read
> correctly the DSDT). There may be though one little annoying thing for
> the ASUS bug: FSB will be reported at 100MHz whereas it is at
> 133MHz, but it's only cosmetic, I hope.
Hmm, won't that skew the calculated frequencies somewhat ?
> The real trouble is that I don't know how to retrieve FSB on a
> athlon/duron: MSR_IA32_EBL_CR_POWERON do not give it :(
*nod*. I even looked through the powernow docs hoping that the fsb
would be stored in one of those registers, but no.
One thing that I did just find though that is interesting.
In the powernow documents, they describe the current/maximum/startup FID
and say "multiply by 100 to determine the frequency" which is very odd
if there really are 133 bus parts out there.
It does state in another part of the document that the FSB is either 100
or 133 MHz, but in bold.. "For mobile applications the FSB is 100 MHz"
Very odd.
Dave
next prev parent reply other threads:[~2004-03-22 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-22 9:25 [PATCH] powernow-k7: acpi support Bruno Ducrot
2004-03-22 9:38 ` [PATCH] powernow-k7: example use for powernow_acpi_init() Bruno Ducrot
2004-03-22 9:51 ` Dave Jones
2004-03-22 12:36 ` Bruno Ducrot
2004-03-22 12:43 ` [PATCH] powernow-k7: stupid bug in a printk introduced Bruno Ducrot
2004-03-22 14:27 ` Dave Jones [this message]
2004-03-22 18:23 ` [PATCH] powernow-k7: example use for powernow_acpi_init() Bruno Ducrot
2004-03-22 18:25 ` Dominik Brodowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040322142740.GG29733@redhat.com \
--to=davej@redhat.com \
--cc=cpufreq@www.linux.org.uk \
--cc=ducrot@poupinou.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.