From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: cpufreq@lists.linux.org.uk
Subject: RE: cpufreq: powernow-k8 frequency transitions question
Date: Tue, 03 Jan 2006 01:19:28 +0100 [thread overview]
Message-ID: <dpcfth$16q$2@sea.gmane.org> (raw)
In-Reply-To: 84EA05E2CA77634C82730353CBE3A84303D430BD@SAUSEXMB1.amd.com
Devriendt, Paul wrote:
> Transitions between low frequencies (<=1.4GHz) are not supported by
> hardware. The way to do them is to transition to an intermediate
> high frequency.
Yes, I read about that in the PDF I referred to. I guess that#s the guide
you also mentioned?
> No BIOSs define two low PStates so the case never occurs, but it could
> theoretically be done.
I'm currently experimenting with the speeds my CPU can run at. (Out of spec,
at lower frequencies and voltages to safe a few watts and keep everything
cool'n'quiet, so to say... ;)
It seems to run fine a several low pstates, I just need to check if
supporting low-low-transitions would be worth the hassle, or if I just
limit my pstate table to two pstates between which the CPU can transition
directly.
Thanks a lot for your answer,
Gunter
--
Thunder rolled. ... It rolled a six. -- (Terry Pratchett,
Guards! Guards!)
*** PGP-Verschlüsselung bei eMails erwünscht :-) *** PGP: 0x1128F25F ***
next prev parent reply other threads:[~2006-01-03 0:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 17:37 cpufreq: powernow-k8 frequency transitions question Devriendt, Paul
2006-01-03 0:19 ` Gunter Ohrner [this message]
2006-01-03 16:29 ` Bruno Ducrot
2006-01-04 0:47 ` Gunter Ohrner
2006-01-04 1:50 ` Nebojsa Trpkovic
2006-01-04 10:45 ` Bruno Ducrot
2006-01-04 13:04 ` Nebojsa Trpkovic
2006-01-07 14:31 ` Gunter Ohrner
2006-01-07 14:28 ` Gunter Ohrner
2006-01-08 2:32 ` Gunter Ohrner
-- strict thread matches above, loose matches on Subject: below --
2006-01-04 3:12 Devriendt, Paul
2006-01-01 12:13 Gunter Ohrner
2006-01-02 17:15 ` Andi Kleen
2006-01-03 0:16 ` Gunter Ohrner
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='dpcfth$16q$2@sea.gmane.org' \
--to=g.ohrner@post.rwth-aachen.de \
--cc=cpufreq@lists.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