Re: [gpsd-dev] SHM refclock improvements

[Gary E. Miller]

Yo Miroslav!

On Wed, 29 Aug 2012 11:03:22 +0200
Miroslav Lichvar <address@hidden> wrote:

> Allocate two ints from the dummy array for clockTimeStampNSec and
> receiveTimeStampNSec, the client fills all usecs and nsecs fields, and
> the server uses the nsec fields only if nsec / 1000 == usec. That's
> it. If they match by accident, it's noise below microsecond.

I checked gpsd and the entire shmTime structure is first zeroed before
use.  So that should work and be forward/back compatible.  I could add
that to gpsd git in a few minutes.

As long as we know an 'int' will be at least 4 bytes.  Do we know that?

> For the other issues with SHM, if they really cause some problems,
> it's probably better to make a new protocol from scratch instead of
> trying to extend SHM.

Yes, long term getting off of SHM is a good idea.  Short term we
can patch SHM.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
        address@hidden  Tel:+1(541)382-8588

signature.asc
Description: PGP signature