All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dominik Brodowski <linux@dominikbrodowski.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: my dothan didn't work with cpufreq...
Date: Wed, 21 Jul 2004 18:55:20 -0700	[thread overview]
Message-ID: <1090461320.13505.3.camel@localhost> (raw)
In-Reply-To: <20040713094937.GB8124@dominikbrodowski.de>

On Tue, 2004-07-13 at 11:49 +0200, Dominik Brodowski wrote:
> Maybe. The frequency/voltage pairs for Dothans are different to those of
> Banias. A built-in table isn't possible for Dothans, IIRC, as even if you 
> know the CPUID you can't know for 100% which pairs are valid -- it depends
> on some other info not in the CPUID.

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).

Anyway, I have a good collection of /proc/cpuinfos now, so I can pick
through them to see what common elements there are.

I guess it would also be good to get dumps from the ACPI tables.  What's
the best way to do that?

[ And for those who've mailed me and got nothing back - I'm sorry about
that.  I have been getting a lot of reports - people seem to be buying a
lot of laptops... ]

	J

  parent reply	other threads:[~2004-07-22  1:55 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 [this message]
2004-07-22  6:04     ` Dominik Brodowski
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=1090461320.13505.3.camel@localhost \
    --to=jeremy@goop.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=linux@dominikbrodowski.de \
    /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.