[LinuxPPS] refclock_nmea patch

Udo van den Heuvel udovdh at xs4all.nl
Mon Oct 22 20:20:04 CEST 2007


Rodolfo Giometti wrote:
>> Note the %d in the message string and that the first gps0 device is not
>> used. %d was fixed with your suggestion.
> 
> Good.

/dev/gps0 is not used!...

>> /dev/gps0 points to /dev/ttyS0. Is the fd still open when it reaches the
>> LinuxPPS part that we change? Maybe reopen the fd?
> 
> No, the fd is opened since it is passed to the first
> pps_time_create().

So why is the alternate devise used?

>> [root at epia ntpd]# setserial /dev/ttyS0
>> /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4, Flags: hardpps low_latency
>> [root at epia ntpd]# setserial /dev/gps0
>> /dev/gps0, UART: 16550A, Port: 0x03f8, IRQ: 4, Flags: hardpps low_latency
> 
> Are yo uusing patched setserial? If so I don't see the hardpps
> flag. 

See the output...

>> [root at epia ntpd]# setserial /dev/pps0
> 
> Why do you use setserial on /dev/pps0?

Just to see what it is.
Apparently it is created by the LinuxPPS patch.
But why only for pps0 and not for gps0?

> 
>> [root at epia ntpd]# ls -l /dev/?ps0
>> lrwxrwxrwx 1 root root     10 2007-10-22 19:17 /dev/gps0 -> /dev/ttyS0
>> crw------- 1 root root 254, 0 2007-10-22 19:17 /dev/pps0
>> [root at epia ntpd]# ls -l /dev/ttyS0
>> crw-rw---- 1 root uucp 4, 64 2007-10-22 19:36 /dev/ttyS0
>>
>> Any ideas!?
> 
> About what?

Why only for pps0 and not for gps0?
/dev/gps0 is not used at all!

> Great job! Just fix these few errors and you may submit your patch to
> the NTPD mail list for inclusion! :)

First I want to understand why /dev/gps0 is not used.
Then I can send it out I think.

> Thanks for your help,

Thank you too!


Udo



More information about the LinuxPPS mailing list