| H A D | kern_cpu.c | 67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
67c8649f Tue Feb 15 07:43:48 GMT 2005 Nate Lawson <njl@FreeBSD.org> When dealing with systems with no absolute drivers attached, only calibrate
the rate for the 100% state once. Afterwards, use that value for deriving
states. This should fix the problem where the calibrated frequency was
different once a switch was done, giving a different set of levels each
time. Also, properly search for the right cpufreqX device when detaching.
|