Historic archive of defunct list thumbgps-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Patrick Maupin <pmaupin@gmail.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
Date: Thu, 15 Mar 2012 00:23:43 -0400	[thread overview]
Message-ID: <20120315042343.GA32483@thyrsus.com> (raw)
In-Reply-To: <CAPz3yKe3g1LsA788KxDRiuuqfORYndi7+9Gn9CNgBYZkBto0qQ@mail.gmail.com>

Patrick Maupin <pmaupin@gmail.com>:
> The latency timer on the FTDI parts can be dropped to a millisecond.
> If we find a USB dongle that has a USB converter with similar
> capabilities and a GPS chipset that has rock-solid first-character
> timing, we might avoid needing the RS232 handshake altogether.

There's a reason I'm a bit wary of a non-1PPS design based on timing
the leading edge of the $GPZDA or whatever. That is this: unless the
device is self-identifying, there'll be no way to know when the time
information can be trusted.  Remember that the bufferbloat deployment
is planned to use GPSD and that we *cannot* assume that GPSD 
knows anything hand-configured about the USB devices it talks to.

By "self-identifying" that it ether (a) has a recognizable USB
vendor/ID pair, (b) ships a unique sentence type that GPSD can
recognize, or (c) there's a probe string GPSD can ship it that elicits
a unique response.  For reasons of history and vendor stupidity most
GPS-chip/adapter combos will fail all three tests.

One of the advantages of 1PPS is that it is self-identifying in this
way. If you're talking to a GPS, nothing but 1PPS produces DCD or RI
transitions, so when you see a 1PPS pulse you know what it is.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  reply	other threads:[~2012-03-15  4:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 10:49 Eric S. Raymond
2012-03-14 12:55 ` Ron Frazier (NTP)
2012-03-14 12:58   ` Ron Frazier (NTP)
2012-03-14 18:13 ` Patrick Maupin
2012-03-14 18:42   ` Eric S. Raymond
2012-03-14 18:57     ` Dave Taht
2012-03-14 20:09       ` Patrick Maupin
2012-03-15  3:33     ` Patrick Maupin
2012-03-15  4:23       ` Eric S. Raymond [this message]
     [not found] <CAFv7OigTLhw24i+jRshv0YgLogyx_GEREAOkP7tieeH1Nr5WzA@mail.gmail.com>
2012-03-15 14:37 ` tz
2012-03-15 14:52   ` Ron Frazier (NTP)
2012-03-15 17:57     ` Eric S. Raymond
2012-03-15 18:31   ` Eric S. Raymond
2012-03-15 18:54     ` Patrick Maupin
2012-03-15 19:36       ` Eric S. Raymond
2012-03-15 19:55         ` Patrick Maupin
2012-03-15 19:14     ` tz
2012-03-15 19:50       ` Eric S. Raymond

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120315042343.GA32483@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=pmaupin@gmail.com \
    --cc=thumbgps-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox