From: Tom Hughes <tom@compton.nu>
To: Thomas Renninger <trenn@suse.de>
Cc: Cristiano Prisciandaro <cristiano.p@solnet.ch>,
Dave Jones <davej@redhat.com>,
cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver
Date: Fri, 05 Dec 2008 23:05:39 +0000 [thread overview]
Message-ID: <4939B3C3.8060205@compton.nu> (raw)
In-Reply-To: <200812040257.09099.trenn@suse.de>
Thomas Renninger wrote:
> The biggest problem I see with these "special" ACPI cpufreq interface is:
> Can there be Asus/eeepcs which provide these ACPI functions (maybe dummies on
> future machines?), but can still be switched via the spec conform and more
> efficient acpi-cpufreq driver via PSS tables?
So should we tie this driver to particular DMI signature(s) then? As far
as I know it is only useful for the Eee 900 and possibly the 701 when
running later BIOSes.
> BTW: Have you tried out how much power (or at least battery life time) you
> win?
Running with wifi and the screen off, and the CPU busy (doing m5sum of
/dev/zero) I get 2:37 run time at 900MHz and 3:09 at 630MHz so the
increase in run time is about 20% on that test.
Tom
--
Tom Hughes (tom@compton.nu)
http://www.compton.nu/
next prev parent reply other threads:[~2008-12-05 23:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 15:27 [PATCH 1/1] cpufreq: eeepc 900 frequency scaling driver Cristiano Prisciandaro
2008-11-23 18:04 ` Pavel Machek
2008-12-02 16:15 ` Matthew Garrett
2008-12-02 20:14 ` Pavel Machek
2009-03-16 4:24 ` Len Brown
2009-03-16 8:29 ` Pavel Machek
2009-03-17 8:30 ` Fabio Comolli
2009-03-17 8:59 ` Fabio Comolli
2008-11-24 9:38 ` Tom Hughes
2008-11-24 15:13 ` Thomas Renninger
2008-11-24 16:36 ` Thomas Renninger
2008-11-24 16:41 ` [Acpi4asus-user] " Corentin Chary
2008-11-24 16:48 ` Tom Hughes
2008-11-24 16:58 ` Corentin Chary
2008-11-24 17:07 ` Tom Hughes
2008-11-24 16:46 ` Tom Hughes
2008-11-24 23:02 ` Cristiano Prisciandaro
2009-04-05 7:43 ` [Acpi4asus-user] " Corentin Chary
2009-04-05 10:20 ` Matthew Garrett
2009-04-05 11:39 ` Grigori Goronzy
2008-11-24 16:39 ` Tom Hughes
2008-11-24 19:09 ` Cristiano Prisciandaro
2008-12-03 19:26 ` Tom Hughes
2008-12-04 1:57 ` Thomas Renninger
2008-12-05 23:05 ` Tom Hughes [this message]
2008-12-06 16:35 ` Matthew Garrett
2008-12-07 15:55 ` Tom Hughes
2008-12-09 12:36 ` 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=4939B3C3.8060205@compton.nu \
--to=tom@compton.nu \
--cc=cpufreq@vger.kernel.org \
--cc=cristiano.p@solnet.ch \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trenn@suse.de \
/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