From: Tony Lindgren <tony@atomide.com>
To: Voluspa <lista1@telia.com>
Cc: Pavel Machek <pavel@ucw.cz>,
jesper.juhl@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference
Date: Mon, 25 Jul 2005 03:21:04 -0700 [thread overview]
Message-ID: <20050725102103.GG5837@atomide.com> (raw)
In-Reply-To: <20050722204439.54a63a00.lista1@telia.com>
* Voluspa <lista1@telia.com> [050722 11:46]:
> On Fri, 22 Jul 2005 20:02:36 +0200 Pavel Machek wrote:
> > will not help. It seems like your machine is simply not able to do
> > reasonable powersaving.
>
> Digging up this patch from last month regarding C2 on a AMD K7 implies
> that the whole blame can be put on kernel acpi:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=111933745131301&w=2
AFAIK Linux ACPI expects BIOS to contain all the necessary stuff to enable
C2 and C3. Otherwise they won't get enabled, and you have to create a custom
module like the amd76x_pm is.
There's been some talk on adding a module to enable C2 and C3 states for
various chipsets, but nobody seems to have enough time to do it...
Tony
next prev parent reply other threads:[~2005-07-25 10:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 18:04 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference Voluspa
2005-07-21 18:14 ` Jesper Juhl
2005-07-21 18:33 ` Voluspa
2005-07-22 14:48 ` Pavel Machek
2005-07-22 17:15 ` Voluspa
2005-07-22 18:02 ` Pavel Machek
2005-07-22 18:28 ` Voluspa
2005-07-22 18:44 ` Voluspa
2005-07-25 10:21 ` Tony Lindgren [this message]
2005-07-25 18:30 ` Bill Davidsen
2005-07-21 18:49 ` Guillaume Chazarain
2005-07-21 19:01 ` Voluspa
2005-07-26 13:14 ` Vojtech Pavlik
2005-07-26 14:53 ` Voluspa
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 5:23 Brown, Len
2005-07-26 14:52 ` Bill Davidsen
2005-07-26 6:29 Voluspa
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=20050725102103.GG5837@atomide.com \
--to=tony@atomide.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lista1@telia.com \
--cc=pavel@ucw.cz \
/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.