From: Pavel Machek <pavel@ucw.cz>
To: dual_bereta_r0x@arenanetwork.com.br,
linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: 2.6.2: P4 ClockMod speed
Date: Wed, 25 Feb 2004 18:43:27 +0100 [thread overview]
Message-ID: <20040225174326.GD1214@elf.ucw.cz> (raw)
In-Reply-To: <20040216213435.GA9680@dominikbrodowski.de>
Hi!
> By doing so it becomes easier to enter different frequencies e.g. into
> /sys/devices/system/cpu/cpufreq/scaling_setspeed -- on my desktop, typing in
> 1200000 is easier than 12121224... [*]
...
> [*] The _actual_ CPU speed should be used on all cpufreq drivers where this
> specific CPU frequency has implications to external components, e.g. LCD,
> memory or pcmcia devices. Where only the _frequency ratio_ is of importance
> [for loops_per_jiffy and friends] such "rounding" is acceptable, as long as
> the ratio is constant.
Hey, that's ugly. Values should be real.
If you have troubles typing real frequency, you can either use
/proc/cpufreq and specify values in percent, or modify
scaling_setspeed to go for nearest lower frequency, or create bash
scripts "hi_speed" and "low_speed"; but please don't break
interface....
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-02-25 17:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 21:34 2.6.2: P4 ClockMod speed Dominik Brodowski
2004-02-16 21:34 ` Dominik Brodowski
2004-02-16 21:48 ` dual_bereta_r0x
2004-02-16 21:57 ` Bruno Ducrot
2004-02-17 9:09 ` Dominik Brodowski
2004-02-17 9:09 ` Dominik Brodowski
2004-02-26 1:28 ` dual_bereta_r0x
2004-03-03 19:12 ` Bruno Ducrot
2004-03-14 14:44 ` Dominik Brodowski
2004-03-14 21:23 ` Pavel Machek
2004-03-15 9:26 ` Dominik Brodowski
2004-03-15 12:44 ` Pavel Machek
2004-03-15 13:59 ` Dominik Brodowski
2004-03-15 19:02 ` Pavel Machek
2004-02-25 17:43 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-16 19:23 dual_bereta_r0x
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=20040225174326.GD1214@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=cpufreq@www.linux.org.uk \
--cc=dual_bereta_r0x@arenanetwork.com.br \
--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 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.