[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] Draft Time Service HOWTO is beginning to approach final f

From: Eric S. Raymond
Subject: Re: [gpsd-dev] Draft Time Service HOWTO is beginning to approach final form
Date: Fri, 25 Oct 2013 10:22:57 -0400
User-agent: Mutt/1.5.21 (2010-09-15)

Andy Walls <address@hidden>:
> I was going to hack up my GPSD to indicate a clock alarm to NTPD until I
> know my device is providing good time.

Perhaps this is a patch that should go into the main line?  I can't judge
until I know what a "clock alarm" is supposed to do.
> A Trimble distributor tech support person told me that, for my Trimble
> Condor chip, "[in] the [$GP]GLL output, UTC is not included until the
> offset has been decoded".

GPSD already checks for this.  Shipping time to ntpd is done at the end of
each fix reporting cycle; for it to happen, the active driver has to
assert a PPSTIME_IS bit in the state flags it passes back.  PPSTIME_IS
is never asserted unless we have aggregated valid time from the
current reporting cycle, but drivers can impose additional conditions.

If you look in the TSIP driver, you'll see exactly where PPSTIME_IS 
gets asserted.
                <a href="";>Eric S. Raymond</a>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]