summaryrefslogtreecommitdiff
path: root/www/performance
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2011-09-29 06:12:17 -0400
committerEric S. Raymond <esr@thyrsus.com>2011-09-29 06:12:17 -0400
commitbc3c77cb8b20cda72cde05e00d722cbaa643f873 (patch)
tree43bc0818d1a6684777c2867b6b4d5315b1ffb961 /www/performance
parenteb24494a5b13ec82ee8709e7005efdfc80afe0fd (diff)
downloadgpsd-bc3c77cb8b20cda72cde05e00d722cbaa643f873.tar.gz
Thinko fix.
Diffstat (limited to 'www/performance')
-rw-r--r--www/performance/performance.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/www/performance/performance.xml b/www/performance/performance.xml
index 85c9931d..403dca64 100644
--- a/www/performance/performance.xml
+++ b/www/performance/performance.xml
@@ -324,7 +324,7 @@ settings).</para>
<para>Another effect is to enable a Z command to switch on profiling.
When profiling is on, each time
<application>gpsd</application>
-reports a fix with timestamp (e.g. on GPGGA, GPMRC and GPGLL
+reports a fix with timestamp (e.g. on GPGGA, GPRMC and GPGLL
sentences) it also reports timing information from five checkpoints
inside the daemon. The client library adds two more checkpoints.</para>
@@ -407,7 +407,7 @@ factor. Consider this table:</para>
</thead>
<tbody>
<row>
-<entry>GPMRC</entry>
+<entry>GPRMC</entry>
<entry>70</entry>
<entry>1.01</entry>
</row>
@@ -457,7 +457,7 @@ gives us this:</para>
<para>This graph looks almost identical to the previous one, except
for vertical scale &mdash; latency has been cut neatly in half.
-Transmission times for GPMRC go from about 0.15sec to 0.075sec. Oddly,
+Transmission times for GPRMC go from about 0.15sec to 0.075sec. Oddly,
average E1 is also cut almost in half. I don't know how to explain
this, unless a lot of what looks like E1 is actually RS232
transmission time spent before the first character appears in the