| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to Matthias Drochner at
http://lists.lysator.liu.se/pipermail/lsh-bugs/2003q4/000151.html:
I thought I'd give lsh a try, just to see how it compares to openssh...
The client didn't work well on NetBSD, got a message like "unexpected
EWOULDBLOCK" on each keystroke.
Looked a bit deeper and found that stdin is set to O_NONBLOCK and
a raw tty mode with c_cc[VMIN] > 1 and c_cc[VTIME] > 0.
I'll append a little test program which does the same. I've tried
it on 3 operating systems (Linux, NetBSD, Digital UNIX), and it
behaves differently on each:
-on Linux, if a key is pressed, the read returns immediately with
that one character
-on NetBSD, the read returns with no data but EWOULDBLOCK
-on D'UNIX, the poll() doesn't teturn before 4 keypresses are done;
the read() returns these 4 characters
Indeed, in SUSv2's termios page is a sentence which says that if
both O_NONBLOCK and VTIME>0 are set, the behaviour is more or less
undefined.
I've solved my immediate problems by setting VMIN to 1 instead of 4
in unix_interact.c:do_make_raw(), but VTIME is still pointless,
so I wouldn't call this a clean solution.
All regression tests pass.
|
|
|
|
| |
Length 0 means the minimum is unknown and the driver should use character I/O.
|
|
|
|
| |
This fixes an hour-offset bug due to the tm_isdst member being uninitialized.
|
| |
|
|
|
|
|
| |
Turned up a bug in where a counter was incremented un the Navcom driver;
this required one test rebuild.
|
| |
|
|
|
|
| |
This change doesn't affect generated binary code.
|
|
|
|
|
|
|
| |
Instead, set the used member in the satellites array directly where possible.
The NMEA0183 and TSIP drivers still need a local equivalent.
This changes pseudo-NMEA GSA output in several binary-protocol tests.
|
|
|
|
|
|
|
|
|
|
|
| |
Before, that information was partly coming from the navigation-solution message
and being pieced together with related data from svinfo. This way of doing
things is more consistent.
While this change required a rebuild of four check files, the effects are minor.
Fixes don't change, but some generated pseudo-NMEA does and the error
modeler can sometimes compute error estimates in cases where the old
code could not because of a determinant-zero condition.
|
|
|
|
|
|
|
| |
Warning cleanup that one of the nav message was not used if
RECONFIGURE_ENABLE was not defined. Inspection shows that it is only
used from within code guarded by the same ifdef guard so adjusted to
clear the compile warning.
|
|
|
|
|
|
|
| |
Returns us to something amost identical to the original code.
Sigh. Timezones are a swamp.
All regression tests pass.
|
|
|
|
| |
Dependency soon to be fixed. All regression tests pass.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...from a set of parallel arrays. This change flushed out a
longstanding bug in the computation of DOPs for estimated error bars.
Some test-load rebuilds were required:
geostar-geos1m-binary.log.chk: With this change error
estimates are computed and reported.
trimble-lassen_iq-3dfix.log, trimble-lassen_iq-3dfix.log: the
change revealed a bug in the computation of satellite-seen bits.
Error estimates did not change.
navcom.log: Error estimates changed.
With these rebuilds, all regression tests pass.
|
| |
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...with calls to gps_notify(), which indirects to its output method
through a slot in an errout structure. Usually the errout structure
lives inside the session context, but because struct errout_t is its
own thing this does not have to be the case. One large clique of
gpsd_notify() calls, in packet.c and isgps.c, looks at a struct
errout_t copy in a lexer control block
This change is not complete. Remnant gpsd_report calls need to be changed,
and gpsmon needs to be tweaked so that the struct_error_t in its context
is a non-defaukt hook updating the cuses display rather than simply
dumping to stderr. Also the report label functionality needs to be added.
All regression tests pass.
|
|
|
|
|
|
| |
A major step towards eliminating reverse linkage.
All regression tests pass.
|
|
|
|
| |
All regression tests pass.
|
|
|
|
| |
All regression tests pass.
|
|
|
|
| |
Follows a tip from Michael Tatarinov.
|
|
|
|
|
|
| |
This enables us to force readonly off while it's being called.
The practical effect is that gpsmon can get a firmware version (if this
is possible) without reconfiguring the device.
|
| |
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
|
|
| |
Required a regression-test rebuild, of course. The field is still set by
the TSIP and SiRF drivers; the SiRF driver actually uses it. It may be
possible to eliminate the TSIP uses, but so far attempting this has
produced odd regression-test failures.
|
| |
|
|
|
|
| |
Dodgy code turned out to be right after all - just needs documentation.
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
|
| |
This is in response to a report by Jeff WEoolsey on gpsd-dev
indicating that it masy be *required* to turn this off to
get accurate time...
|
|
|
|
| |
It failed on a live GPS, in the configuration code.
|
| |
|
|
|
|
|
| |
With this code, direct-mode gpsmon speed changes work on SiRF II, III, and IV.
Direct-mode gpsctl speed changes work on SiRF II and III, fail on SiRF IV.
|
| |
|
| |
|
|
|
|
|
|
|
| |
From a patch by Michael Tatarinov. Does no harm, and may be required
for SiRF IV to work.
All regressiion tests pass.
|
|
|
|
| |
Correct initialization observed oon SiRF-III. All regression tests pass.
|
| |
|
| |
|
| |
|
|
|
|
| |
All regression tests pass, PPS is live.
|
|
|
|
|
| |
Works on a BU-355 (SiRF-III); at least, it gets through the configuration
sends with little stalling.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also make it a lot longer than before. The SiRF driver should
also be listening for the ACK/NACKs.
|
|
|
|
| |
This logging level is intended to directly explain accompanying I/O messages.
|
|
|
|
|
|
|
|
|
|
| |
Way too much logging was happening at LOG_IO level, which is intended for
watching data traffic in and out of the daemon rather than all the minutiae
of data analysis - that's LOG_DATA.
Also, LOG_DATA gets pushed down two levels. The effect is that -D 5
means exactly what it did, but for purposes other than driver debugging
-D 4 now suffices.
|
| |
|
| |
|
| |
|