Hi Florian,
Florian Fainelli <f.fainelli@xxxxxxxxx> writes:
> bridge vlan add vid 2 dev br0 self
> -> CPU port gets programmed
> bridge vlan add vid 2 dev port0
> -> port0 (switch port 0) gets programmed
Although this is not specific to this patch, I'd like to point out that
this seems not to be the behavior bridge expects.
The bridge manpage says:
bridge vlan add - add a new vlan filter entry
...
self the vlan is configured on the specified physical device.
Required if the device is the bridge device.
master the vlan is configured on the software bridge (default).
So if I'm not mistaken, the switch chip must be programmed only when the
bridge command is called with the "self" attribute. Without it, only
software configuration must be made, like what happens when the driver
returns -EOPNOTSUPP.
Currently, both commands below program the hardware:
# bridge vlan add vid 2 dev port0 [master]
# bridge vlan add vid 2 dev port0 [master] self
Jiri, what do you think? Is there a reason for switchdev not to be
consistent with the bridge doc, or should this be fixed?
Thanks,
Vivien
