diff options
| author | Gary E. Miller <gem@rellim.com> | 2015-03-19 13:01:26 -0700 |
|---|---|---|
| committer | Gary E. Miller <gem@rellim.com> | 2015-03-19 13:02:50 -0700 |
| commit | 0a9de16ab3df386e67ee99ccb40ab00186b87162 (patch) | |
| tree | eb571c348e650078a0aaf2714cee8c6cc7f4f9b8 | |
| parent | 69054cab02118ee03995c2c7d80fb6afd8b7e82f (diff) | |
| download | gpsd-0a9de16ab3df386e67ee99ccb40ab00186b87162.tar.gz | |
TODO items for subtype and pps_precision
subtype is too short, expand to 128
need pps_precision to add to JSON for ntpd usage
| -rw-r--r-- | TODO | 4 | ||||
| -rw-r--r-- | gpsd_json.c | 1 |
2 files changed, 4 insertions, 1 deletions
@@ -20,7 +20,9 @@ the calibration process less annoying? ** Things to do when we can break compatibility ** -Make subtype longer. 100 chars long sounds good. +In gps_device_t Make subtype longer. 128 chars long sounds good. + +In gps_device_t, save NTP precision in pps_precision ** Bugs in gpsd and its clients: diff --git a/gpsd_json.c b/gpsd_json.c index c7ceb4d2..48c686e0 100644 --- a/gpsd_json.c +++ b/gpsd_json.c @@ -195,6 +195,7 @@ void json_tpv_dump(const struct gps_device_t *session, struct timespec clock_tmp = session->pps_thread.ppsout_last.clock; timespec_str( &clock_tmp, ts_str, sizeof(ts_str) ); str_appendf(reply, replylen, "\"pps\":%s,", ts_str); + /* TODO: add PPS precision to JSON output */ } /*@+type +formattype@*/ #endif /* PPS_ENABLE */ |