public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Staikos <staikos@kde.org>
To: Chris Wedgwood <cw@f00f.org>, linux-kernel@vger.kernel.org
Subject: Re: Select voltage manually in cpufreq
Date: Tue, 18 Feb 2003 18:09:34 -0500	[thread overview]
Message-ID: <200302181809.34537.staikos@kde.org> (raw)
In-Reply-To: <20030218214726.GB15007@f00f.org>

On Tuesday 18 February 2003 16:47, Chris Wedgwood wrote:
> On Tue, Feb 18, 2003 at 10:42:20PM +0100, Pavel Machek wrote:
> > I've added possibility to manualy force specified frequency and
> > voltage... That's fairly usefull for testing, and I believe this (or
> > something equivalent) is needed because every 2nd bios seems to be
> > b0rken.
>
> Why are all the power/cpu patches so complex?  Can't we have a
> two-mode style operation, "slow-low-power" and "fast-high-power" or
> something?  Would that not work with 99% or what people need and also
> be somewhat more uniform across platforms, CPUs, etc?

  I think the important thing is for the kernel to provide the functionality 
that 99% of the people will need, and then for userspace tools/daemons to 
hide the complex portions and make it easy for a user to get what he wants.

   /proc is not nearly a valid user interface, but it is one of the 
application interfaces.

-- 

George Staikos


  parent reply	other threads:[~2003-02-18 23:01 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
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 [this message]
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=200302181809.34537.staikos@kde.org \
    --to=staikos@kde.org \
    --cc=cw@f00f.org \
    --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