[LinuxPPS] RE: with Atom driver problems

[Tom Playford]

On 30/08/06, Rodolfo Giometti <giometti at linux.it> wrote:
> If you enable the kernel messages and your userland application (NTPD
> in your case) reads the PPS signals you should see something like
> this:
>
>    "pps_core":"pps"[82]: New message from PID 13131 (flags 0)
>    "pps_core":"pps"[189]: PPS_FETCH: source 0

Yes, I do. I've put a dmesg dump below. ntpd is running on pid 5205.

NTP is still giving a reach of 0.
ntpq> peer
     remote           refid      st t when poll reach   delay   offset  jitter
==========================================================
 PPS(0)          .PPS.            0 l    -   64    0    0.000    0.000   0.001

So, NTP is connecting to the PPS inteface, and sending 'FETCH'
commands but it's not doing anyting with it. Correct? Any ideas?

Thanks,

Tom

> P.S. Please, send your letters to the ML also, in this manner other
> people may learn from you. :)

Will do, I'm terrible at remembering to do that.

dmesg dump:

drivers/serial/8250.c: serial8250: PPS clear event at 420692
drivers/pps/pps.c: New message from PID 5205 (flags 0)
drivers/pps/pps.c: PPS_FETCH: source 0
drivers/pps/kapi.c: capture assert seq #292 for source 0
drivers/serial/8250.c: serial8250: PPS assert event at 420817
drivers/pps/kapi.c: capture clear seq #292 for source 0
drivers/serial/8250.c: serial8250: PPS clear event at 420942
drivers/pps/pps.c: New message from PID 5205 (flags 0)
drivers/pps/pps.c: PPS_FETCH: source 0
drivers/pps/kapi.c: capture assert seq #293 for source 0
drivers/serial/8250.c: serial8250: PPS assert event at 421067