public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Michael Blakeley <mike@blakeley.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: why use acpi for cpufreq?
Date: Tue, 31 Oct 2006 19:04:42 +0100	[thread overview]
Message-ID: <20061031180442.GA4297@isilmar.linta.de> (raw)
In-Reply-To: <454684D9.1080805@blakeley.com>

Hi,

On Mon, Oct 30, 2006 at 03:03:53PM -0800, Michael Blakeley wrote:
> I've recently been bitten by 
> http://bugzilla.kernel.org/show_bug.cgi?id=7157 - I also have an HP 
> nc6400, with bios F.05, and can't downgrade to F.03 because my CPU only 
> became supported in F.05. While I'm waiting to see if HP will fix this 
> problem in a future bios rev, I wondered why cpufreq needs any bios 
> information in the first place?
> 
> This is all well outside my technical expertise, so I'm sure that I'm 
> misunderstanding the problem - but that's why I'm asking. Basically my 
> question is: why can't cpufreq interrogate the CPU directly, in order to 
> find out what sort of cpu frequency scaling it supports (SpeedStep in 
> various flavors, PowerNow, and whatever else is out there in the wild)? 
> Wouldn't that be more robust than relying on the bios to get it right?

Unfortunately, no -- it is not only a matter of the processor on whether CPU
frequency and voltage scaling is supported, but also a matter of the
motherboard. Not all combinations of frequencies and voltages which run
stable on one notebook may run well on a different notebook with the same
CPU. Therefore, such hardcoded table-based approaches are only available in
rare cases.

	Dominik

      reply	other threads:[~2006-10-31 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 23:03 why use acpi for cpufreq? Michael Blakeley
2006-10-31 18:04 ` Dominik Brodowski [this message]

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=20061031180442.GA4297@isilmar.linta.de \
    --to=linux@dominikbrodowski.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=mike@blakeley.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