While I tried to spread the patch to all architectures, I have no idea
how they work. I'm planning to move on to the development release of
Linux-2.1 to get more exciting things for PPSkit-0.4 (like the PPS
API). Still I would add architecture dependent fixes into further 0.3
releases. The NEWS file says:
NEWS for 0.3.3
+ Added ``ntp.conf.PPS'' as an example configuration file for xntpd
and PPS usage (uses ATOM driver)
+ Updated INSTALL to have numeric steps (I hope you'll get lost a bit
harder now)
+ Modified ``hardware_pps'' to reset calibration interval when
``STA_PPSWANDER'' is detected. Dave Mills did not fully confirm the
problem: ``I gotta put you on hold. It's been awhile since I last
danced with that code and I have a couple of heavy conferences to
survive. However, I recall the intent of the code was not
necessarily to ignore jitter or even wander, as long as the
calibration interval could safely increase while avoiding a slip of
the tick, which could cause severe error. The idea is to discipline
the frequency in a closed- loop system, not necessarily to calculate
the exact frequency. Once the frequency has been measured and the
interval increased to the max, it's pretty hard to kick the loop out
of lock, unless the PPS jitter becomes much larger than the tick
interval.''
+ Updated xntpd/ntp_refclock patch to give better status messages.
+ Changes to the serial driver have been minimized.
+ Patch has been updated for Linux-2.0.31.
+ Updated kernel patch to include architectures (alpha, m68k, mips,
ppc, sparc), but did not test anything at all:
- alpha, m68k, mips, sparc have no ``do_gettimeoffset'' function.
- mips and sparc have different structure of their
``include/asm-<arch>'' directories; they still lack CIOGETEV
--- &disclaimer; ---
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de+no-spam>
Klinikum der Universitaet Regensburg, Rechenzentrum DV-med
Franz-Josef-Strauss-Allee 11\\D-93042 Regensburg, Germany
%%[PGP 2.3a/2.6ui Public Key 0x[e8]43660d on at least one key server]%%
%1024/E843660D 1994/03/26 = CF D7 43 A1 5A 49 14 25 7C 04 A0 6E 4C 3A AC 6D
Stop the SPAM, read the Nettiquette (RFC 1855)!