Hello,
Harlan Stenn schrieb:
In article 4948f81b$0$29004$9b622...@news.freenet.de, Juergen Kosel
juergen.ko...@freenet.de writes:
And I also don't understand what you mean by computing time is a concern.
Is the overhead of a subroutine call that significant in your application?
it would
Hello,
Harlan Stenn schrieb:
In article 4944eab4$0$12693$9b622...@news.freenet.de, Juergen Kosel
juergen.ko...@freenet.de writes:
Juergen Hello, Greg Dowd schrieb:
I'm not quite sure what you mean. A reference clock doesn't compute an
offset, it acquires, formats and returns a time value
Hello,
Greg Dowd schrieb:
I'm not quite sure what you mean. A reference clock doesn't compute an
offset, it acquires, formats and returns a time value from an external
source. NTP takes care of the rest.
ntpd reads the time of a reference clock with a reference clock driver.
My problem was,
Hello,
I have a system with hardware support for PTP (IEEE 1588 time
synchronisation) [ http://en.wikipedia.org/wiki/Precision_Time_Protocol ].
So the system can read from two 32 bit registers seconds and nanoseconds
since 1.1.1970. It appears like the system time, but is n't the system time.
To