NTP to QNX

bridged with qdn.public.qnxrtp.porting
Post Reply
David Kuechenmeister

NTP to QNX

Post by David Kuechenmeister » Thu Nov 07, 2002 8:04 pm

I'm trying to get NTP running on a QNX 6 platform. The sticking point is how
to adjust the clock incrementally after an initial slew. It seems that most
platforms have an adjtime function that takes a struct timeval for the
number of usec to adjust. QNX has the ClockAdjust function that would appear
to do the same thing, except it's different. Instead of a struct timeval,
QSSL has invented a struct _clockadjust that contains the amount of time per
tick and the number of ticks to adjust the clock.

It looks like the upper limit on adjustments is 500 usec. Does anyone have
an estimate for the number of ticks over which that correction should be
applied? It would be nice to base it on the unix adjtime function, but I
don't know that much about how the adjtime function works on that platform.

Thanks,
David Kuechenmeister

Guest

Re: NTP to QNX

Post by Guest » Fri Nov 08, 2002 3:08 pm

david.kuechenmeister@viasat.com sed in <aqegk8$2bb$1@inn.qnx.com>
I'm trying to get NTP running on a QNX 6 platform. The sticking point is how
At least ntp 4.1.72 compiles "out-of-the-box" having adjtime() emulation.

(it still barfs on negative-full-second adjustments;
my package has it fixed but ntpd never offsets more than 500us anyway)

--
kabe

David Kuechenmeister

Re: NTP to QNX

Post by David Kuechenmeister » Fri Nov 08, 2002 6:12 pm

Thanks.

<kabe@sra-tohoku.co.jp> wrote in message news:aqgk0q$chd$1@inn.qnx.com...
david.kuechenmeister@viasat.com sed in <aqegk8$2bb$1@inn.qnx.com

I'm trying to get NTP running on a QNX 6 platform. The sticking point
is how

At least ntp 4.1.72 compiles "out-of-the-box" having adjtime() emulation.

(it still barfs on negative-full-second adjustments;
my package has it fixed but ntpd never offsets more than 500us anyway)

--
kabe

Post Reply

Return to “qdn.public.qnxrtp.porting”