public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@kernel-space.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>
Subject: Re: dsa: mv88e6xxx: mv88e6321 rsvd2cpu
Date: Wed, 26 Apr 2023 15:59:39 +0200	[thread overview]
Message-ID: <141aebfc-46a3-7ac3-c984-dcd549124c05@kernel-space.org> (raw)
In-Reply-To: <5056756b-5371-4e7c-9016-8234352f9033@lunn.ch>

Hi Andrew,

On 26/04/23 3:35 PM, Andrew Lunn wrote:
> On Wed, Apr 26, 2023 at 10:12:28AM +0200, Angelo Dureghello wrote:
>> Hi all,
>>
>> working on some rstp stuff at userspace level, (kernel stp
>> disabled), i have seen bpdu packets was forwarded over bridge
>> ports generating chaos and loops. As far as i know, 802.1d asks
>> bpdus are not forwarded.
>>
>> Finally found a solution, adding mv88e6185_g2_mgmt_rsvd2cpu()
>> for mv88e6321.
>> Is it a proper solution ? Is there any specific reason why
>> rsvd2cpu was not implemented for my 6321 ?
>> I can send the patch i am using actually. in case.
> 
> Should it be mv88e6185_g2_mgmt_rsvd2cpu() or
> mv88e6352_g2_mgmt_rsvd2cpu()? Does the 6321 only support
> 01:80:c2:00:00:0x or does it have 01:80:c2:00:00:2x as well?
> 
> Please do send a patch, and include a Fixes: tag.
> 

you are right, it supports also the 01:80:c2:00:00:2x,
will test that too, and will send patch v2.

>         Andrew


Thanks,
angelo

  reply	other threads:[~2023-04-26 13:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26  8:12 dsa: mv88e6xxx: mv88e6321 rsvd2cpu Angelo Dureghello
2023-04-26 13:23 ` Vladimir Oltean
2023-04-26 13:35 ` Andrew Lunn
2023-04-26 13:59   ` Angelo Dureghello [this message]
2023-04-26 14:46     ` Vladimir Oltean

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=141aebfc-46a3-7ac3-c984-dcd549124c05@kernel-space.org \
    --to=angelo@kernel-space.org \
    --cc=andrew@lunn.ch \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    /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