diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2006-10-30 11:36:06 +0000 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2006-10-30 11:36:06 +0000 |
commit | e88d740ff5fecb3a6cad327b48dd1b85c5cf1f63 (patch) | |
tree | 4e4a2f24844417ba81d8419736f8aea8c6c35523 /www | |
parent | f6519ca132b92c29874b40079ca1f5d07ecd0676 (diff) | |
download | gpsd-e88d740ff5fecb3a6cad327b48dd1b85c5cf1f63.tar.gz |
Rename some methods for clarity.
Diffstat (limited to 'www')
-rw-r--r-- | www/hacking.html | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/www/hacking.html b/www/hacking.html index 151e5363..990cf1ea 100644 --- a/www/hacking.html +++ b/www/hacking.html @@ -778,9 +778,10 @@ line, the interpreter switches to its driver.</p> <p>When a driver switch takes place, the old driver's wrapup method is called. Then the new driver's initializer method is called.</p> -<p>A good thing to send from the NMEA initializer is probe strings. These are -strings which should elicit an identifying response from the GPS that -you can use as a trigger string for a native-mode driver.</p> +<p>A good thing to send from the NMEA probe_subtype method is probe +strings. These are strings which should elicit an identifying +response from the GPS that you can use as a trigger string for a +native-mode driver.</p> <p>Don't worry about probe strings messing up GPSes they aren't meant for. In general, all GPSes have rather rigidly defined packet formats with @@ -809,7 +810,7 @@ See the Garmin binary driver for an example.</p> <h3 id="reports">Where to put the data you get from the GPS</h3> <p>Your driver should put new data from each incoming packet or sentence -in the 'newdata' member of the GPS, and return a validity flag mask +in the 'gpsdata' member of the GPS, and return a validity flag mask telling what members were updated (all float members are initially set --> to not-a-number. as well). There is driver-independent code that will be responsible for merging that new data into the existing |