[lkml]   [2001]   [Nov]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: VIA 686 timer bugfix incomplete
Vojtech Pavlik wrote:
> On Thu, Nov 08, 2001 at 10:21:24AM +0100, Jonas Diemer wrote:
> > Well, then maybe Vojtech's suggestion is best: use RTC for timing, not the
> > chipset...
> > as to my knowledge, every i38 system has a standard RTC, so why not use this? or
> > even better: make an option in the config to choose whether use RTC or the
> > chipset.
> There is a little problem with RTC, though:
> While you can set it up to generate interrupts at say 1024 Hz, you can't
> read any value of how much time passed since last interrupt. You can do
> this on the PIT (i8253), and this is the part that is buggy.
> TSC is perfect, precise and accurate, but not reliable in long term.
> Some CPUs do thermal throttling, notebooks play with CPU speed, etc,
> etc. And it's not synchronized to any interrupt source.
> Ugly, ugly, ugly is the PC architecture.
Me thinks the real solution is the ACPI pm timer. 3 times the
resolution of the PIT and you can not stop it. The high-res-timers
patch will allow you to use this as the time keeper and just use the PIT
to generate interrupts.

Finding the ACPI pm timer, on the other hand, is MOST obscure and not
all x86 platforms have ACPI. Still, we are almost there.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:13    [W:0.075 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site