All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: dual_bereta_r0x@arenanetwork.com.br
Cc: linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: 2.6.2: P4 ClockMod speed
Date: Mon, 16 Feb 2004 22:34:35 +0100	[thread overview]
Message-ID: <20040216213435.GA9680@dominikbrodowski.de> (raw)


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

Hi,

> I have a P4 2.4 running @ 3.12GHz.

So you overclock your CPU but then throttle it down... strange, but well...

> In 2.6.0, i could change it frequency 
> via speedfreqd(8) up to its actual speed. Since 2.6.1, its max speed is 
> locked on cpu *real* speed.

It's just a change of appearance -- the cpufreq driver uses the theoretical
speed of the CPU for its calculations; the actual CPU speed isn't
affected. You can verify this by looking at /proc/cpuinfo which still tells
3124.376 MHz.

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... [*]

	Dominik

[*] 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.

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

WARNING: multiple messages have this Message-ID (diff)
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: dual_bereta_r0x@arenanetwork.com.br
Cc: linux-kernel@vger.kernel.org, cpufreq@www.linux.org.uk
Subject: Re: 2.6.2: P4 ClockMod speed
Date: Mon, 16 Feb 2004 22:34:35 +0100	[thread overview]
Message-ID: <20040216213435.GA9680@dominikbrodowski.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]

Hi,

> I have a P4 2.4 running @ 3.12GHz.

So you overclock your CPU but then throttle it down... strange, but well...

> In 2.6.0, i could change it frequency 
> via speedfreqd(8) up to its actual speed. Since 2.6.1, its max speed is 
> locked on cpu *real* speed.

It's just a change of appearance -- the cpufreq driver uses the theoretical
speed of the CPU for its calculations; the actual CPU speed isn't
affected. You can verify this by looking at /proc/cpuinfo which still tells
3124.376 MHz.

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... [*]

	Dominik

[*] 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.

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

             reply	other threads:[~2004-02-16 21:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-16 21:34 Dominik Brodowski [this message]
2004-02-16 21:34 ` 2.6.2: P4 ClockMod speed 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
  -- 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=20040216213435.GA9680@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --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.