diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2005-05-18 15:28:13 +0000 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2005-05-18 15:28:13 +0000 |
commit | c32861588b9f55b917457c4f1e9ef0ebf256abaa (patch) | |
tree | 6556d2977d2ef106a70ecb913b3b1f3ec22965eb /TODO | |
parent | a695fa769db7b47e1c35aa8bb611b1bc225f4ec7 (diff) | |
download | gpsd-c32861588b9f55b917457c4f1e9ef0ebf256abaa.tar.gz |
Update the bug list.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 45 |
1 files changed, 45 insertions, 0 deletions
@@ -1,6 +1,51 @@ This is the gpsd to-do list. If you're viewing it with Emacs, try doing Ctl-C Ctl-t and browsing through the outline headers. +** Problems with the leap-second offset + +Remco, using a SiRF chip at level 231, is still seeing a 10-second +offset in his reported GPS times. Rob Janssen and I, with the same +hardware, aren't seeing this. + +** Devicename pointer may get clobbered during very long runs + +Wallace E. Owen <owen@titan.com> and Rainer Scholz <ras@sigos.de>, +who may or may not be different people :-), have reported that after +gpsd has been running for a long time (5 hours in Rainer's original +report) something clobbers the device name and zeros it out. Rainer +seems to have established that this is due to some change introduced +between 2.21 and 2.22; I've sent him a diff which we're going to try +to whittle down until we can figure out what. + +** No data from BU-303? + +Roeland Th. Jansen <roeland@linux-it.nl> was reporting no data from +a BU-303. I have a BU-303 and it's working fine. I don't know if +he has checked out SVN head recently. + +** Design problems with he NTP interface: + +There's a messy question about how NTP shared-memory segments should +be associated with GPSes. At the moment, the code allocates just +one and all devices report through it. It would be better for each +device to have its own segment, so they look like separate time +sources to NTP and it can apply its heuristics for weeding out +the less consistent ones. + +The trouble with this is that: + +1) The default build of NTP only supports 4 segments. Thus, if we +allocate them per GPS device, we're not unlikely to run out of them. + +2) We may actually want *two* segments per device, one for message time +and one for PPS time. + +3) We can't grab new segments after privileges are dropped. + +I think we're going to be stuck with grabbing pointers to all four +segments just in case gpsd wants them, and then having control-socket +commands to bind NTP unit numbers to devices. + ** Set FIFO threshold to 1 to reduce jitter in serial-message times This can matter if you're using gpsd as a time reference. |