public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gryniewicz <dang@fprintf.net>
To: Robert Love <rml@ximian.com>
Cc: Dave Jones <davej@redhat.com>,
	Matthew Garrett <mgarrett@chiark.greenend.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Laptops & CPU frequency
Date: Wed, 14 Jan 2004 14:23:27 -0500	[thread overview]
Message-ID: <1074108207.5935.15.camel@localhost> (raw)
In-Reply-To: <1074107842.1153.959.camel@localhost>

On Wed, 2004-01-14 at 14:17, Robert Love wrote:
> Dave did not mean that the other power management schemes cannot do the
> automatic reduction on loss of AC, just that there is no SMM/BIOS hacks
> to do it automatically.
> 
> Your APM scripts are probably adjusting your CPU speed when you go on
> AC.  Fedora does this, for example.

No APM scripts, no APM even.  I have ACPI, but no acpid, and I don't
currently do anything with ACPI other than get battery status and
temperature.  It also happened before I built in any cpufreq support.

> That is cool - the OS (user-space, even) controls the policy.
> 
> What we don't like is how SpeedStep can be controlled from SMM.

This happens even booted into DOS, so it's definitely a BIOS thing.  I
haven't looked into turning it off, I can check next time I reboot.
-- 
Daniel Gryniewicz <dang@fprintf.net>

  reply	other threads:[~2004-01-14 19:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11  2:56 Laptops & CPU frequency jlnance
2004-01-11  3:17 ` Robert Love
2004-01-11  4:12   ` Valdis.Kletnieks
2004-01-11  6:16   ` Willy Tarreau
2004-01-11 10:27   ` Xavier Bestel
2004-01-11 10:33     ` Xavier Bestel
2004-01-12 16:58       ` Jerry Cooperstein
2004-01-12 21:19         ` Xavier Bestel
2004-01-12 19:52       ` john stultz
2004-01-12 20:11         ` Disconnect
2004-01-12 23:19           ` john stultz
2004-01-12 21:28         ` Xavier Bestel
2004-01-12 22:07           ` john stultz
2004-01-13  9:13             ` Xavier Bestel
2004-01-11 17:06   ` Matthew Garrett
2004-01-11 17:13     ` Robert Love
2004-01-11 17:44       ` Matthew Garrett
2004-01-11 17:54         ` Robert Love
2004-01-14  4:59           ` Dave Jones
2004-01-14 19:11             ` Daniel Gryniewicz
2004-01-14 19:17               ` Robert Love
2004-01-14 19:23                 ` Daniel Gryniewicz [this message]
2004-01-15 20:42                 ` Pavel Machek
2004-01-15 21:18                   ` Daniel Gryniewicz
2004-01-15 22:21                   ` John Bradford
2004-01-15 22:48                     ` Pavel Machek
2004-01-19 17:44             ` Ducrot Bruno
2004-01-16 10:47         ` Pavel Machek

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=1074108207.5935.15.camel@localhost \
    --to=dang@fprintf.net \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgarrett@chiark.greenend.org.uk \
    --cc=rml@ximian.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