diff options
author | Jon Schlueter <jon.schlueter@gmail.com> | 2010-04-29 19:19:06 -0400 |
---|---|---|
committer | Jon Schlueter <jon.schlueter@gmail.com> | 2010-04-29 19:19:06 -0400 |
commit | 365ed18bccd859533bc15ed444d631ae8db956ea (patch) | |
tree | cf3cdd2208ee42193eb0965cb0fb3fe6a3501e7a /driver_sirf.c | |
parent | ec2e285be32fbf5d8190e668179c62e92c779fbd (diff) | |
download | gpsd-365ed18bccd859533bc15ed444d631ae8db956ea.tar.gz |
Whitespace and indenting cleanup.
In bits.c gpsd.c gpsd_json.c and several drivers.
Regression tests passing.
Diffstat (limited to 'driver_sirf.c')
-rw-r--r-- | driver_sirf.c | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/driver_sirf.c b/driver_sirf.c index 925c6541..1d898d03 100644 --- a/driver_sirf.c +++ b/driver_sirf.c @@ -6,7 +6,7 @@ * The disadvantages: Doesn't return PDOP or VDOP, just HDOP. * * Chris Kuethe, our SiRF expert, tells us: - * + * * "I don't see any indication in any of my material that PDOP, GDOP * or VDOP are output. There are quantities called Estimated * {Horizontal Position, Vertical Position, Time, Horizonal Velocity} @@ -14,9 +14,9 @@ * active." * * "(SiRFdrive is their Dead Reckoning augmented firmware. It - * allows you to feed odometer ticks, gyro and possibly - * accelerometer inputs to the chip to allow it to continue - * to navigate in the absence of satellite information, and + * allows you to feed odometer ticks, gyro and possibly + * accelerometer inputs to the chip to allow it to continue + * to navigate in the absence of satellite information, and * to improve fixes when you do have satellites.)" * * "[When we need RINEX data, we can get it from] SiRF Message #5. @@ -49,7 +49,7 @@ #ifdef ALLOW_RECONFIGURE /*@ +charint @*/ -/* message to enable: +/* message to enable: * MID 7 Clock Status * MID 8 50Bps subframe data * MID 17 Differential Corrections @@ -201,8 +201,8 @@ static bool sirf_speed(int ttyfd, speed_t speed, char parity, int stopbits) /*@ +charint @*/ static unsigned char msg[] = { 0xa0, 0xa2, 0x00, 0x09, - 0x86, /* byte 4: - * Set Binary Serial Port + 0x86, /* byte 4: + * Set Binary Serial Port * MID 134 */ 0x00, 0x00, 0x12, 0xc0, /* bytes 5-8: 4800 bps */ 0x08, /* byte 9: 8 data bits */ @@ -523,7 +523,7 @@ static gps_mask_t sirf_msg_svinfo(struct gps_device_t *session, session->driver.sirf.time_seen |= TIME_SEEN_GPS_1; mask |= TIME_IS; /* - * This time stamp, at 4800bps, is so close to 1 sec old as to + * This time stamp, at 4800bps, is so close to 1 sec old as to * be confusing to ntpd, but ntpshm_put() will ignore it if a better * time already seen */ @@ -660,8 +660,8 @@ static gps_mask_t sirf_msg_navsol(struct gps_device_t *session, so for a while) don't report a valid time field, leading to annoying twice-per-second jitter in client displays. -2) What we wanted out of this that MND didn't give us was horizontal and - vertical error estimates. But we have to do our own error estimation by +2) What we wanted out of this that MND didn't give us was horizontal and + vertical error estimates. But we have to do our own error estimation by computing DOPs from the skyview covariance matrix anyway, because we want separate epx and epy errors a la NMEA 3.0. @@ -729,7 +729,7 @@ static gps_mask_t sirf_msg_geodetic(struct gps_device_t *session, struct tm unpacked_date; double subseconds; /* - * Early versions of the SiRF protocol manual don't document + * Early versions of the SiRF protocol manual don't document * this sentence at all. Some that do incorrectly * describe UTC Day, Hour, and Minute as 2-byte quantities, * not 1-byte. Chris Kuethe, our SiRF expert, tells us: @@ -743,10 +743,10 @@ static gps_mask_t sirf_msg_geodetic(struct gps_device_t *session, * To work around the incomplete implementation of this * packet in 231, we used to assume that only the altitude field * from this packet is valid. But even this doesn't necessarily - * seem to be the case. Instead, we do our own computation + * seem to be the case. Instead, we do our own computation * of geoid separation now. * - * UTC is left all zeros in 231 and older firmware versions, + * UTC is left all zeros in 231 and older firmware versions, * and misdocumented in version 1.4 of the Protocol Reference. * Documented: Real: * UTC year 2 2 @@ -1184,7 +1184,7 @@ static void sirfbin_event_hook(struct gps_device_t *session, event_t event) /* do this every time */ { /*@ +charint @*/ - /* Poll Navigation Parameters MID 152 + /* Poll Navigation Parameters MID 152 * query for MID 19 */ static unsigned char navparams[] = { 0xa0, 0xa2, 0x00, 0x02, |