cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Georg Sauthoff <g_sauthoff@web.de>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Pentium M and 2.4. kernel: does not work
Date: Sat, 16 Aug 2003 20:53:20 +0200	[thread overview]
Message-ID: <20030816185320.GA833@brodo.de> (raw)
In-Reply-To: <200308161028.50976.g_sauthoff@web.de>

On Sat, Aug 16, 2003 at 10:28:50AM +0200, Georg Sauthoff wrote:
> > So,
> > # echo -n "0%0%100%userspace" > /proc/cpufreq
>              ^^^^^^^^ What does this mean?

set the CPU 0  0%
to something between
                 0%
and                100%
and let the             userspace
governor decide which speed to use in between. It's much easier with the
2.6. sysfs interface -- one of the reasons I'm not really too excited about
the cpufreq backport for 2.4. [besides, I _only_ use 2.[56] kernels...]

> > 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.

Probably a BUG I introduced in the latest backport. Hopefully I'll have
the time tomorrow to update it. In the meantime: what does /proc/cpufreq
tell?

	Dominik

  reply	other threads:[~2003-08-16 18:53 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
2003-08-16 18:53     ` Dominik Brodowski [this message]
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=20030816185320.GA833@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=g_sauthoff@web.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