[lkml]   [2003]   [Feb]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Select voltage manually in cpufreq
On Tue, Feb 18, 2003 at 02:08:58PM -0800, Chris Wedgwood wrote:
> On Tue, Feb 18, 2003 at 10:58:19PM +0100, Pavel Machek wrote:
> > Well, and does slow-low-power mean 300MHz, 1.4V as bios said, or
> > 300MHz, 1.2V which is probably also safe?
> I have no idea... that's the point... the user almost never knows what
> *exact* magic values are required, they just want fast-on-power or
> slow-on-battery sort of thing.

One possibility is a database of known-safe overrides for specific
models of laptops. We *could* even do DMI based overrides which make
cpufreq point at an in-module PST instead of BIOS. That in-module PST
would be machine-independant, and would need to be derived by someone
like Pavel using a patch pretty much like the one he proposed to do
trial and error testing. The only thing I'm concerned about with that
approach is the risk of possible damage.

longhaul will allow you to overclock/overpower the cpu. I've never
actually damaged a C3 in this way, just locked it up needing a
power-cycle. powernow-k7 clips in hardware to the maximum the cpu
is capable of. Specifying too low a voltage also seems to universally
lock up the box. Those are the implementations I know about, so unless
any of the other implementations allow dangerous operations, we should
be 'mostly harmless' right now.


| Dave Jones.
| SuSE Labs
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.042 / U:3.564 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site