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
This commit is contained in:
parent
3f7ad4d593
commit
d32e27a9f4
@ -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);
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user