summaryrefslogtreecommitdiffstats
path: root/sys/dev/acpica/acpi_timer.c
diff options
context:
space:
mode:
authordillon <dillon@FreeBSD.org>2002-02-24 22:58:15 +0000
committerdillon <dillon@FreeBSD.org>2002-02-24 22:58:15 +0000
commitb4c7fcd8a53e22daec42a622f070f3783dd7ce7a (patch)
tree2ce16b2b434102c3be7c000763ffedb7cf2f259b /sys/dev/acpica/acpi_timer.c
parent9bd838c13d3c43c88d0f8975b2c8752a69d28230 (diff)
downloadFreeBSD-src-b4c7fcd8a53e22daec42a622f070f3783dd7ce7a.zip
FreeBSD-src-b4c7fcd8a53e22daec42a622f070f3783dd7ce7a.tar.gz
Tests by numerous people have shown that many chipsets do not properly
latch the acpi timer, resulting in weird deltas. The problem is severe enough to adversely effect the timecounter code. Default to the 'safe' version of the get-timecount function. The probe will override it if a known-good chipset is found. This is temporary until a more complete solution is found. Reviewed by: phk
Diffstat (limited to 'sys/dev/acpica/acpi_timer.c')
-rw-r--r--sys/dev/acpica/acpi_timer.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/dev/acpica/acpi_timer.c b/sys/dev/acpica/acpi_timer.c
index 4afec1b..6de7641 100644
--- a/sys/dev/acpica/acpi_timer.c
+++ b/sys/dev/acpica/acpi_timer.c
@@ -138,7 +138,7 @@ acpi_timer_identify(driver_t *driver, device_t parent)
if (getenv("debug.acpi.timer_test") != NULL)
acpi_timer_test();
- acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount;
+ acpi_timer_timecounter.tc_get_timecount = acpi_timer_get_timecount_safe;
acpi_timer_timecounter.tc_frequency = acpi_timer_frequency;
tc_init(&acpi_timer_timecounter);
OpenPOWER on IntegriCloud