[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] RC for DRIFT message
From: |
Gary E. Miller |
Subject: |
Re: [gpsd-dev] RC for DRIFT message |
Date: |
Mon, 23 Feb 2015 12:20:44 -0800 |
Yo Hal!
On Mon, 23 Feb 2015 00:30:47 -0800
Hal Murray <address@hidden> wrote:
>
> > The idea of writing a HOWTO is an excellent one, thank you. I
> > believe I am well equipped to do it, and it would be good
> > battlespace preparation for redesigning the reporting mechanism to
> > NTP.
>
> Please don't limit yourself to NTP. That's all the current SHM
> implementation supports, but there is no reason that all the
> navigation info currently sent via JSON/TCP can't be passed via SHM,
> Pipes, or IPC queues. (There might be practical size limits I don't
> know about.)
3.12 also passes gps_device_t as shmid: 0x47505344 (GPSD). Until
it gets some use no way to say it is solid yet.
> You might think about ways to plot other stuff, say temperature.
Yeah, motherboard temp might be a proxy for motherboard crystal. I
see strong temp effects on my timekeeping.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97701
address@hidden Tel:+1(541)382-8588
- Re: [gpsd-dev] RC for DRIFT message, (continued)
- Re: [gpsd-dev] RC for DRIFT message, Hal Murray, 2015/02/22
- Re: [gpsd-dev] RC for DRIFT message, Eric S. Raymond, 2015/02/23
- Re: [gpsd-dev] RC for DRIFT message, Hal Murray, 2015/02/23
- Re: [gpsd-dev] RC for DRIFT message, Eric S. Raymond, 2015/02/23
- Re: [gpsd-dev] RC for DRIFT message, Hal Murray, 2015/02/24
- Re: [gpsd-dev] RC for DRIFT message, Eric S. Raymond, 2015/02/24
- Re: [gpsd-dev] RC for DRIFT message, Hal Murray, 2015/02/25
- Re: [gpsd-dev] RC for DRIFT message, Gary E. Miller, 2015/02/25
- Re: [gpsd-dev] RC for DRIFT message, Eric S. Raymond, 2015/02/26
- Re: [gpsd-dev] RC for DRIFT message,
Gary E. Miller <=
Re: [gpsd-dev] RC for DRIFT message, Greg Troxel, 2015/02/22