I have just written a PHC driver for NTP and tested it on this system:
Supermicro SYS-50150EHF-D525 which has a pair of Intel 82574L NICs which
have IEEE 1588 hardware-based timestamping. I'm using NTP dev 4.2.7p397 on
Linux kernel 3.12 with linuxptp. One of the PHCs is sync'd via PTP to an FEI
On 2013-11-22, schmidt.r...@gmail.com wrote:
> I have just written a PHC driver for NTP and tested it on this system:
> Supermicro SYS-50150EHF-D525 which has a pair of Intel 82574L NICs which
> have IEEE 1588 hardware-based timestamping. I'm using NTP dev 4.2.7p397 on
> Linux kernel 3.12 with l
On 2013-11-22 09:19, schmidt.r...@gmail.com wrote:
I have just written a PHC driver for NTP and tested it on this system:
Supermicro SYS-50150EHF-D525 which has a pair of Intel 82574L NICs which have
IEEE 1588 hardware-based timestamping. I'm using NTP dev 4.2.7p397 onLinux
kernel 3.12 with lin
On Friday, November 22, 2013 12:38:36 PM UTC-5, unruh wrote:
> On 2013-11-22, schmidt.r...@gmail.com wrote:
>
> > I have just written a PHC driver for NTP and tested it on this system:
>
> > Supermicro SYS-50150EHF-D525 which has a pair of Intel 82574L NICs which
>
> > have IEEE 1588 hardware-
On 2013-11-22, Brian Inglis wrote:
> On 2013-11-22 09:19, schmidt.r...@gmail.com wrote:
>> I have just written a PHC driver for NTP and tested it on this system:
>> Supermicro SYS-50150EHF-D525 which has a pair of Intel 82574L NICs which
>> have
>> IEEE 1588 hardware-based timestamping. I'm usi
Rich,
Improving convergence time is important to the NTP Project.
If there's a bug in the code or in the algorithms let's identify and fix
it.
If there is a known "offset to true time" then let's increase support
for http://nwtime.org/projects/timestamp-api/ so it can start being
deployed and ap
On 2013-11-22 14:12, unruh wrote:
On 2013-11-22, Brian Inglis wrote:
On 2013-11-22 09:19, schmidt.r...@gmail.com wrote:
I have just written a PHC driver for NTP and tested it on this system:
Supermicro SYS-50150EHF-D525 which has a pair of Intel 82574L NICs which have
IEEE 1588 hardware-base
On Saturday, November 23, 2013 1:20:37 AM UTC-5, Brian Inglis wrote:
> On 2013-11-22 14:12, unruh wrote:
> My point is that without other indicators, these are just another bunch of
> ref clock
>
> timestamps being delivered into the discipline control loop.
>
> When these are known to be high q
schmidt.r...@gmail.com wrote:
My new prototype driver refclock_phc() uses as its clock the PTP
Hardware Clock (PHC) found on one of the newer LAN NICs which are PTP
(IEEE 1588) aware. This driver is producing phenomenal results (under
LINUX 3.12 with linuxPTP): the overlapping Allan deviation com
I do the latter. To use PTP to timestamp one would have to modify NTP source
outside of refclock_phc(), which we would not presume to do. However the PHC
loopstats has a standard deviation of 0.58 microseconds, so we are not far off
in using standard NTP timestamping.
Rich Schmidt
> Do you
schmidt.r...@gmail.com wrote:
I do the latter. To use PTP to timestamp one would have to modify NTP
source outside of refclock_phc(), which we would not presume to do.
However the PHC loopstats has a standard deviation of 0.58
microseconds, so we are not far off in using standard NTP
timestamping
schmidt.r...@gmail.com wrote:
My new prototype driver refclock_phc() uses as its clock the PTP
Hardware Clock (PHC) found on one of the newer LAN NICs which are PTP
(IEEE 1588) aware. This driver is producing phenomenal results (under
LINUX 3.12 with linuxPTP): the overlapping Allan deviation com
On Thu, Dec 12, 2013 at 09:59:03AM +0100, Martin Burnicki wrote:
> A major problem was that the standard NTP protocol doesn't support a
> way to send the captured time stamp of a previously sent packet to
> its client, as done by the so-called followup message in PTP.
ntpd has the peer and broadca
What about NTP's interleave mode (xleave)?
H
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
Harlan Stenn wrote:
What about NTP's interleave mode (xleave)?
Please see my reply to Miroslav.
Martin
--
Martin Burnicki
Meinberg Funkuhren
Bad Pyrmont
Germany
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questi
Miroslav Lichvar wrote:
On Thu, Dec 12, 2013 at 09:59:03AM +0100, Martin Burnicki wrote:
A major problem was that the standard NTP protocol doesn't support a
way to send the captured time stamp of a previously sent packet to
its client, as done by the so-called followup message in PTP.
ntpd ha
Martin Burnicki wrote:
There are network switches out there which are PTP-aware and also
timestamp incoming and outgoing PTP packets to compensate the introduced
packet delay in some way, but there are no switches (AFAIK) which can do
this with NTP packets, so even if you used hardware time sta
Uwe Klein wrote:
Martin Burnicki wrote:
There are network switches out there which are PTP-aware and also
timestamp incoming and outgoing PTP packets to compensate the
introduced packet delay in some way, but there are no switches (AFAIK)
which can do this with NTP packets, so even if you used h
18 matches
Mail list logo
