On Tue, Feb 25, 2003 at 07:03:11PM +0100, Pavel Machek wrote:
> Hi!
>
> Well, look again; if you use mVforce, it forces *just one* frequency
> (min=max=freq you specified), so it is actually okay.
But min=max=freq is awful... I know, I reccommended it sometimes, but with
the appearance of the userspace governor (already available on the cpufreq
homepage, http://www.brodo.de/cpufreq/advanced.html , will be submitted
soon) min=max=freq is deprecated.
> But I agree that hacking proc_intf is not the right thing to do. I did
> not see that sysfs access. Where is it?
kernel/cpufreq.c
> > - selecting the voltage manually is something which is only valid for some
> > very few drivers - so let's only export one sysfs file[*] for these
> > drivers.
>
> Very few drivers? It should be common for at least Intel and AMD, no?
No. Intel doesn't let you select the exact voltage. IIRC, only vew
VIA/Cyrix-longhaul-capable processors and, of course, powernow-k7 are vaild
targets for such a patch.
Dominik
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/