summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2005-02-15 09:59:10 +0000
committerEric S. Raymond <esr@thyrsus.com>2005-02-15 09:59:10 +0000
commit88fd76b730724b7f96293863545c0e123da9bf68 (patch)
tree306444be65f4499da6066c5d941fcc1c27e2cee6
parent3521c4a16289ac25e86dd2d2c75e494c29f018c8 (diff)
downloadgpsd-88fd76b730724b7f96293863545c0e123da9bf68.tar.gz
Update our to-do list.
-rw-r--r--TODO53
1 files changed, 6 insertions, 47 deletions
diff --git a/TODO b/TODO
index ffda898c..a7642c3d 100644
--- a/TODO
+++ b/TODO
@@ -1,52 +1,11 @@
* Things to do:
-** On some systems gpsd doesn't pull DTR low when closing the GPS.
-
-Reported by Robert E. Anderson <rea@q.sr.unh.edu>. He tells us this seems
-to have been introduced since 1.98. The 1.98 code looked like this:
-
-void serial_close()
-{
- if (ttyfd != -1) {
- if (isatty(ttyfd)) {
-#if defined (USE_TERMIO)
- ttyset.c_cflag = CBAUD & B0;
-#else
- ttyset.c_ispeed = B0;
- ttyset.c_ospeed = B0;
-#endif
- tcsetattr(ttyfd, TCSANOW, &ttyset);
- }
- /* Restore original terminal parameters */
- /* but make sure DTR goes down */
- ttyset_old.c_cflag |= HUPCL;
- tcsetattr(ttyfd,TCSANOW,&ttyset_old);
-
- close(ttyfd);
- ttyfd = -1;
- }
-}
-
-The new code looks like this:
-
-void gpsd_close(struct gps_session_t *session)
-{
- if (session->gNMEAdata.gps_fd != -1) {
- if (isatty(session->gNMEAdata.gps_fd)) {
- /* force hangup on close on systems that don't do HUPCL properly */
- cfsetispeed(&session->ttyset, (speed_t)B0);
- cfsetospeed(&session->ttyset, (speed_t)B0);
- tcsetattr(session->gNMEAdata.gps_fd, TCSANOW, &session->ttyset);
- }
- /* this is the clean way to do it */
- session->ttyset_old.c_cflag |= HUPCL;
- tcsetattr(session->gNMEAdata.gps_fd,TCSANOW,&session->ttyset_old);
- close(session->gNMEAdata.gps_fd);
- }
-}
-
-It looks as though there may be something wrong with cfsetispeed() and/or
-cfsetospeed() in rea's environment.
+** Figure out how to probe for whether the GPS is a SiRF-II or not.
+
+Shipping $PSRF105,0*3E\r\n ought to elicit an $Ack 105 response
+from SiRF-II chipsets, but I haven't been able to make this work yet.
+We'd get several things from this, including knowing when we can change
+baud rates.
** Do the research to figure out just what the heck is going on with status bits