Danny Mayer wrote:
[]
> You need to run the OpenSSL build first to create that directory. Just
> follow the instructions.
>
> Danny
Danny,
I'm afraid the build didn't work for me, so I tried creating a directory
"openssl" in the ntp tree, and copied 33 header files from the OpenSSL
tree. Havin
[EMAIL PROTECTED] wrote:
> Are there any clear requirements in NTP/SNTP RFC docs about the UDP
> source address in
> all responses the same as the UDP target address in the original
> requests?
> I doubt it would be a UDP requirement because this is domain of upper
> protocols.
If you want to use
Martin Burnicki wrote:
>
> Hm, the process CPU affinity is not restricted to a single CPU. Ntpd has 4
> active threads, and only the CPU affinity of the clock interpolation thread
> is restricted to the first CPU since this is the only thread which calls
> QueryPerformanceCounter() and thus potent
Harlan,
This has come up several times over the years (I give you the parse
clocks as one approach). Here has been my reply on these occastions.
Almost all reference clock derivers can be designed as a state machine
which has largely been implemented in the reference clock interface.
There is
David J Taylor wrote:
> Danny Mayer wrote:
> []
>> With VS 2005, just open the dsw file and tell it to convert all the
>> project files. I recently add the necessary macros to the dsp files so
>> that I don't have to add a bunch of macros every time I pull in a new
>> tarball. I'm only building on
Guys,
In both the NTPv4 specification and reference implementation the
destination address used by the client when mobilizeing the association
and sending the request must match the source address when receiving the
response. This is a property of all RPC protocols known to me that use
address
Hi all,
After going through the NMEA ref.clock driver, it seems that the
original author has choosen values 0(GPXXX), 1(GPRMC), 2(GPGGA) and
4(GPGLL) for mode field so that multiple sentences can be selected. As
posted earlier reg. using the mode byte/field to support Accord GPS
Clock, fourth bit
>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (Hal Murray) writes:
Hal> I'd like to be able to say "Z3801A" rather than whatever line settings
Hal> it actually uses.
I agree and suggest:
http://support.ntp.org/bin/view/Dev/NewNtpConfFormat
as I did in a previous reply on the parent thr
>>> In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] (venu gopal) writes:
venu> Hi Harlan, Yes. I am volunteering to be the maintainer of the
venu> code.
Glad to hear it, thanks!
venu> Infact I'll be more than happy to do this. I have been a fan of
venu> open-source community since about si
Venu,
It is easy to add more bits to the mode word. How about 32? You and
other driver programmers should come to some loose agreement on how to
exploit these bits.
Dave
venu gopal wrote:
> Hi all,
>
> The 'mode' field a.k.a 'ttl' for NMEA reference driver is used
> to select the
>Perhaps the best way is to add a completely new command "refclock" and
>load it up with all kinds of options, including those now done by the
>fudge command. The command would not need the dotted quad, which could
>be replaced by the driver name already in a table. The syntax could in
>principle b
[EMAIL PROTECTED] wrote:
> Are there any clear requirements in NTP/SNTP RFC docs about the UDP
> source address in
> all responses the same as the UDP target address in the original
> requests?
> I doubt it would be a UDP requirement because this is domain of upper
> protocols.
Yes and no. The ba
Martin Burnicki wrote:
> David,
[]
> I had made a fresh installation of Vista and forgot to disable
> automatic sleep mode, so my overnight test failed and I had to run it
> once more over the last hours.
Been there, done that!
> The test machine is a Intel Pentium D 3 GHz (dual core) with Window
David,
David J Taylor wrote:
> Martin Burnicki wrote:
> []
>> I've just set up a new test under Vista, so let's see.
>>
>> What I can say right now is that the default tick adjustment value is
>> 156001 instead of 156250 which it used to be on earlier Windows
>> versions. Also the granularity of t
Hi all,
I am sorry, the mode field and corresponding configuration should be
as follows to preserve the existing NMEA sentences in the driver.
Mode value 8 => 9600, GPXXX
Mode value 9 => 9600, GPRMC
Mode value 10 => 9600, GPGGA
Mode value 11 => 9600, GPZDG (Accord custom NMEA sentence)
Mode valu
Martin Burnicki wrote:
>
> AFAIK the code in the SNTP subdirectory has not yet been ported to
> Windows ...
>
> Martin
We probably wron't try since that code is supposed to be rewritten. The
effort doesn't justify the cost.
Danny
___
questions mailing
Hal Murray wrote:
> I
>> I don't know; it seems to me better for the refclock driver to specify a
>> default set of comm parameters that will work for the "standard" device
>> that refclock supports, but have a universal mechanism that would allow
>> overriding those params from the config file
Harlan,
What planet are you coming from? You know I violently disagree with you
on the options thing and it has absolutely nothing to do with the html
documentation. The options thing is overkill, an unnecessary
complication and not really helpful in view of the available
documentation. I woul
Hi Hal,
The custom NMEA format has GPS time unlike standard NMEA which give
UTC. And the baudrate cannot be changed to 4800, it only works at 9600.
Things are not as simple as we think and we need to work to make things simple
I am looking for people who can help me in doing this.
The binary
Hi all,
The 'mode' field a.k.a 'ttl' for NMEA reference driver is used
to select the NMEA
sentence. I cannot use the unused fudge flags 'flag1' and 'flag4'
as they are unavailable
before the serial port is opened. Somehow I have to select both
the baudrate and the
NMEA sent
>Over the years and with some effort several drivers now support more
>than one device. All TrueTime models are supported by one driver; all
>Spectracom models by another and all telephone modem services by a
>third. With few exceptions, a NMEA radio is a NMEA radio and I strongly
>suspect man
I
>I don't know; it seems to me better for the refclock driver to specify a
>default set of comm parameters that will work for the "standard" device
>that refclock supports, but have a universal mechanism that would allow
>overriding those params from the config file and would work for any drive
> 1. Accord GPS Clock spits out NMEA at 9600 baudrate
The NMEA specs call for 4800. Is there some way to set
the Accord box to run at 4800? That seems only sensible
if they are in the NMEA market.
>2. It has custom NMEA format for GPS (and the driver is
> intended to use this )
23 matches
Mail list logo
