From: Benedikt Spranger <b.spranger@linutronix.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
netdev@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Kurt Kanzenbach <kurt@linutronix.de>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [RFC PATCH v2 2/2] Documentation: net: dsa: b53: Describe b53 configuration
Date: Tue, 2 Jul 2019 18:28:34 +0200 [thread overview]
Message-ID: <20190702182834.7d2eb022@mitra> (raw)
In-Reply-To: <20190701173550.GH30468@lunn.ch>
Am Mon, 1 Jul 2019 19:35:50 +0200
schrieb Andrew Lunn <andrew@lunn.ch>:
> > +Configuration without tagging support
> > +-------------------------------------
>
> How does this differ to the text you just added in the previous patch?
The b53 has some implementation specific detail:
The b53 DSA driver tags the CPU port in all VLANs, since otherwise any
PVID untagged VLAN programming would basically change the CPU port's
default PVID and make it untagged, undesirable.
This need some attention while configuring. Therefore the configuration
is slightly different to the generic one:
The following extra commands are needed on b53 single port and gateway
configuration:
bridge vlan del dev lan1 vid 1
bridge vlan del dev lan2 vid 1
On bridge config the following commands are not needed:
bridge vlan add dev lan1 vid 1 pvid untagged
bridge vlan add dev lan2 vid 1 pvid untagged
bridge vlan add dev lan3 vid 1 pvid untagged
> Do we need both?
I like full configuration examples. But it can also be done by
describing the changes. I would prefer both - description and full
script:
...
Configuration without tagging support
-------------------------------------
Older models (5325, 5365) support a different tag format that is not
supported yet. 539x and 531x5 require managed mode and some special
handling, which is also not yet supported. The tagging support is
disabled in these cases and the switch need a different configuration.
The configuration slightly differ from
the :ref:`dsa-vlan-configuration`.
+ The b53 tags the CPU port in all VLANs, since otherwise any PVID
+ untagged VLAN programming would basically change the CPU port's
+ default PVID and make it untagged, undesirable.
+ In difference to the configuration described
+ in :ref:`dsa-vlan-configuration` the default VLAN 1 has to be removed
+ from the slave interface configuration in single port and gateway
+ configuration, while there is no need to add an extra VLAN
+ configuration in the bridge showcase.
single port
~~~~~~~~~~~
...
Regards
Bene Spranger
prev parent reply other threads:[~2019-07-02 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 15:42 [RFC PATCH v2 0/2] Document the configuration of b53 Benedikt Spranger
2019-07-01 15:42 ` [RFC PATCH v2 1/2] Documentation: net: dsa: Describe DSA switch configuration Benedikt Spranger
2019-07-01 17:33 ` Andrew Lunn
2019-07-01 15:42 ` [RFC PATCH v2 2/2] Documentation: net: dsa: b53: Describe b53 configuration Benedikt Spranger
2019-07-01 17:35 ` Andrew Lunn
2019-07-02 16:28 ` Benedikt Spranger [this message]
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=20190702182834.7d2eb022@mitra \
--to=b.spranger@linutronix.de \
--cc=andrew@lunn.ch \
--cc=bigeasy@linutronix.de \
--cc=f.fainelli@gmail.com \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@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;
as well as URLs for NNTP newsgroup(s).