FWIW, I'm currently trying to find a cpu freqency daemon to default new laptop installs to in the laptop task, and powernowd is an obvious choice since:
a) More users use it than powersaved or cpufreqd, although powersaved is also rapidly gaining users, possibly because kpowersave depends on it. b) Unlike powersaved, it doesn't do other unrelated things like #372295, taking over from acpid, or trying to handle suspends on its own. Instead it does one thing and does it (presumably) well. c) it has a very simple governor requirement and setup, just needing cpufreq_userspace (or maybe some other machine specific governor like speedstep-centrino) to be loaded, compared with cpufreqd's more complex needs for various governors to be loaded depending on its configuration. d) I suspect it's somewhat more portable to powerpc although I don't know for sure. The lack of automatic module loading is the main thing preventing me from putting powernowd in the laptop task. Note that powersaved already handles autoloading modules. It probes in its init script with a fairly brute force loop. It does seem to me that it would be possible to abstract this probing out of the cpu freqency daemons, but I encourage you to go with the working and implemented solution in the meantime so that laptop installs can come with a working frequcency daemon. -- see shy jo
signature.asc
Description: Digital signature
