summaryrefslogtreecommitdiff
path: root/driver_rtcm3.c
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2011-06-17 02:23:58 -0400
committerEric S. Raymond <esr@thyrsus.com>2011-06-17 02:23:58 -0400
commit0d3f1eb114c9733519a25f8881b85cb81a7d37a0 (patch)
treeca41b5e9e9ca78637795fbfa5d27b0991dde588d /driver_rtcm3.c
parent730b2feea3b2da3d046b25b119375682dea5e179 (diff)
downloadgpsd-0d3f1eb114c9733519a25f8881b85cb81a7d37a0.tar.gz
Cut down on gpsd_hexdump_wrapper() calls.
This awkward construct seems to have triggered some sort of toolchain bug. The symptom is that gpsd_hexdump_level has different values depending on whether we test it inside or outside of hex.c. As a first step towards eliminating this global, we throw out a bunch of hex logging that is duplicative or not really needed for production drivers. Experimental drivers can call the hex dumper unconditionally. The goal is to reduce the number of uses of this variable to eliminate it withoud doing violence to the internal APIs. This is a first step. All regression tests pass.
Diffstat (limited to 'driver_rtcm3.c')
-rw-r--r--driver_rtcm3.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/driver_rtcm3.c b/driver_rtcm3.c
index 15920a5c..c39d3450 100644
--- a/driver_rtcm3.c
+++ b/driver_rtcm3.c
@@ -96,9 +96,8 @@ void rtcm3_unpack( /*@out@*/ struct rtcm3_t *rtcm, char *buf)
rtcm->length = (uint)ugrab(10);
rtcm->type = (uint)ugrab(12);
- gpsd_report(LOG_RAW, "RTCM3: type %d payload length %d: %s\n",
- rtcm->type, rtcm->length,
- gpsd_hexdump_wrapper(buf+3, rtcm->length, LOG_RAW));
+ gpsd_report(LOG_RAW, "RTCM3: type %d payload length %d\n",
+ rtcm->type, rtcm->length);
switch (rtcm->type) {
case 1001: /* GPS Basic RTK, L1 Only */