[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pm77dg5i.fsf@waldekranz.com>
Date: Wed, 10 May 2023 23:34:49 +0200
From: Tobias Waldekranz <tobias@...dekranz.com>
To: Fabio Estevam <festevam@...il.com>, Andrew Lunn <andrew@...n.ch>,
Vladimir Oltean <olteanv@...il.com>
Cc: Florian Fainelli <f.fainelli@...il.com>, Steffen Bätz
<steffen@...osonix.de>, netdev <netdev@...r.kernel.org>
Subject: Re: mv88e6320: Failed to forward PTP multicast
Hi Fabio,
On ons, maj 10, 2023 at 11:05, Fabio Estevam <festevam@...il.com> wrote:
> On Fri, May 5, 2023 at 10:02 AM Andrew Lunn <andrew@...n.ch> wrote:
>
>> I'm not too familiar with all this VLAN stuff. So i could be telling
>> your wrong information.... 'self' is also importing in way's i don't
>> really understand. Vladimir and Tobias are the experts here.
>
> Vladimir and Tobias,
>
> Would you have any suggestions as to how to allow PTP multicast to be
> forwarded when
> vlan_filtering is active?
If possible, could you install mdio-tools and paste the output of `mvls`
on your board from the two configurations above?
Unfortunately, you will have to patch it to support your device. Based
on a quick view of the datasheet, this should probably work:
diff --git a/src/mvls/mvls.c b/src/mvls/mvls.c
index 3ced04a..d4442c9 100644
--- a/src/mvls/mvls.c
+++ b/src/mvls/mvls.c
@@ -195,6 +195,16 @@ const struct chip chips[] = {
.family = &opal_family,
.n_ports = 11,
},
+ {
+ .id = "Marvell 88E6320",
+ .family = &opal_family,
+ .n_ports = 7,
+ },
+ {
+ .id = "Marvell 88E6321",
+ .family = &opal_family,
+ .n_ports = 7,
+ },
{
.id = "Marvell 88E6352",
.family = &opal_family,
Powered by blists - more mailing lists