ublox refclock

Trevor N. trv-n at comcast.net
Tue Nov 26 07:49:54 UTC 2019

Eric S. Raymond esr at thyrsus.com :
>Gary E. Miller via devel <devel at ntpsec.org>:
>> > So there is nothing you recommend be merged at this time?
>> I sorta wish NTPsec had a staging area like the Linux kernel does.
>> There is value to a small and clean u-blox driver fully integrated
>> into NTPsec.  But without KPPS it is inferior at timekeeping.
>> If the guy that wrote it wanted to work on it under the NTPsec umbrella
>> that would be good.  A little guidance and the guy that wrote that could
>> be very useful to NTPsec.
>> Without that guy, or someone interested in being that guy. I'd pass on
>> that driver.  I'm not personally interested in upgrading that software to
>> have the smarts that gpsd already does about the u-blox and KPPS.
>I left an issue on his tracker about merging to upstream.  If he responds
>I will try to bring him into the fold. If he does not, from what you say there
>os not much loss hrere.
>		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Thanks for the interest in the driver. It's the same one I posted in
issue 499:

I have been busy with my day job this year, but I will have some free
time starting next month. I'll update my fork to the latest upstream
this weekend.

I have also tested the driver with a ZED-F9T for a few months now
(with the new version posted on issue 499), and the performance is
even better than what I reported on the issue 499 thread with the M8T
-- And the F9T did not show any of the strange issues that I reported
having with the M8T.

I will attach some ntpvis plots of the F9T to the issue 499 thread.

More information about the devel mailing list