<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#fffffe" text="#000000">
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?<br>
<br>
<div class="moz-cite-prefix">On 17/08/2018 6:37 AM, Udo van den
Heuvel via devel wrote:<br>
</div>
<blockquote
cite="mid:04768cd3-97d4-122b-6f92-8607e935b7ef@xs4all.nl"
type="cite">On 17-08-18 12:08, Udo van den Heuvel via devel wrote:
<br>
<blockquote type="cite">On 15-08-18 15:12, Udo van den Heuvel via
devel wrote:
<br>
<blockquote type="cite">I will test if the patches apply to
Linux and ntpd.
<br>
</blockquote>
<br>
Kernel patch complains about arm-related files.
<br>
I guess we need x86/x86_64 equivalent changes?
<br>
</blockquote>
<br>
Without the arm-related pach the rest of the patch applies and
compiles on x86_64.
<br>
But how do we instruct the API to use DTR/RTS to signal the u-blox
receiver?
<br>
<br>
Amy updates on the usability of the u-blox refclock in ntpsec?
<br>
<br>
Kind regards,
<br>
Udo
<br>
_______________________________________________
<br>
devel mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:devel@ntpsec.org">devel@ntpsec.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.ntpsec.org/mailman/listinfo/devel">http://lists.ntpsec.org/mailman/listinfo/devel</a>
<br>
<br>
</blockquote>
<br>
</body>
</html>