From: Ducrot Bruno <ducrot@poupinou.org>
To: Michael Frank <mflt1@micrologica.com.hk>
Cc: Luigi Belli <lbelli@crema.unimi.it>, cpufreq@www.linux.org.uk
Subject: Re: Cpufreq: powernow-k7 weirdness
Date: Mon, 7 Jul 2003 15:12:52 +0200 [thread overview]
Message-ID: <20030707131252.GC7796@poupinou.org> (raw)
In-Reply-To: <200307071129.46683.mflt1@micrologica.com.hk>
> The actual minimum time between steps depends on systems design and can
> only be established by watching the (core) voltage on an oscilloscope
> while modulating cpufreq/ACPI settings. The time used should be double
> or triple the minimum for longterm stability. It would be better if
> Mainboard manufacturers would specify this minimum time.
That is suposed to be done via a BIOS table (with signature
AMDK7PNOW!) for the powernow-k7 driver, but is used for the
CPU only (I believe), and I guess that anyway this occur
only when a valid core voltage is applied to the CPU (well,
I hope).
But perhaps this table do not give appropriate values on some system?
Actually, I was wondering why the _PSS method (from ACPI) give
a settling time of 125us, instead of 100us for some systems.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2003-07-07 13:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-06 1:00 Cpufreq: powernow-k7 weirdness Juliusz Chroboczek
2003-07-06 1:21 ` Ducrot Bruno
2003-07-06 17:11 ` Carl Thompson
2003-07-06 17:28 ` Jay Goodman Tamboli
2003-07-06 17:43 ` Carl Thompson
2003-07-06 18:48 ` Ducrot Bruno
2003-07-06 21:56 ` Luigi Belli
2003-07-07 4:16 ` Michael Frank
2003-07-07 13:12 ` Ducrot Bruno [this message]
2003-07-07 15:06 ` Michael Frank
2003-07-07 16:32 ` Daniel Thor Kristjansson
2003-07-07 12:58 ` Juliusz Chroboczek
2003-07-07 13:32 ` Ducrot Bruno
2003-07-07 17:32 ` Dave Jones
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=20030707131252.GC7796@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=lbelli@crema.unimi.it \
--cc=mflt1@micrologica.com.hk \
/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.