http://bugzilla.kernel.org/show_bug.cgi?id=14066 Summary: p4_clockmod unusable with ondemand even by manual choice Product: Power Management Version: 2.5 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: cpufreq AssignedTo: cpufreq@xxxxxxxxxxxxxxx ReportedBy: nemesis@xxxxxxxxxxxx Regression: No The following patch: [CPUFREQ] Prevent p4-clockmod from auto-binding to the ondemand governor certainly seems like a good idea. No reason to use an inefficient governor by default. However, as a side effect, setting the transition latency to this value makes it impossible for the user to _choose_ to use ondemand even when it is the best choice for his environment. On a Celeron-M processor, ondemand is useful for reducing heat output and keeping the fan from turning on all the time, and p4_clockmod is the only module that works for such processors. Until 2.6.29 this was a very useful thing. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
