From: Marc Singer <elf@buici.com>
To: paul.devriendt@amd.com
Cc: cpufreq@www.linux.org.uk
Subject: Re: Athlon 64 complains of frequency mismatch
Date: Wed, 23 Jun 2004 00:54:18 -0700 [thread overview]
Message-ID: <20040623075418.GA5213@buici.com> (raw)
In-Reply-To: <84EA05E2CA77634C82730353CBE3A8432698C5@SAUSEXMB1.amd.com>
On Wed, Jun 23, 2004 at 12:43:51AM -0700, paul.devriendt@amd.com wrote:
> > Perhaps this is an addition to the FAQ:
> >
> > Q609: AMD Cool&Quiet CPU won't load the powernow-k? driver. Why?
> >
> > A609: The powernow driver gets it's information about processor
> > states from the BIOS's reported ACPI control data. If the
> > powernow driver won't load it may be because Cool&Quiet hasn't
> > been enabled in the BIOS. Make sure that BIOS settings for a
> > PowerNow or a Cool&Quiet option are enabled.
> >
> > Or, maybe the driver should output a kernel message about BIOS
> > settings.
>
> Where is the FAQ ? I would like to read it :)
>
> How about having the driver put out a message referring to go
> read the FAQ ?
Hmm. It's hard to read your response. If you are being sarcastic
then perhaps I need to be more explicit.
--- linux/Documentation/cpu-freq/user-guide.txt_orig 2004-06-23 00:51:46.000000000 -0700
+++ linux/Documentation/cpu-freq/user-guide.txt 2004-06-23 00:52:35.000000000 -0700
@@ -71,6 +71,14 @@
[*] Only if "ACPI Processor Performance States" are available
to the ACPI<->BIOS interface.
+ Q: AMD Cool&Quiet CPU won't load the powernow-k? driver. Why?
+
+ A: The powernow driver gets it's information about processor
+ states from the BIOS's reported ACPI control data. If the
+ powernow driver won't load it may be because Cool&Quiet hasn't
+ been enabled in the BIOS. Make sure that BIOS settings for a
+ PowerNow or a Cool&Quiet option are enabled.
+
1.3 sparc64
-----------
next prev parent reply other threads:[~2004-06-23 7:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 7:43 Athlon 64 complains of frequency mismatch paul.devriendt
2004-06-23 7:54 ` Marc Singer [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-23 8:07 paul.devriendt
2004-06-23 7:43 paul.devriendt
2004-06-23 17:52 ` Len Brown
2004-06-22 15:28 paul.devriendt
2004-06-22 15:26 paul.devriendt
2004-06-22 16:07 ` Marc Singer
2004-06-22 17:07 ` Dominik Brodowski
2004-06-22 6:02 paul.devriendt
2004-06-22 7:30 ` Arjan van de Ven
2004-06-22 10:28 ` Andi Kleen
2004-06-22 15:16 ` Marc Singer
2004-06-18 18:51 Marc Singer
2004-06-19 10:44 ` Dominik Brodowski
2004-06-19 15:55 ` Marc Singer
2004-06-19 16:36 ` Marc Singer
2004-06-21 20:26 ` Dominik Brodowski
2004-06-21 21:42 ` Marc Singer
2004-06-22 17:11 ` Dominik Brodowski
2004-06-22 17:59 ` Marc Singer
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=20040623075418.GA5213@buici.com \
--to=elf@buici.com \
--cc=cpufreq@www.linux.org.uk \
--cc=paul.devriendt@amd.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox