netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Waldekranz <tobias@waldekranz.com>
To: Fabio Estevam <festevam@gmail.com>, Andrew Lunn <andrew@lunn.ch>,
	Vladimir Oltean <olteanv@gmail.com>
Cc: "Florian Fainelli" <f.fainelli@gmail.com>,
	"Steffen Bätz" <steffen@innosonix.de>,
	netdev <netdev@vger.kernel.org>
Subject: Re: mv88e6320: Failed to forward PTP multicast
Date: Wed, 10 May 2023 23:34:49 +0200	[thread overview]
Message-ID: <87pm77dg5i.fsf@waldekranz.com> (raw)
In-Reply-To: <CAOMZO5DSSQY5fa5vTmDbCxu1x2ZRdyB2kTqrkw5bRg94_-34zg@mail.gmail.com>


Hi Fabio,

On ons, maj 10, 2023 at 11:05, Fabio Estevam <festevam@gmail.com> wrote:
> On Fri, May 5, 2023 at 10:02 AM Andrew Lunn <andrew@lunn.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,

  parent reply	other threads:[~2023-05-10 21:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04 18:39 mv88e6320: Failed to forward PTP multicast Fabio Estevam
2023-05-04 19:21 ` Andrew Lunn
2023-05-04 19:40   ` Fabio Estevam
2023-05-04 19:55     ` Andrew Lunn
2023-05-05 11:27     ` Fabio Estevam
2023-05-05 13:02       ` Andrew Lunn
2023-05-05 14:03         ` Fabio Estevam
2023-05-10 14:05         ` Fabio Estevam
2023-05-10 18:28           ` Vladimir Oltean
2023-05-11 11:03             ` Fabio Estevam
2023-05-11 11:46               ` Vladimir Oltean
2023-05-16 14:12                 ` Fabio Estevam
2023-05-16 16:29                   ` Andrew Lunn
2023-05-17 16:51                     ` Vladimir Oltean
2023-05-10 21:34           ` Tobias Waldekranz [this message]
2023-05-11 11:16             ` Fabio Estevam
2023-05-11 11:56               ` Tobias Waldekranz
2023-05-16 18:10                 ` Fabio Estevam
2023-05-17 16:53                   ` Vladimir Oltean
2023-05-17 17:07                     ` Andrew Lunn
2023-05-17 21:42                       ` Tobias Waldekranz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pm77dg5i.fsf@waldekranz.com \
    --to=tobias@waldekranz.com \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=festevam@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=steffen@innosonix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).