HEADSUP: cpufreq import complete, acpi_throttling changed

[Nate Lawson]

Michael W. Oliver wrote:
> On 2005-02-06T13:21:32-0800, Nate Lawson wrote:
> 
>>I've finished the major work of importing cpufreq.  As part of this, the 
>>sysctls for acpi throttling have been removed.  The power_profile script 
>>has been updated, so you can use performance/economy_cpu_freq= in 
>>rc.conf to set AC on/offline cpu frequencies.  The acpi throttling 
>>support has been compiled into acpi_perf.ko so load that to get 
>>throttling.  Do a sysctl dev.cpu to get an understanding of the cpufreq 
>>sysctls.
> 
> 
> Nate,
> 
> Thanks for the hard work on cpufreq!  I am running an AMD64 3400 CPU in
> my lappy, and I don't see any difference in dev.cpu with cpufreq and/or
> acpi_perf loaded.  This is all I have:
> 
> dev.cpu.0.%desc: ACPI CPU (2 Cx states)
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> 
> The above is the same for the following conditions:
> 
>  o cpufreq AND acpi_perf NOT loaded
>  o cpufreq (without acpi_perf) loaded
>  o acpi_perf (without cpufreq) loaded
>  o cpufreq AND acpi_perf loaded
> 
> The acpi_ppc module does continue to work for me, however, yielding the
> following additional OIDs from hw.acpi:

A powernow driver will be imported at some point.  I hope the maintainer 
  will do this and it looks like he might but I'll let him speak for 
himself.  Once that's in, your functionality will appear.

> Also, I had to build the cpufreq and acpi_perf modules manually, as they
> weren't built automatically.  Maybe they aren't "connected" to the build
> for AMD64?

Another developer unhooked them from the build because of a temporary 
build problem.  Since there's no useful driver for amd64 yet, I'll wait 
until more are imported to hook it back up to the build.

Thanks,
-- 
Nate