[lkml]   [2006]   [Nov]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: NTP time sync
On Wed, Nov 22, 2006 at 09:23:55PM +0100, Alessandro Zummo wrote:
> On Wed, 22 Nov 2006 11:55:23 -0800
> David Brownell <> wrote:
> > >
> > > So, if the arch maintainers agree,
> > > I would suggest to schedule it for removal.
> > >
> > > [1]
> >
> > Suggested time of removal: one year after two relevant software
> > package releases get updated:
> >
> > - NTPD, to call hwclock specifying the relevant RTC;
> This might introduce delays. ntpd might open the device
> and update the time itself.

Indeed, the update should be at least _triggered_ by ntp.

In the end it will be the kernel that accesses the hardware,
the fundamental problem is that with RTC chips with very slow
access like I2C it cannot be done from an interrupt.

But it nevertheless has to be done as close as possible
to the half-second or second boundary (depending on the chip)
boundary if we want to keep some precision. You can't expect
miracles from RTC chips in this respect, since the crystal
period is about 30µs to boot and from some tests I did a long
time ago it seems that most do not reset the first bits of
the divider when written to, so the precision is much worse
(something like 30ms IIRC). It is still much better than 1
second in any case.

How can ntp know if the RTC chip has to be updated at the
half-second or second boundary? That is the kind of knowledge
that is better left to the driver.

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: 2006-11-23 02:53    [W:0.030 / U:32.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site