Re: [PATCH] LinuxPPS (with new syscalls API) - new version

[Roman Zippel <zippel@linux-m68k.org>]

Hi,

On Wed, 11 Jul 2007, Lennart Sorensen wrote:

> On Wed, Jul 11, 2007 at 03:18:46AM +0200, Roman Zippel wrote:
> > This is really not an API that needs to deal with such large time range.
> 
> No one will want to use PPS API to keep accurate time past 2030?  Why
> not?  Or should we be forced to invent a new PPS API before then to fix
> this one?

That's not necessary.

> Actually, come to think of it, is this passing a current time, or it it
> passing an interval since last PPS?  If it is an interval, then yes
> never mind, we don't need that many seconds (usually 1 or 2 at most).
> For some reason I thought this was for passing the current time of a
> stamp.

It's an absolute time stamp, but users of this interface are more 
interested in the time difference between events and how they change over 
time. E.g. NTP time stamps are 64bit fixed point values with a 32bit 
integral part.
This is not an interface to read the current system time, so 32bit will 
continue to work.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/