On Thu, Aug 26, 2021 at 05:13:26PM +0300, Vladimir Oltean wrote:

On Thu, Aug 26, 2021 at 01:29:56PM +0800, DENG Qingfang wrote:

quoted

The comment says the VLAN tag need to be combined with the special tag in
order to perform VLAN table lookup,

It does say this.

quoted

so we can set its destination port vector to all zeroes and the switch
will forward it like a data frame (TX forward offload),

And it does not say this. So this is supported after all with mt7530?
Are you looking to add support for that?

I already run-tested that, it works, as long as there is only one bridge.

quoted

but as we allow multiple bridges which are either VLAN-unaware or
VLAN-aware with the same VID, there is no way to determine the
destination bridge unless we maintain some VLAN translation mapping.

What does "VLAN translation mapping" mean, practically?

It's just VLAN remapping, as you stated below.

Other drivers which cannot remap VIDs to internal VLANs just restrict a
single VLAN-aware bridge, and potentially multiple VLAN-unaware ones.

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek