From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932407AbdKFOzw (ORCPT <rfc822;w@1wt.eu>);
        Mon, 6 Nov 2017 09:55:52 -0500
Received: from mail-pf0-f182.google.com ([209.85.192.182]:55008 "EHLO
        mail-pf0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753599AbdKFOzu (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 6 Nov 2017 09:55:50 -0500
X-Google-Smtp-Source: ABhQp+RmTMAAH1VnyYhBXlA6dx1nGliUqP2+xiCkVyLgZYQQTXorPpyYCp7SdYTbGajE4jkpGJfdgg==
Date: Mon, 6 Nov 2017 06:55:46 -0800
From: Richard Cochran <richardcochran@gmail.com>
To: Brandon Streiff <brandon.streiff@ni.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
        "David S. Miller" <davem@davemloft.net>,
        Florian Fainelli <f.fainelli@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
        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: <20171106145546.atfjkqf3xdxu4wyg@localhost>
References: <1506612341-18061-1-git-send-email-brandon.streiff@ni.com>
 <20170929094323.cwh2ubv4odknlyot@localhost>
 <20171008153821.w4pm6j43lpdvnpph@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20171008153821.w4pm6j43lpdvnpph@localhost>
User-Agent: NeoMutt/20170113 (1.7.2)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Sun, Oct 08, 2017 at 11:38:21AM -0400, Richard Cochran wrote:
> I will try to get my hands on some HW, perhaps by the end of October,
> in order to test and complete your driver...

I now have a 88E6352 to test your series on.  Unfortunately, it
doesn't really work. Here is what I did.

1. Gave one of the external switch ports an address (ifconfig ext0
   192.168.1.111)

2. Ran ptp4l with option 'free_running 1'.

When I run with Layer2 transport and the switch as master, it seems to
work.  Any other combination of role + transport fails.

| Switch Role | Tranport | Result                                         |
|-------------+----------+------------------------------------------------|
| master      | UDPv4    | no Delay_Resp appear at slave                  |
| master      | UDPv6    | no Delay_Resp appear at slave                  |
| master      | layer2   | seems okay                                     |
| slave       | layer2   | Announce messages not getting through to host? |

Have you tested any of this?

Do I need some special switch configuration first?

 
Thanks,
Richard