gpsd-dev
[Top][All Lists]
Advanced

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

Re: [gpsd-dev] ✘Change FIXED_PORT_SPEED and FIXED_STOP_BITS


From: Jason Schoon
Subject: Re: [gpsd-dev] ✘Change FIXED_PORT_SPEED and FIXED_STOP_BITS
Date: Tue, 29 Oct 2019 07:15:47 -0500

The time has come to change FIXED_PORT_SPEED and FIXED_STOP_BITS from
build options and make them runtime options.

Wholeheartedly agree. We've begrudgingly modified this in our released products for years. 

I think the thing that has blocked many people previously are the hackers guide and FAQ that have statements such as https://gpsd.gitlab.io/gpsd/faq.html#baud

I'm all in favor of removing those and moving onward and upward.


On Thu, Oct 24, 2019 at 2:12 PM Gary E. Miller <address@hidden> wrote:
Yo All!

The time has come to change FIXED_PORT_SPEED and FIXED_STOP_BITS from
build options and make them runtime options.

Build options for common configurations are not useable by those that
use gpsd binaries built by someone else.  Some GNSS receivers, like
the RES SMT 360 behave strangly unless you talk to them with odd
settings, like 8O1, that are hard to auto configure.

Is there an obvious option to use for these?

How about adding options:
        -t [speed]
        -T [char]

Where [speed] is the port speed, and [char] is bits/parity/stop (default 8N1).

Ideas?

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

            Veritas liberabit vos. -- Quid est veritas?
    "If you can't measure it, you can't improve it." - Lord Kelvin

reply via email to

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