summaryrefslogtreecommitdiff
path: root/build.txt
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2015-01-29 11:51:41 -0500
committerEric S. Raymond <esr@thyrsus.com>2015-01-29 11:51:41 -0500
commita3af061b227d8334f6f69191ee211baf66de2408 (patch)
tree9c781b7a8944becbcc16dc13fe65fcac15b3d0ad /build.txt
parenta67291dffa1b8741bf44c1dcce1c9a4c855ceb3b (diff)
downloadgpsd-a3af061b227d8334f6f69191ee211baf66de2408.tar.gz
Remove the failed adaptive-delay experiment.
Instead, we're going to try telling the tty layer to deliver input in chunks larger than chracters, with a timeout. That way the select call in the main loop will return data ready less often. All regression tests pass.
Diffstat (limited to 'build.txt')
-rw-r--r--build.txt14
1 files changed, 0 insertions, 14 deletions
diff --git a/build.txt b/build.txt
index 1105f22f..2847be60 100644
--- a/build.txt
+++ b/build.txt
@@ -352,20 +352,6 @@ scons minimal=yes socket_export=yes nmea0183=yes
will do that.
-buzzkill=yes: this option is intended to thwart problems due to gpsd's
-main select(2) loop buzzing (spinning too fast). On battery-powered
-SBCs and mobile devices this can cause serious and unnecessary power
-drain; this has been observed on the Raspberry Pi and sporadically on
-particular Android phone hardware. There are at least two reasons it
-can happen; one is defective select(2) device-driver hooks that return
-a data-ready when they shouldn't, the other is tty layers that return
-data in single characters or small packets even when it's arriving in
-packet-sized chunks. GPSD with buzzkill=yes watches the incoming data
-rate from all devices and adaptively inserts delays in the main loop
-if it thinks it sees buzzing. This logic is routed around if all
-devices have types that never require delays, notably pseudo-ttys and
-UDP packet streams.
-
== Port and toolchain testing ==
'scons check' will run a comprehensive regression-test suite. You