All of lore.kernel.org
 help / color / mirror / Atom feed
From: Georg Sauthoff <g_sauthoff@web.de>
To: cpufreq@www.linux.org.uk
Subject: Re: Pentium M and 2.4. kernel: does not work
Date: Sat, 16 Aug 2003 10:28:50 +0200	[thread overview]
Message-ID: <200308161028.50976.g_sauthoff@web.de> (raw)
In-Reply-To: <20030815213028.GB1738@brodo.de>

On Friday 15 August 2003 23:30, Dominik Brodowski wrote:
> That's not a bug, it's a feature. If you want to set the CPU frequency
> manually, you need to enable this "governor" first. [Other "governors" set
> to lowest and highest speed permanently (powersave/performance), and there
> could be many more such "governors" which adapt the CPU frequency to
> current system load etc. These only need to be written....]

Ok, I did not do RTMF enough I think ...

> So,
> # echo -n "0%0%100%userspace" > /proc/cpufreq
             ^^^^^^^^ What does this mean?

> first, then you can use the
> /proc/sys/cpu/0/speed
> file to set the CPU speed manually.

Hm, unfortunetly after I set the userspace governor (like above) the 
/proc/sys/cpu/0/s* gives me 0 again ...

In the kernel logs I don't see any messages from cpufreq. Ok, after a very 
quick look at the patch sources I don't see printk's there, too.

Regards
Georg Sauthoff

  parent reply	other threads:[~2003-08-16  8:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15 22:43 Pentium M and 2.4. kernel: does not work Georg Sauthoff
2003-08-15 21:30 ` Dominik Brodowski
2003-08-16  7:34   ` Jeremy Fitzhardinge
2003-08-16 18:54     ` Dominik Brodowski
2003-08-16  8:28   ` Georg Sauthoff [this message]
2003-08-16 18:53     ` Dominik Brodowski
2003-08-16 19:57       ` Georg Sauthoff
2003-08-17 21:09         ` Georg Sauthoff
     [not found]           ` <20030818175051.GA1570@brodo.de>
2003-08-18 18:51             ` Georg Sauthoff

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=200308161028.50976.g_sauthoff@web.de \
    --to=g_sauthoff@web.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.