Harlan Stenn st...@ntp.org wrote:
Rob,
You have seen 'flag1' in the recent ntp-dev SHM driver documentation,
right?
I have installed ntp-dev and as part of that also ntp-dev-doc, but
it is essentially empty (only an automatically generated changelog).
There appears to be a package
Rob writes:
Harlan Stenn st...@ntp.org wrote:
Rob,
You have seen 'flag1' in the recent ntp-dev SHM driver documentation,
right?
I have installed ntp-dev and as part of that also ntp-dev-doc, but
it is essentially empty (only an automatically generated changelog).
It's in the source
Rob wrote:
Harlan Stenn st...@ntp.org wrote:
Rob,
You have seen 'flag1' in the recent ntp-dev SHM driver documentation,
right?
I have installed ntp-dev and as part of that also ntp-dev-doc, but
it is essentially empty (only an automatically generated changelog).
There appears to be a
David Lord sn...@lordynet.org wrote:
Rob wrote:
Harlan Stenn st...@ntp.org wrote:
Rob,
You have seen 'flag1' in the recent ntp-dev SHM driver documentation,
right?
I have installed ntp-dev and as part of that also ntp-dev-doc, but
it is essentially empty (only an automatically generated
On 23/08/2014 11:52, David Taylor wrote:
[]
I would suggest first stopping NTP, and testing whether this program can
see the PPS signal.
http://www.satsignal.eu/software/net.htm#SerialPortLEDs
--
Cheers,
David
Web: http://www.satsignal.eu
___
On Sat, Aug 23, 2014 at 6:05 AM, Harlan Stenn st...@ntp.org wrote:
No idea what you mean there - we do 64-bit builds (under linux and other
OSes) all the time. You might want to check with whoever handles
building packages for your distro.
You lot are not fulfilling your obligation to Rob.
Harlan Stenn st...@ntp.org wrote:
Rob writes:
Harlan Stenn st...@ntp.org wrote:
Rob,
You have seen 'flag1' in the recent ntp-dev SHM driver documentation,
right?
I have installed ntp-dev and as part of that also ntp-dev-doc, but
it is essentially empty (only an automatically
Paul tik-...@bodosom.net wrote:
On Sat, Aug 23, 2014 at 6:05 AM, Harlan Stenn st...@ntp.org wrote:
No idea what you mean there - we do 64-bit builds (under linux and other
OSes) all the time. You might want to check with whoever handles
building packages for your distro.
You lot are not
thanks David
Yes it works fine with the SerialPortLEDs. The DCD blinks in that software.
In my GPS engine the PPS length is 100msec.
The problem is that when I start the NTP, I only can see the NMEA driver
working. No PPS is recognized by the NTP.
As I mentioned above I have already installed
On 23/08/2014 17:04, valizade...@gmail.com wrote:
thanks David
Yes it works fine with the SerialPortLEDs. The DCD blinks in that software.
In my GPS engine the PPS length is 100msec.
The problem is that when I start the NTP, I only can see the NMEA driver
working. No PPS is recognized by the
Paul writes:
More seriously -- having that somewhat stale deb repo probably isn't
helping anyone and causes confusion (like yours) between ntp-dev tar
balls and ntp-dev debs including the (nearly empty) ntp-dev-doc deb.
I didn't know that Rob was talking about the debian package stuff from
On Sat, Aug 23, 2014 at 4:00 PM, Harlan Stenn st...@ntp.org wrote:
I didn't know that Rob was talking about the debian package stuff from
ntp.org until he replied to that message.
Look for 'ntp-dev conflicts with ntp' from early this month. Of
course there's going to be confusion when 99.99%
Paul writes:
On Sat, Aug 23, 2014 at 4:00 PM, Harlan Stenn st...@ntp.org wrote:
I didn't know that Rob was talking about the debian package stuff from
ntp.org until he replied to that message.
Look for 'ntp-dev conflicts with ntp' from early this month. Of
course there's going to be
Harlan Stenn st...@ntp.org wrote:
To carp yet again: you should add timepps.h to the tar ball and stick
to that. Leave the package building to the distributions. If people
want/need more current features they should learn how to build the
current dev source and you should make that a LOT
14 matches
Mail list logo
