Poul-Henning Kamp dad3b6c6fd Back in the good old days, PC's had random pieces of rock for ... frequency generation and what frequency the generated was anyones guess. In general the 32.768kHz RTC clock x-tal was the best, because that was a regular wrist-watch Xtal, whereas the X-tal generating the ISA bus frequency was much lower quality, often costing as much as several cents a piece, so it made good sense to check the ISA bus frequency against the RTC clock. The other relevant property of those machines, is that they typically had no more than 16MB RAM. These days, CPU chips croak if their clocks are not tightly within specs and all necessary frequencies are derived from the master crystal by means if PLL's. Considering that it takes on average 1.5 second to calibrate the frequency of the i8254 counter, that more likely than not, we will not actually use the result of the calibration, and as the final clincher, we seldom use the i8254 for anything besides BEL in syscons anyway, it has become time to drop the calibration code. If you need to tell the system what frequency your i8254 runs, you can do so from the loader using hw.i8254.freq or using the sysctl kern.timecounter.tc.i8254.frequency.		2008-03-26 22:12:00 +00:00
..
atrtc.c	Back in the good old days, PC's had random pieces of rock for	2008-03-26 22:12:00 +00:00
isa_common.c
isa_common.h
isa_dmareg.h
isa_if.m
isahint.c
isareg.h
isavar.h
orm.c
pnp.c
pnpparse.c
pnpreg.h
pnpvar.h
rtc.h
syscons_isa.c	Further cleanup of sound generation in syscons:	2008-03-26 22:02:51 +00:00
vga_isa.c	Replace explicit calls to video methods with their respective variants	2007-12-29 23:26:59 +00:00