From: Dave Jones <davej@codemonkey.org.uk>
To: "Anthony L. Awtrey" <tony@awtrey.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: acpi_cpufreq stepping issue on Pentium M 1.2GHz
Date: Sun, 18 May 2008 20:08:10 -0400 [thread overview]
Message-ID: <20080519000810.GA11313@codemonkey.org.uk> (raw)
In-Reply-To: <482DCF52.6030307@awtrey.com>
On Fri, May 16, 2008 at 02:15:46PM -0400, Anthony L. Awtrey wrote:
> Hi,
>
> I've been trying to get the acpi_cpufreq working on my Panasonic
> Toughbook CF-18 (Intel Pentium M 1.2GHz). It works just fine on my CF-19
> (Intel Core Duo U2400) just fine.
>
> When I am on wall power, the system runs at full speed (1.2GHz) and when
> I pull it off wall power it steps to 600MHz and nothing I have tried
> changes that. I need to be able to run full speed while on battery.
Some BIOSes take away P states when theres a transition in power source.
Nothing much we can do about it. Check if your BIOS has an option to
let this be 'OS controlled', as opposed to 'automatic' or similar wording.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2008-05-19 0:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 18:15 acpi_cpufreq stepping issue on Pentium M 1.2GHz Anthony L. Awtrey
2008-05-19 0:08 ` Dave Jones [this message]
2008-05-19 11:29 ` Anthony L. Awtrey
2008-05-19 13:14 ` Dave Jones
2008-05-19 13:38 ` Anthony L. Awtrey
2008-05-20 10:38 ` Thomas Renninger
2008-05-21 12:51 ` Anthony L. Awtrey
2008-05-21 13:08 ` [PATCH] Make acpi-cpufreq more robust against BIOS freq changes behind our back Thomas Renninger
2008-05-21 13:15 ` Thomas Renninger
2008-05-21 15:00 ` [stable] " Greg KH
2008-05-21 18:48 ` Anthony L. Awtrey
2008-05-23 9:20 ` Thomas Renninger
2008-05-21 15:46 ` Anthony L. Awtrey
2008-06-02 22:36 ` [stable] " Chris Wright
2008-06-11 14:33 ` Thomas Renninger
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=20080519000810.GA11313@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=cpufreq@lists.linux.org.uk \
--cc=tony@awtrey.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;
as well as URLs for NNTP newsgroup(s).