Re: HEADSUP: cpufreq import complete, acpi_throttling changed

Jiawei Ye wrote:
> On Mon, 14 Feb 2005 08:27:01 -0800, Nate Lawson <nate_at_root.org> wrote:
> 
>>Jiawei Ye wrote:
>>cpufreq et al don't fully support unloading yet.
>>
>>--
>>Nate
>>
> 
> I've got it working, but the available frequencies seem to drift:
> root_at_chihiro:/home/leafy# sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU1
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 1819
> dev.cpu.0.freq_levels: 2355/0 2060/0 1766/0 1471/0 1177/0 883/0 588/0 294/0
> root_at_chihiro:/home/leafy# sysctl dev.cpu
> dev.cpu.0.%desc: ACPI CPU
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%location: handle=\_PR_.CPU1
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.freq: 1819
> dev.cpu.0.freq_levels: 1821/0 1593/0 1365/0 1138/0 910/0 682/0 455/0 227/0

Thanks.  This is a bug in how we handle relative-only systems (i.e., 
just acpi_throttle and no other driver).  I'll work on a fix.  The only 
effect is that the values look incorrect due to a calibration error. 
Actually using them should work properly.

-- 
Nate