diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2005-07-27 03:42:26 +0000 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2005-07-27 03:42:26 +0000 |
commit | dea892615bb38cf8c1ae8341b6b7a648d5309488 (patch) | |
tree | ff7b707b60eeef247840ddb7201b96324c5e450d /TODO | |
parent | 3eef1caf1de8b6532338813cbf98fcc0e51cade5 (diff) | |
download | gpsd-dea892615bb38cf8c1ae8341b6b7a648d5309488.tar.gz |
This version passes all regression tests and should serve RTCM-104 on port 2101.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 10 |
1 files changed, 3 insertions, 7 deletions
@@ -93,19 +93,15 @@ packet-cracking needed to get the data off the chips. We have an RTCM packet decoder. Here's the plan for the rest of it: -1) When there are attached RTCM104 sources, tell the daemon to serve - these packets on port 2101. At this point we will have replaced - dgpsip's server function. +1) Make the client library able to read RTCM data served from the daemon. -2) Make the client library able to read RTCM data served from the daemon. - -3) Get rid of the -d option by hacking open_device() so that when it +2) Get rid of the -d option by hacking open_device() so that when it sees a command-line option of the form server:port (with no embedded backslashes) it opens a socket to read from that server. Now any GPS-packet and RTCM data sources given on the command line can be remote as well as local. -4) Make RTCM encoding work with an 'invert' option to rtcmdecode. +3) Make RTCM encoding work with an 'invert' option to rtcmdecode. *** Do the research to figure out just what is going on with status bits |