From: Voluspa <lista1@telia.com>
To: len.brown@intel.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference
Date: Tue, 26 Jul 2005 08:29:39 +0200 [thread overview]
Message-ID: <20050726082939.2a7388cd.lista1@telia.com> (raw)
On 2005-07-26 5:23:08 Len Brown wrote:
>than C1 and the generic ACPI code doesn't support it,
>then it is either a Linux/ACPI bug or a BIOS bug -- file away:-)
The issue has made me fume enough to contemplating installing windos for
the first time in some 10 years. But I'll persevere. Will learn
ACPI-speak, read bios- and kernelcode. Then return, have no fear (even
if just to admit that the BIOS is buggy). Speaking of bugs, I was
directed, off-list, to the patch which mends your latest chip-away of
C2/C3 for many systems:
http://marc.theaimsgroup.com/?l=acpi4linux&m=112138186129178&w=2
It did however not fix my K8 system.
>I.e. The whole concept of ACPI is that you shoulud _not_ need
>a platform specific driver to accomplish this.
Indeed. It's supposed to be some kind of neutral non-discrimatory
standard... I suppose.
Mvh
Mats Johannesson
--
next reply other threads:[~2005-07-26 6:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 6:29 Voluspa [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-07-26 5:23 2.6.13-rc3 Battery times at 100/250/1000 Hz = Zero difference Brown, Len
2005-07-26 14:52 ` Bill Davidsen
2005-07-21 18:04 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
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
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=20050726082939.2a7388cd.lista1@telia.com \
--to=lista1@telia.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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