On 02/18/2011 12:58 AM, Rogério Brito wrote:
On Dec 16 2010, Phillip Susi wrote:
Powernowd used to accomplish the same thing as ACPI P-states by
directly manipulating the amd k8 cpu registers.
No, it doesn't. It is just a userspace governor and, despite the name,
it is not tied to AMD cpus.
That is what it does NOW. It USED TO directly manipulate the k8 cpu
registers, which is where it got its name.
Unless you happen to have a CPU (Intel, BTW) that can only have its
frequency scaled using something other than ondemand/conservative in
their stock form and you have to use the P4 clock modulation.
To my understanding, p4_clockmod is just another frequency scaling
driver in the kernel for very old p4 cpus, and all of the governors work
with it like any of the other scaling drivers.
I have some patches to the ondemand cpufreq regulator, but it will need
a lot of fine tuning to make ondemand work (if at all). OTOH, using
powernowd usually works OK for my computer.
Can you be more specific? Why doesn't ondemand work with p4_clockmod?
And I am not even talking about some other architectures (e.g., PowerPC)
where there is some support for frequency scaling, but where there is no
ACPI.
Such architectures support frequency scaling via a frequency scaling
driver. As you said before, all that powernowd does is govern that
driver. The kernel's own governors should work better.
I think that I may not (yet) be willing to adopt it, but I am sure
willing to co-maintain it or make the occasional QA upload from time to
time, so that I can keep things in shape and close some of the most
pressing bugs.
If it doesn't work now, why not get the kernel governor working right
instead?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
