From: "Ron Frazier (NTP)" <timekeepingntplist@c3energy.com>
Cc: thumbgps-devel@lists.bufferbloat.net
Subject: Re: [Thumbgps-devel] USB handshake signals and Linux
Date: Thu, 15 Mar 2012 10:52:28 -0400 [thread overview]
Message-ID: <4F62022C.6020901@c3energy.com> (raw)
In-Reply-To: <CAFv7Oij9uk1u_tTd_a4R4KjrA8CCApHTD-nD9ZFExy8hihYoGA@mail.gmail.com>
I have a question about GPSD. I have nothing against it, but why is it
necessary to use it at all? I have NTPD running on both Windows and
Linux, and reading my GPS. GSPD isn't available on Windows as far as I
know. What does using GPSD get me that running without it does not?
Sincerely,
Ron
On 3/15/2012 10:37 AM, tz wrote:
>
> Skytraq has a number of unique commands that identify the chipsets.
> So do MTK and Garmin.
>
> Right now the udev for gpsd gets it wrong by including the generic
> FTDI vendor id for one gps, so plugging in my ftdi arduino/breakout
> starts up gpsd and it probes (same error in upowerd - I filed a bug
> report with fedora). It thought my SkyTraq was this unit.
>
> I have the PPS hooked to the CTS pin, but gpsd has to be recompiled to
> enable pps or change pins. This should be configurable at runtime.
>
> You still have the same problem using any other gps for bufferbloat -
> gpsd will attempt to sync the time via ntpshm based on any NMEA stream
> at the last sentence in a group. You will need some tweaking to make
> it not do this, or reject other gps units, or otherwise indicate that
> unless you are using one of our 'blessed' units the time won't be
> accurate. 'Blessed' might mean PPS, but how do we certify it?
>
> How much of an issue will this be? If we are going to require using
> one specific hardware combo, it will have the right set for
> gpsd-ntpd-kernel. If we allow any configuration of any hardware or
> software, we have no way of verifying it has precise UTC time - when
> was the last PPS, has the correction in adjtime caught up, etc. though
> that applies to ours too.
>
>
--
(PS - If you email me and don't get a quick response, don't be concerned.
I get about 300 emails per day from alternate energy mailing lists and
such. I don't always see new messages very quickly. If you need a
reply and have not heard from me in 1 - 2 weeks, send your message again.)
Ron Frazier
timekeepingdude AT c3energy.com
next prev parent reply other threads:[~2012-03-15 14:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFv7OigTLhw24i+jRshv0YgLogyx_GEREAOkP7tieeH1Nr5WzA@mail.gmail.com>
2012-03-15 14:37 ` tz
2012-03-15 14:52 ` Ron Frazier (NTP) [this message]
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
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
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=4F62022C.6020901@c3energy.com \
--to=timekeepingntplist@c3energy.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