From: Chris Wedgwood <cw@f00f.org>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
davej@suse.de, linux@brodo.de
Subject: Re: Select voltage manually in cpufreq
Date: Tue, 18 Feb 2003 14:08:58 -0800 [thread overview]
Message-ID: <20030218220858.GA15273@f00f.org> (raw)
In-Reply-To: <20030218215819.GC21974@atrey.karlin.mff.cuni.cz>
On Tue, Feb 18, 2003 at 10:58:19PM +0100, Pavel Machek wrote:
> Well, and does slow-low-power mean 300MHz, 1.4V as bios said, or
> 300MHz, 1.2V which is probably also safe?
I have no idea... that's the point... the user almost never knows what
*exact* magic values are required, they just want fast-on-power or
slow-on-battery sort of thing.
> What about
> "as-fast-as-possible-but-not-exceed-140MHz-because-batteries-are-
> running-low-and-can-not-give-enough-current"? That's different from
> "fast-high-power", but it is *also* different from
> "slow-low-power". [This actually matters on beasts like
> zaurus]. What about
> "as-low-power-as-possible-but-make-sure-you-can-keep-display-up"?
> [On some machines cpu must be > some HMz for display to still work].
this just shows how silly these complex schemes are
you pick two options, a slow and fast option; both should work
--cw
next prev parent reply other threads:[~2003-02-18 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 21:42 Select voltage manually in cpufreq Pavel Machek
2003-02-18 21:47 ` Chris Wedgwood
2003-02-18 21:58 ` Pavel Machek
2003-02-18 22:08 ` Chris Wedgwood [this message]
2003-02-18 22:16 ` Pavel Machek
2003-02-18 22:16 ` Russell King
2003-02-18 22:33 ` Chris Wedgwood
2003-02-19 10:15 ` Dave Jones
2003-02-19 14:43 ` John Bradford
2003-02-18 23:09 ` George Staikos
2003-02-19 2:02 ` Alan Cox
2003-02-19 15:31 ` 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=20030218220858.GA15273@f00f.org \
--to=cw@f00f.org \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=pavel@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox