[LinuxPPS] Occasionally ntpd stops receiving NMEA data
Rodolfo Giometti
giometti at linux.it
Mon Jun 5 13:07:02 CEST 2006
On Mon, Jun 05, 2006 at 12:55:53PM +0200, Udo van den Heuvel wrote:
>
> So?
> This means that defining a version number in the name of a variable is
> not so handy of there is no control over other sources like in the case
> of ntp.
I didn't study deeply how much that define may change the code. I only
know that if PPS_API_VERS_1 is not defined the NTPD default
configuration changes.
> For Philip a small patch of configure might fix the problem.
Maybe, or maybe not... first of all we should verify that the problem
is in that define. Currently we are only supposing. :)
However I think the file timepps.h should be changed as follow:
/* --- 3.2 New data structures --------------------------------------------- */
#define PPS_API_VERS_1 1 /* Keeped for NTPD back compatibility */
#define PPS_API_VERS PPS_API_VERS_1
#define LINUXPSS_API 1 /* mark LinuxPPS API */
#define NETLINK_PPSAPI 17 /* we use just one free number... */
In this manner NTPD should restart working with proper configuration
but we still continue patching the drivers using LINUXPSS_API to mark
LinuxPPS code.
I know. It's an hack... but it is the shortest way! ;)
Ciao,
Rodolfo
--
GNU/Linux Solutions e-mail: giometti at enneenne.com
Linux Device Driver giometti at gnudd.com
Embedded Systems giometti at linux.it
UNIX programming phone: +39 349 2432127
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: Digital signature
Url : http://ml.enneenne.com/pipermail/linuxpps/attachments/20060605/2e2c6b33/attachment.pgp
More information about the LinuxPPS
mailing list