From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: my dothan didn't work with cpufreq...
Date: Thu, 22 Jul 2004 08:04:37 +0200 [thread overview]
Message-ID: <20040722060437.GA8888@dominikbrodowski.de> (raw)
In-Reply-To: <1090461320.13505.3.camel@localhost>
On Wed, Jul 21, 2004 at 06:55:20PM -0700, Jeremy Fitzhardinge wrote:
> I've been meaning to look into this to see if there's some way to add a
> table method. It's moderately tricky because there's two steppings of
> Dothan, and the specs are not obvious to me (they seem to list 4
> voltages per frequency point, which is confusing).
AFAICS in some specs, there are identical-looking (CPUID, string) Dothans
with different voltage requirements, at least for the B1 stepping. Also, as
the usage of the ACPI P-State library in speedstep-centrino seems to work
flawlessly on Dothans [at least I haven't heard otherwise], I'm tempted to
remove the "(EXPERIMENTAL)" mark on it and possibly make it even the default.
What do you think?
> I guess it would also be good to get dumps from the ACPI tables. What's
> the best way to do that?
acpi_pdump with pdc=1 as parameter. This test module can be grabbed here:
http://www.brodo.de/patches/2004-04-06/cpufreq-acpi_pdump.c
Dominik
next prev parent reply other threads:[~2004-07-22 6:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 20:54 my dothan didn't work with cpufreq Damien Marchal
2004-07-13 9:49 ` Dominik Brodowski
2004-07-14 10:50 ` Damien Marchal
2004-07-16 8:19 ` Dominik Brodowski
2004-07-22 1:55 ` Jeremy Fitzhardinge
2004-07-22 6:04 ` Dominik Brodowski [this message]
2004-07-22 6:56 ` Jeremy Fitzhardinge
2004-07-22 9:31 ` Dominik Brodowski
2004-07-22 17:34 ` Jeremy Fitzhardinge
2004-07-23 19:38 ` Dominik Brodowski
2004-07-24 1:27 ` Jeremy Fitzhardinge
2004-07-24 7:06 ` Dominik Brodowski
2004-08-02 19:26 ` Dave Jones
2004-08-02 20:17 ` Jeremy Fitzhardinge
2004-08-02 20:29 ` Dave Jones
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=20040722060437.GA8888@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--cc=cpufreq@www.linux.org.uk \
--cc=jeremy@goop.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.