diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2013-11-02 16:13:30 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2013-11-02 16:13:30 -0400 |
| commit | f489ba3ee85b4fc9ab1a25e89f597b48016354d0 (patch) | |
| tree | ced653607e497fcc00121514972e8c6613887ae9 /www | |
| parent | 76508d80374ffaa85ac4a62f04272c61a2cb2d13 (diff) | |
| download | gpsd-f489ba3ee85b4fc9ab1a25e89f597b48016354d0.tar.gz | |
gpsmon display of PPS events is now a public feature.
Diffstat (limited to 'www')
| -rw-r--r-- | www/gpsd-time-service-howto.txt | 4 | ||||
| -rw-r--r-- | www/hacking.html.in | 14 |
2 files changed, 13 insertions, 5 deletions
diff --git a/www/gpsd-time-service-howto.txt b/www/gpsd-time-service-howto.txt index d5caf619..106c8940 100644 --- a/www/gpsd-time-service-howto.txt +++ b/www/gpsd-time-service-howto.txt @@ -220,6 +220,10 @@ deliver 1PPS through USB or even RS232. Thus the usual run of cheap GPS mice won't do. In general, you can't use a USB device for time service unless you know it has the Macx-1 mod. +If you are in any doubt about whether your device has PPS +capability, point gpsmon at it. When it has a 3D fix the PPS +event reports should be obvious in the packet window. + In the past, the RS232 variant of the Garmin GPS-18 has been very commonly used for time service. While it is still a respectable choice, newer devices have better sensitivity and signal diff --git a/www/hacking.html.in b/www/hacking.html.in index f892340d..7cc71945 100644 --- a/www/hacking.html.in +++ b/www/hacking.html.in @@ -1572,24 +1572,28 @@ have to be rebuilt. The problem is in the SiRF tests; that driver relies on the default until it gets the current offset from subframe data.</p></dd> -<dt>8. Push and pull from the public repo</dt> +<dt>9. Live-test PPS</dt> +<dd><p>Point gpsmon at a GR601-W or other PPS-capable GPS and verify +that PPS events are visible.</p></dd> + +<dt>10. Push and pull from the public repo</dt> <dd><p>This is the revision the release will be built from.</p></dd> -<dt>9. Build and ship the release</dt> +<dt>11. Build and ship the release</dt> <dd><p><code>scons release</code> will tag the release, make the tarball, upload it to the hosting site, and refresh the website.</p></dd> -<dt>10. Bump the release number and push that commit</dt> +<dt>12. Bump the release number and push that commit</dt> <dd><p>Bump the release number in SConstruct, adding a '~dev' suffix so tarball instances pulled from the repo will be clearly distinguishable from the next public release.</p></dd> -<dt>11. Close all resolved tracker bugs</dt> +<dt>13. Close all resolved tracker bugs</dt> <dd><p>Go to <a href="https://savannah.nongnu.org/bugs/?group=gpsd">the tracker</a> and close all resolved bugs.</p></dd> -<dt>12. Announce the release</dt> +<dt>14. Announce the release</dt> <dd><p>Announce the release on the announce list, and the resumption of regular commits on the dev list.</p></dd> </dl> |