Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 8 Nov 2017 01:09:12 +0100
From:   Andrew Lunn <andrew@lunn.ch>
To:     Brandon Streiff <brandon.streiff@ni.com>
Cc:     Richard Cochran <richardcochran@gmail.com>,
        "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "David S. Miller" <davem@davemloft.net>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
        Erik Hons <erik.hons@ni.com>
Subject: Re: [PATCH net-next RFC 0/9] net: dsa: PTP timestamping for mv88e6xxx
Message-ID: <20171108000912.GF7601@lunn.ch>
References: <1506612341-18061-1-git-send-email-brandon.streiff@ni.com>
 <20170929094323.cwh2ubv4odknlyot@localhost>
 <20171008153821.w4pm6j43lpdvnpph@localhost>
 <20171106145546.atfjkqf3xdxu4wyg@localhost>
 <20171107181344.b4itrmd7atxkwc5x@localhost>
 <CO2PR04MB2184661473BE7E1B2C98A8449F510@CO2PR04MB2184.namprd04.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CO2PR04MB2184661473BE7E1B2C98A8449F510@CO2PR04MB2184.namprd04.prod.outlook.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Nov 07, 2017 at 08:56:05PM +0000, Brandon Streiff wrote:
> > Oops, I had "slaveOnly" set in my PC's configuration.  So layer2 seems
> > to work as expected.
> > 
> > Have you tested UDPv4?  It doesn't work.
> 
> I have not. Our usage has been focused on 802.1AS; the ptp4l settings we
> use are the following:
> 
> transportSpecific    0x1
> ptp_dst_mac          01:80:C2:00:00:0E
> p2p_dst_mac          01:80:C2:00:00:0E
> network_transport    L2
> delay_mechanism      P2P
> time_stamping        hardware
> 
> One thing that we're not doing (and probably should be) is configuring
> multicast frames to 01:1B:19:00:00:00 to be destined to the CPU port.
> (01:80:C2:00:00:0E is used for management, so the *_mgmt_rsvd2cpu()
> functions give us that "for free".) That might be necessary to make 1588
> L2 work properly. I don't know if that would affect 1588 L4, or if
> there's anything else missing to make L4 timestamping work from the HW
> perspective.

Is the application performing a join on the group? If so, on which
interface?

I've not tested many multicast applications with DSA. It is possible
we have bugs.

   Andrew


From 1583464000163838881@xxx Wed Nov 08 02:42:27 +0000 2017
X-GM-THRID: 1579797979616373237
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread