[LinuxPPS] ntpd

[Udo van den Heuvel]

This should have gone to the list FOlkert?

Folkert van Heusden wrote:
>>> I verified that.
>> So the config is OK. Pulse length config is OK.
>> Does the GPS see sats? Does it know a position? How many sats?
> 
> field 'POS_STAT' said 'A' which is valid according to
> http://www.eecis.udel.edu/~mills/ntp/html/drivers/driver20.html

Good!

>>> The device also responded correctly to my commands
>>> (e.g. when I said "be silent", it became silent).
>>> Now the testpps thing still outputs nothing.
>> So no PPS if the kernel was patched OK.
> 
> 'pps_core' module is loaded

Good...


>>> I saw by the way that the 'on-line' status pulses between off-line and
>>> on-line when I am in minicom.
>> Online == Carrier Detect?
> 
> yes

Good! We see PPS!

>> So there is PPS.
>> So the kernel is not OK, assuming ppstest is OK and ntpd can find your
>> pps source normally.
> 
> how can I test this further?
> 
> I enabled debugging, now I get every second in my syslog:
> Aug  2 20:37:43 keetweej kernel: [42964983.580000] drivers/pps/clients/ktimer.c: PPS event at 1531062
> Aug  2 20:37:43 keetweej kernel: [42964983.580000] drivers/pps/kapi.c: capture assert seq #34 for source 8
> Aug  2 20:37:44 keetweej kernel: [42964984.580000] drivers/pps/clients/ktimer.c: PPS event at 1531162
> Aug  2 20:37:44 keetweej kernel: [42964984.580000] drivers/pps/kapi.c: capture assert seq #35 for source 8
> Aug  2 20:37:45 keetweej kernel: [42964985.580000] drivers/pps/clients/ktimer.c: PPS event at 1531262
> Aug  2 20:37:45 keetweej kernel: [42964985.580000] drivers/pps/kapi.c: capture assert seq #36 for source 8
> (with ktimer)

So PPSapi is working.

> keetweej:/usr/src/linuxpps-current# test/ppstest 1
> found PPS source #1 "pps_8250_1" on "/dev/ttyS1"
> 
> ppstest still doesn't emit anything

So the PPS of the kernel still does not reach you via the kernel
although the hardware receives the DCD pulses.