gpsd-commit-watch
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gpsd-commit-watch] [SCM] GPSD branch, master, updated. release-3.16-543


From: Fred Wright
Subject: [gpsd-commit-watch] [SCM] GPSD branch, master, updated. release-3.16-543-gb6f7daa
Date: Fri, 20 Jan 2017 03:24:30 +0000 (UTC)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GPSD".

The branch, master has been updated
       via  b6f7daade9563dc009d2e61816bd69538d845b49 (commit)
       via  a849277d3bd54aacf22df6c3ea1bf3b1c3054e6d (commit)
       via  e91f750c1e9ac1e1340181febf89201cb3cce8bd (commit)
      from  4dd216c55d2838f71a1c7e445a2f180393e04fb3 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit b6f7daade9563dc009d2e61816bd69538d845b49
Author: Fred Wright <address@hidden>
Date:   Thu Jan 19 19:03:25 2017 -0800

    Updates MAXCHANNELS in gps.py to match gps.h.
    
    This value is only provided as a convenience, and has no internal
    function at all.  It was never updated to reflect the two increases in
    gps.h.  The new value would be excessive for xgps, but that no longer
    uses this definition.
    
    TESTED:
    No point.

commit a849277d3bd54aacf22df6c3ea1bf3b1c3054e6d
Author: Fred Wright <address@hidden>
Date:   Thu Jan 19 18:50:38 2017 -0800

    Increases MAXCHANNELS in xgps.
    
    The current MAXCHANNELS value in xgps, obtained from gps.py, has been
    observed to be inadequate.  The value in gps.py is an outdated value
    that was never updated when the C value was changed, but using the new
    value of 72 in xgps would result in a huge window.  This change
    defines a local MAXCHANNELS in xgps, which does not need to match the
    value in gps.py.  It's currently set to 28, based on having observed a
    case with 25 visible satellites.  It would be better to make it
    dynamic, but that would require reworking some of the Gtk setup code.
    
    TESTED:
    Ran against a receiver reporting 25 visible satellites, seeing all
    satellites reported and no console error messages.

commit e91f750c1e9ac1e1340181febf89201cb3cce8bd
Author: Fred Wright <address@hidden>
Date:   Thu Jan 19 17:49:59 2017 -0800

    Fixes some trouble with gpsmon and no PPS_ENABLE.
    
    Until recently, PPS_ENABLE was always true by default, even on
    platforms where it was intended to be forced off.  Fixing this exposed
    some issues in gpsmon.  This generally related to confusion between
    *displaying* PPS info versus *capturing* it.  Since gpsmon can be run
    against a remote target, it should be able to report PPS info even
    when running on a host that doesn't support PPS, but the code was
    conflating the two issues.
    
    The changes here are:
    
    1) There is now a PPS_DISPLAY_ENABLE, which is always true, and should
    be used in place of PPS_ENABLE in code related to displaying PPS info,
    to the extent possible.
    
    2) The code related to processing remote TOFF and PPS events now uses
    this new conditional.  Aside from restoring the presence of the "PPS
    offset" lines in the scrolling data, this also fixes a problem where
    the display malfunctioned when this code was absent.  The exact nature
    of this dependency hasn't yet been determined, but there's a FIXME to
    document the issue.
    
    3) The reporting of PPS offsets in the windowed area still doesn't
    work without PPS_ENABLE, due to the entanglement between that code and
    the pps_thread code.  There are now a couple of FIXMEs related to that
    issue, which is being left for future work.
    
    4) A couple of unnecessary PPS_ENABLE conditionals were eliminated by
    making use of the existing conditionally-defined lock/unlock
    functions.
    
    TESTED:
    Ran gpsmon on OSX 10.9 (where PPS_ENABLE is off) against three
    receivers (one local and two remote), with the expected results.  Also
    ran it on Ubuntu 14 (where PPS_ENABLE is on) against the same three
    receivers (again one local and two remote), again with the expected
    results.

-----------------------------------------------------------------------

Summary of changes:
 gps/gps.py |    2 +-
 gpsmon.c   |   22 +++++++++++++---------
 xgps       |   10 +++++++---
 3 files changed, 21 insertions(+), 13 deletions(-)


hooks/post-receive
-- 
GPSD



reply via email to

[Prev in Thread] Current Thread [Next in Thread]