As this is likely for a dedicated timeserver, why not have some
dedicated stand-alone software deal with an M8T (or others with
Timemark) and discipline System Time, then have nptsec use System
Time as a reference?
On 17/08/2018 6:37 AM, Udo van den
Heuvel via devel wrote:
On 17-08-18 12:08, Udo van den Heuvel via devel wrote:
On 15-08-18 15:12, Udo van den Heuvel via
devel wrote:
I will test if the patches apply to
Linux and ntpd.
Kernel patch complains about arm-related files.
I guess we need x86/x86_64 equivalent changes?
Without the arm-related pach the rest of the patch applies and
compiles on x86_64.
But how do we instruct the API to use DTR/RTS to signal the u-blox
receiver?
Amy updates on the usability of the u-blox refclock in ntpsec?
Kind regards,
Udo
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel
|
_______________________________________________
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mailman/listinfo/devel