An error occurred fetching the project authors.
- 24 Aug, 2004 1 commit
-
-
Dave Jones authored
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com> Signed-off-by: Dave Jones <davej@redhat.com>
-
- 12 Apr, 2004 1 commit
-
-
Andrew Morton authored
From: Rusty Russell <rusty@rustcorp.com.au> From: "Petri T. Koistinen" <petri.koistinen@iki.fi> 1) Various URLs in the Kconfig files are out of date: update them. 2) URLs should be of form <http://url-goes-here>. 3) References to files in the source should be of form <file:path-from-top> 4) Email addresses should be of form <foo@bar.com>
-
- 26 Feb, 2004 1 commit
-
-
Dave Jones authored
From: Russell King <rmk@arm.linux.org.uk>
-
- 05 Jan, 2004 1 commit
-
-
Dave Jones authored
-
- 07 Oct, 2003 1 commit
-
-
Dave Jones authored
Spotted by Pavel Machek.
-
- 05 Oct, 2003 1 commit
-
-
Rusty Russell authored
From: Petri Koistinen <petri.koistinen@iki.fi>
-
- 03 Sep, 2003 2 commits
-
-
Dave Jones authored
-
Dave Jones authored
Also add a config option so that the default governor [which is loaded and enabled at boot] is started. Note that if you select "performance" here, the CPU will be set to the highest possible frequency even if the CPU was booted at a lower frequency. If you select "userspace", the frequency will stay the same.
-
- 01 Mar, 2003 1 commit
-
-
Dominik Brodowski authored
The old /proc/sys/cpu/ - based interface is nothing else than a cpufreq governor which decides what frequency to use within a policy based on userspace input. So, convert this interface (and add a corresponding sysfs file, /sys/devices/sys/cpu0/scaling_setspeed) to become a cpufreq governor, and move it out to an extra module (which partly explains the size of this patch).
-
- 15 Feb, 2003 1 commit
-
-
Dominik Brodowski authored
The deprecated /proc/cpufreq interface can easily live outside the cpufreq core now.
-