> The interface to userspace is /proc/cpufreq, and the user can "echo" a new
> policy into this file using the following syntax:
> [cpu:]min_freq:max_freq:policy or
> [cpu%]min_pctg%max_pctg%policy
Should we have both in kernel?
How does it interact with ACPI? Ie. I do echo "100%100%foo", but ACPI thermal
managment decides to slow down?
> Patch 3/5: cpufreq-i386-drivers
> -------------------------------
> Six i386 CPUFreq drivers are ready to be merged this time. These are:
> elanfreq.c: The AMD Elan CPU family offers extensive clock scaling
> longhaul.c: VIA Longhaul processor clock + voltage scaling
> longrun.c: Transmeta Crusoe Longrun clock + voltage scaling
> p4-clockmod.c: clock modulation on P4 Xeon processors
> powernow-k6.c: mobile AMD K6-2+ / mobile AMD K6-3+ clock scaling
> speedstep.c: clock and voltage scaling on mobile Intel Pentium 3 and 4s,
> but (unfortunately) only on ICH2-M or ICH3-M based
> chipsets.
>
> Support for mobile AMD K7 processors is still in development.
What about mobile celerons?
Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- 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/