From bc3534cb3319e1045a2c300b52cc6689e4134a0e Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Thu, 10 Oct 2013 22:42:22 -0400 Subject: Update some documentation. --- www/hacking.html.in | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) (limited to 'www/hacking.html.in') diff --git a/www/hacking.html.in b/www/hacking.html.in index 3345946a..a907eefb 100644 --- a/www/hacking.html.in +++ b/www/hacking.html.in @@ -1214,13 +1214,11 @@ packet state machine in packet.c recognizes a special packet type, or watches for. When that string is recognized at the start of a line, the interpreter switches to its driver.

-

When a driver switch takes place, the old driver's wrapup method is -called. Then the new driver's initializer method is called.

- -

A good thing to send from the NMEA probe_subtype method is probe +

A good thing to send from the NMEA confgure-event code 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.

+native-mode driver, or a response which has an identifiable binary +packet type.

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 @@ -1237,7 +1235,7 @@ with the driver. It will look through the list of drivers compiled in to find the (first) one that handles that packet type.

If you have to add a new packet type to packet.c, add tests for the -type to the TESTMAIN code.

+type to the test_packet.c code.

Probe-detect methods are intended for drivers that don't use the packet getter because they read from a device with special kernel support. -- cgit v1.2.1