networking/dsa/dsa.rst

52 on Port-based VLAN IDs).
262 - inability to configure specific VLAN IDs / trunking VLANs between switches
323 more specifically with its VLAN filtering portion when configuring VLANs on top
330 As of today, the only SWITCHDEV objects supported by DSA are the FDB and VLAN
370   a Port-based VLAN ID for each port and allowing only the CPU port and the
497 Bridge VLAN filtering
501   configured for turning on or off VLAN filtering. If nothing specific needs to
503   When VLAN filtering is turned on, the hardware must be programmed with
504   rejecting 802.1Q frames which have VLAN IDs outside of the programmed allowed
505   VLAN ID map/rules.  If there is no PVID programmed into the switch port,
507   accept any 802.1Q frames irrespective of their VLAN ID, and untagged frames are
511   configuration of a VLAN on the given port. If the operation is not supported
516 - ``port_vlan_add``: bridge layer function invoked when a VLAN is configured
519 - ``port_vlan_del``: bridge layer function invoked when a VLAN is removed from the
523   function that the driver has to call for each VLAN the given port is a member
528   specified address in the specified VLAN Id in the forwarding database
529   associated with this VLAN ID. If the operation is not supported, this
533 .. note:: VLAN ID 0 corresponds to the port private database, which, in the context
534         of DSA, would be its port-based VLAN, used by the associated bridge device.
538   the specified MAC address from the specified VLAN ID if it was mapped into
553   specified address in the specified VLAN ID in the forwarding database
554   associated with this VLAN ID.
556 .. note:: VLAN ID 0 corresponds to the port private database, which, in the context
557         of DSA, would be its port-based VLAN, used by the associated bridge device.
561   the specified MAC address from the specified VLAN ID if it was mapped into