This commit resolves the time overflows in the rgm3800 and mkt3301.

These were causing port problems on systems with 32-bit time.  It turns
out the problem was with the assumption that these devices always
deliver a valid time in $GPRMC.  They don't when the navigation
warning bit (second field 'V') is on!  The NMEA driver now knows.

Also, the code now contains a sanity check - it will log a complaint
if it sees a date moere than a year in the future.  This invariably 
indicates some driver-level problem with time extraction.

1 files changed, 0 insertions, 11 deletions

diff --git a/TODO b/TODO
index c834cf31..3809d8f5 100644
--- a/TODO
+++ b/TODO
@@ -26,22 +26,11 @@ to reverse his refusal to send us an eval unit.
 
 *** Driver issues
 
-**** uBlox-lea-4h.log.chk: 
-
-Time value in TPVs looks like garbage. Something is probably
-off-kilter in the field extraction.
-
 **** bu303-nofix.log.ck: 
 
 Test returns a bogus altitude (large and negative) on NetBSD 5.0
 i386, but not on Intel 64. This is probably a 32-vs.64-bit port problem.
 
-**** mkt-3301.chk and rgm3800.chk:
-
-These files contain bogus timestamps with year beyond 2080.  There is
-probably something wrong with the way we extract time from these
-packets.
-
 **** navcom.chk:
 
 This testfile triggers a numeric instability in the sin() and cos()