[LWN Logo]

Date:	Mon, 10 Apr 2000 13:32:49 +0200 (CEST)
From:	Ulrich Windl <wiu09524@pc3103.klinik.uni-regensburg.de>
To:	linux-kernel@vger.rutgers.edu
Subject: announce: PPSkit-0.9.2 available for Linux-2.2.14

Here's a copy of my article: -- Ulrich

Newsgroups: comp.protocols.time.ntp
Subject: PPSkit-0.9.2 available for Linux-2.2.14
From: Ulrich Windl <wiu09524@rrzc5.rz.uni-regensburg.de>
Date: 10 Apr 2000 13:28:12 +0200
Message-ID: <snf7le6kxf7.fsf@rrzc5.rz.uni-regensburg.de>
Lines: 82
X-Newsreader: Gnus v5.7/Emacs 20.4
--text follows this line--
Hi,

another release of PPSkit is available, again with distinct features
that may be worth the trouble of updating (specifically this is the
first version where DEC Alpha should work out of the box and better
than with the standard kernel):

                             What's new?
              Copyright (c) 1997 - 2000 by Ulrich Windl

                            NEWS for 0.9.2

* Optimized computation used to convert timer register to nanoseconds
  for i386.  Avoid duplicate call to ``do_nanotime()'' when capturing
  timestamps in the serial driver (Modified ``do_clock_gettime()'' to
  return the time offset to make this possible).  These changes should
  save some CPU cycles.

* Streamlined ``INSTALL''.  Updated ``ntp.conf.PPS'', ``CREDITS'', and
  ``MANIFEST''.  Added patch for ntp-4.0.98e (and possibly later) to make
  PPS and ATOM run out-of-the-box.

* Updated ``enable_pps.c'' to display capabilities of PPS API.  Stop
  if ``time_pps_create()'' failed.

* Modified PPS API implementation to accept disabling a nonexistent
  binding for the kernel consumer.  Previously this was EINVAL.
  However, if a valid binding exists for a different PPS source,
  EINVAL is still returned (People use ``edge == 0'' erroneously to
  say that a binding is not to be established, but RFC 2783 specified
  this as ``clearing the binding'').

* Added table with release overview ``status.html''.

* Fixed bug in ``hardpps()'' that caused frequency spikes after bad
  pulses (should have happened quite rarely however).  Fixed problem
  in ``update_wall_time_one_tick()'' when a fractional number for
  ``time_tick'' causes accumulated phase errors (e.g. DEC Alpha).
  Thus ``time_tick'' is no longer used when ``CONFIG_NTP'' is defined!

* Added fix for arch/alpha/kernel/time.c suggested by John Sager
  <jcs@zoo.bt.co.uk> (modified a bit by myself).  Fixed stupid syntax
  error in same file.

* Added fix to arch/alpha/kernel/osf_sys.c (reported by Karlo Gross).
  Should compile now.

* Merged patch for Linux-2.2.14 (manually updated ppc, sparc64).

* Merged changes for new ``S390'' architecture (only
  ``kernel/{irq,time}.c'', untested).


THE LSM file is this:

Begin3
Title:          PPSkit
Version:        0.9.2
Entered-date:   2000-04-01
Description:    General kernel patch to implement nanoseconds as time
                resolution.  Upgrades the kernel clock model for NTP v4
                (nanokernel '#3'), including PPS support.  Adds support
for
                capturing external timestamps with high precision via RFC
2783
                (PPS API v1).
Keywords:       NTP, PPS, PPS API, kernel patch, RFC1305, RFC1589,
RFC2783,
                clock_gettime, clock_getres, clock_settime,
pulse-per-second,
                time synchronization, time calibration, adjtimex,
nanoseconds,
                POSIX.4, nanokernel, hardpps
Author:         Ulrich.Windl@rz.uni-regensburg.de (Ulrich Windl)
Maintained-by:  Ulrich.Windl@rz.uni-regensburg.de (Ulrich Windl)
Primary-site:   linux.kernel.org /pub/linux/daemons/ntp/PPS
                156kB PPSkit-0.9.2.tar.gz
Alternate-site: 
Original-site:  pcphy4.physik.uni-regensburg.de /pub/wiu09524/PPS
                PPSkit-0.9.2.tar.gz
Platform:       Any.  NTP PPS usage requires RS232-compatible precision
                pulse-per-second with an error less than 500PPM (0.0005%)
Copying-policy: GPL, but payment welcome!  (other licensing posible, ask!)
End

Regards,
Ulrich



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/