[LinuxPPS] timepps.h (again)

[Paul]

I truly hope so, but looking at the ntp mailing list is interesting.  
They can get into a serious flame war about leap seconds.

I do have a rather peculiar problem with the atom driver, but I will  
assemble all the information and start a another thread

Thanks for all your help - my understanding is increasing slowly.

Paul

On 01/08/07 16:46:38, Udo van den Heuvel wrote:
> Paul wrote:
> > Kernel inclusion?
> 
> ntp-patches.
> 
> > Do the ntp maintainers know that large chunks are
> > going to have to be rewritten?
> 
> Small chunks. See some patches at
> http://wiki.enneenne.com/index.php/LinuxPPS_support#NTPD_support.
> 
> > Am I missing something or this just isn't going to work?
> 
> It is going to work.
> 
> > By the way some background (mostly for Udo) I couldn't use the great
> > nmea patch because I am using a Jupiter GPS. NMEA messages are
> usually
> > one second late (easy to fudge), but sometimes two seconds. All of
> this
> > is mentioned in the jupiter_refclock (when I finally found it!) but
> the
> > driver is totally prehistoric and of no use for any Jupiter modules
> > bought today.
> 
> Because?
> You need only basic NMEA support.
> 
> > Obviously the PPS output is good, but needs another source.
> 
> You could use the ATOm driver. It has a patch.
> 
> > I may be back to you re: the atom patch, because I had one or two
> > problems there.
> 
> Please see the wiki. It is not my patch but it works here quite well.
> 
> Udo
> 
> _______________________________________________
> LinuxPPS mailing list
> LinuxPPS at ml.enneenne.com
> http://ml.enneenne.com/cgi-bin/mailman/listinfo/linuxpps
> Wiki: http://wiki.enneenne.com/index.php/LinuxPPS_support
> 
> 
>