On Mon, Feb 16, 2015 at 03:12:27PM +0100, Terje Mathisen wrote: > William Unruh wrote: > >I think, but am not sure, that the biggest problem with porting chrony > >to windows is that windows does not have a good way of having the kernel > >discipline the clock-- the equivalent of adjtimex on Linux. > > If this is the biggest problem, then it would already be running there!
There is also the part with porting all the code to Win32/Cygwin :). > GetSystemTimeAdjustment() > SetSystemTimeAdjustment() > > The only "hard" part is that you have to manually convert the adjustment > rate to an absolute value: > > Call Get* to retrieve the amount the system clock is incremented by on each > timer tick/basic clock interval, then scale this value by the adjustment > rate, i.e. to add 5.6ppm you would take the base value and multiply by > 1.0000056. In what resolution can be the frequency controlled? I'm not sure if I remember correctly, I thought it was rather bad and would require dithering. Looking at nt_clockstuff.c in the ntp distribution, it certainly doesn't look easy. -- Miroslav Lichvar _______________________________________________ questions mailing list questions@lists.ntp.org http://lists.ntp.org/listinfo/questions