In article <[EMAIL PROTECTED]>, "Spoon <[EMAIL PROTECTED]>" wrote:
> systohw reads the current system time, then sleeps until the next whole > second, then writes that date to the RTC. This is arguably off topic as manipulationg the RTC is incompatible with running ntpd on Linux, at least when using the kernel clock discipline code. Under these conditions, the kernel updates the RTC every 11 minutes. > However, it seems like the RTC raises the IRQ when the fraction of a > second is 0.5, not when it is 0. You can see this 0.5 second offset in the kernel code that implements the 11 minute update. You can also look at the implementation of hwclock. If you want the fine details, you should look at the data sheet for the original MSI clock and memory chip. Modern ASIC data sheets often assume that you have access to the specifications of the components that are being emulated. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
