[LinuxPPS] timepps.h (again)

Paul paul at lavender-fam.net
Wed Aug 1 17:11:35 CEST 2007


Hmmm

Kernel inclusion? Do the ntp maintainers know that large chunks are  
going to have to be rewritten?

Am I missing something or this just isn't 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. Obviously the PPS output is good, but needs another  
source.

I may be back to you re: the atom patch, because I had one or two  
problems there.


Paul

On 01/08/07 15:57:08, Udo van den Heuvel wrote:
> Paul wrote:
> > When I make ntp (no patches) (after a configure with no switches)
> the
> > make fails when it starts looking at the atom ref_clock.
> >
> > PPS_API_VERS_1 undeclared
> >
> > So are we saying that the only reference clocks that will compile
> are
> > those which were designed to use the PPs kernel?
> 
> Indeed.
> Get a patch for the ATOM driver and it works like it does over here.
> :-)
> 
> 
> _______________________________________________
> 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
> 
> 
> 



More information about the LinuxPPS mailing list