Dear everyone (Mr. Keller in particular), in the process of fiddling with an addon i210-T1 received today (original Intel board SKU) I have discovered minor havoc in my previously posted data.
Over the past few days/weeks I was delighted at how marvellous the
onboard i219LM was, while in fact, it turns out that I've been using
the second onboard NIC, the i210, all along for PTP.
All the praise goes to the i210. The i219LM is inferior in my PC.
I'm re-attaching some samples from a running ptp4l.
The files also contain a corresponding dump of ethtool -T .
I was originally orienting myself by the contents of "dmesg". By the
eth0 vs. eth1 originally reported upon device detection.
Only today I started to smell a rat (because the addon i210 behaved
so very good) and after some fumbling in dmesg, I have noticed that
systemd would rename (swap) eth1 for eth0, all along, probably since
my kernel upgrade (which I did very early on).
Today with the addon board, systemd does a triple rename:
eth0 -> eth1
eth1 -> eth2
eth2 -> eth0
:-)
Trying to trace the renames in dmesg is prone to confusion.
Ultimately my favourite way of mapping the netdevice names
to PCI devices is a combination of the following two commands:
ethtool -i <your_eth_device>
and
lspci
The output of ethtool -i contains a row labeled "bus-info", which
quotes the familiar bus:device.function triplet, matching those
listed by lspci.
Which means that I have a tool that's capable of HW timestamping
with an error within maybe 20-30 ns. Now for the PPS input and
distribution across some 4 boards... I've already ordered some
74LVC1G125 to work as level shifters.
Frank Rysanek
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: i210_onboard_arbor.txt
Date: 11 Dec 2017, 15:06
Size: 2576 bytes.
Type: Unix-text
i210_onboard_arbor.txt
Description: Binary data
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: i219LM_onboard_arbor_PCH_LOM.txt
Date: 11 Dec 2017, 15:05
Size: 2729 bytes.
Type: Unix-text
i219LM_onboard_arbor_PCH_LOM.txt
Description: Binary data
The following section of this message contains a file attachment
prepared for transmission using the Internet MIME message format.
If you are using Pegasus Mail, or any other MIME-compliant system,
you should be able to save it or view it from within your mailer.
If you cannot, please ask your system administrator for assistance.
---- File information -----------
File: i210_addon_intel_original_i210-T1.txt
Date: 11 Dec 2017, 15:07
Size: 2504 bytes.
Type: Unix-text
i210_addon_intel_original_i210-T1.txt
Description: Binary data
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
