On Tue, Jun 17, 2014 at 12:26:27PM +0100, Andrei Perietanu wrote:

> ethtool -T eth1
> Time stamping parameters for eth1:
> Capabilities:
>     hardware-transmit     (SOF_TIMESTAMPING_TX_HARDWARE)
>     software-transmit     (SOF_TIMESTAMPING_TX_SOFTWARE)
>     hardware-receive      (SOF_TIMESTAMPING_RX_HARDWARE)
>     software-receive      (SOF_TIMESTAMPING_RX_SOFTWARE)
>     software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
>     hardware-raw-clock    (SOF_TIMESTAMPING_RAW_HARDWARE)
> PTP Hardware Clock: 1
> Hardware Transmit Timestamp Modes:
>     off                   (HWTSTAMP_TX_OFF)
>     on                    (HWTSTAMP_TX_ON)
> Hardware Receive Filter Modes:
>     none                  (HWTSTAMP_FILTER_NONE)
>     all                   (HWTSTAMP_FILTER_ALL)
>     ptpv1-l4-sync         (HWTSTAMP_FILTER_PTP_V1_L4_SYNC)
>     ptpv1-l4-delay-req    (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ)
>     ptpv2-l4-sync         (HWTSTAMP_FILTER_PTP_V2_L4_SYNC)
>     ptpv2-l4-delay-req    (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ)
>     ptpv2-l2-sync         (HWTSTAMP_FILTER_PTP_V2_L2_SYNC)
>     ptpv2-l2-delay-req    (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ)
>     ptpv2-event           (HWTSTAMP_FILTER_PTP_V2_EVENT)
>     ptpv2-sync            (HWTSTAMP_FILTER_PTP_V2_SYNC)
>     ptpv2-delay-req       (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ)

You have hardware time stamping...

> I use this config file:
> [global]
> verbose               1
> time_stamping         software
                        ^^^^^^^^

and so you should use it by saying "hardware" here. (Or just omit this
line, since HW time stamping is the default.)

> tx_timestamp_timeout  1000
> 
> and when I run  *sudo ptp4l -i eth1 -f /etc/ptp4l.conf*   I get:
> ptp4l[519792.941]: port 1: INITIALIZING to LISTENING on INITIALIZE
> ptp4l[519792.941]: port 0: INITIALIZING to LISTENING on INITIALIZE
> ptp4l[519799.549]: port 1: LISTENING to MASTER on
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> ptp4l[519799.549]: selected best master clock 002590.fffe.f2c1e4
> ptp4l[519799.549]: assuming the grand master role
> 
> 
> After this it seams to just...hang; there no other activity.  Any ideas?

This is the expected behavior when there is only on PTP node on the
network. Do you have another node to test with?

If not, you can patch your igb/eth0 to the e1000e/eth1 and run two
instances of ptp4l. Then you should see some more activity.

HTH,
Richard

------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to