From: "Keld Jørn Simonsen" <keld-6PR53cSIHaE@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: problem with cpu eating too much power, prize given if solved
Date: Thu, 24 Jun 2004 17:35:13 +0200 [thread overview]
Message-ID: <20040624153513.GB19545@rap.rap.dk> (raw)
Dear ACPI developers,
I have a problem with my Acer Travelmate 233.
Many times I just want to read the screen, eg emails or documents,
and then still the cpu will be in idle mode, where
it uses 7.5 W out of the about 15 W that the whole machine uses.
I have found out from Intel data sheets that my
Mobile Intel Celeron 2.0 GHz CPU consumes 7.5 W in idle loop/
stop grant/sleep states, (and 5.0 W i deep sleep state).
So I would like to have the CPU stopped completely (consuming 0 W)
while I still could read the screen. In that way I should
be able to have about double the lifetime on the battery,
going to about 7 hours from the 3.5 hours I have now.
I would like the machine to wake up again by any keystroke
on the keyboard or mouse input. I would like the input to be
reacted upon (not just used to wake up the system, and
then forgotten).
I do not have the skills to program this myself, so
instead I offer a prize of USD 1000 to the person(s) that
can give me a patch for kernel 2.6 and appropiate documentation
that can solve the above problem. The patch needs to be GPL,
and demonstrably run on my laptop. I need the patch before
2004-10-01, after what date the prize offer expires.
I would like that the patch was written in a general way to cover for
CPUs that burn considerable power in idle loop and other states, so that
other users can benefit from it. Also I would prefer that the patch be
rolled into the normal ACPI kernel source tree, but the latter request
is not a condition for the prize.
Best regards
Keld
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-06-24 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 15:35 Keld Jørn Simonsen [this message]
[not found] ` <20040624153513.GB19545-EittdKFJ/bZ/SzgSGea1oA@public.gmane.org>
2004-06-24 17:40 ` problem with cpu eating too much power, prize given if solved Michael Frank
[not found] ` <opr930o2uv4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-25 12:46 ` Keld Jørn Simonsen
[not found] ` <20040625124637.GA14795-EittdKFJ/bZ/SzgSGea1oA@public.gmane.org>
2004-06-25 15:52 ` Michael Frank
[not found] ` <opr95qdzjj4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-25 17:06 ` Keld Jørn Simonsen
2004-06-28 20:40 ` Pavel Machek
[not found] ` <20040628204008.GK698-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2004-06-29 15:57 ` Keld Jørn Simonsen
[not found] ` <20040629155718.GA1866-EittdKFJ/bZ/SzgSGea1oA@public.gmane.org>
2004-06-29 22:10 ` Pavel Machek
[not found] ` <20040629221019.GA25464-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-06-29 22:50 ` Keld Jørn Simonsen
2004-06-29 20:17 ` Michael Frank
[not found] ` <opsadhbojo4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-29 22:11 ` Pavel Machek
[not found] ` <20040629221111.GB25464-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-06-30 14:16 ` Michael Frank
[not found] ` <opsaeu9tyb4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-06-30 17:37 ` Keld Jørn Simonsen
[not found] ` <20040630173754.GA29587-EittdKFJ/bZ/SzgSGea1oA@public.gmane.org>
2004-06-30 19:37 ` Pavel Machek
2004-07-01 0:03 ` Michael Frank
[not found] ` <opsafmf8px4evsfm-TBR8pM7LtsqkE96DxU8f+dAkNl5+tjhE@public.gmane.org>
2004-07-05 18:55 ` Keld Jørn Simonsen
2004-06-30 19:35 ` 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=20040624153513.GB19545@rap.rap.dk \
--to=keld-6pr53csihae@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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