cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco Poli <frx@firenze.linux.it>
To: cpufreq@www.linux.org.uk
Subject: Re: userspace not supported for longrun?
Date: Wed, 2 Jun 2004 17:39:26 +0200	[thread overview]
Message-ID: <20040602173926.70a07dfb.frx@firenze.linux.it> (raw)
In-Reply-To: <20040602121916.GA8781@dominikbrodowski.de>


[-- Attachment #1.1: Type: text/plain, Size: 787 bytes --]

On Wed, 2 Jun 2004 14:19:17 +0200 Dominik Brodowski wrote:

> > because I'm going to try to recommend how FC2 should support Crusoe
> > and processors with longrun support.
> 
> FC2 should not try to run cpuspeed on crusoe processors, but
> 
> select "powersave" as policy [a.k.a scaling_governor] when on battery,
> and select "performance" as policy [a.k.a scaling_governor] when on
> AC. 
> 
> That's all.

You can easily do this (and much more) with Cpufreqd:
http://sourceforge.net/projects/cpufreqd/

-- 
             |  GnuPG Key ID = DD6DFCF4 | You're compiling a program
  Francesco  |        Key fingerprint = | and, all of a sudden, boom!
     Poli    | C979 F34B 27CE 5CD8 DC12 |         -- from APT HOWTO,
             | 31B5 78F4 279B DD6D FCF4 |             version 1.8.0

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  parent reply	other threads:[~2004-06-02 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01  3:40 userspace not supported for longrun? Wayne Wylupski
2004-06-01  9:31 ` Bruno Ducrot
2004-06-01 23:52   ` Wayne Wylupski
2004-06-02  9:30     ` Bruno Ducrot
2004-06-02 12:19     ` Dominik Brodowski
2004-06-02 13:28       ` Bruno Ducrot
2004-06-03  4:18         ` Wayne Wylupski
2004-06-02 15:39       ` Francesco Poli [this message]
2004-06-02 12:40 ` Dominik Brodowski

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=20040602173926.70a07dfb.frx@firenze.linux.it \
    --to=frx@firenze.linux.it \
    --cc=cpufreq@www.linux.org.uk \
    /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