diff options
| author | 2025-11-03 16:42:45 -0800 | |
|---|---|---|
| committer | 2025-11-03 16:42:46 -0800 | |
| commit | 7942602b09497ff1505c9385aefd38c69e16235e (patch) | |
| tree | 575f337261037b36a271b002d25727f0b757fc87 /scripts/basic/git:/ssh:/git@git.zx2c4.com | |
| parent | Merge branch 'net-dsa-b53-fix-bcm63xx-rgmii-user-ports-with-speed-1g' (diff) | |
| parent | net: dsa: b53: properly bound ARL searches for < 4 ARL bin chips (diff) | |
| download | wireguard-linux-7942602b09497ff1505c9385aefd38c69e16235e.tar.xz wireguard-linux-7942602b09497ff1505c9385aefd38c69e16235e.zip | |
Merge branch 'net-dsa-b53-minor-fdb-related-fixes'
Jonas Gorski says:
====================
net: dsa: b53: minor fdb related fixes
While investigating and fixing/implenting proper ARL support for
bcm63xx, I encountered multiple minor issues in the current ARL
implementation:
* The ARL multicast support was not properly enabled for older chips,
and instead a potentially reserved bit was toggled.
* While traversing the ARL table, "Search done" triggered one final
entry which will be invalid for 4 ARL bin chips, and failed to stop
the search on chips with only one result register.
* For chips where we have only one result register, we only traversed at
most half the maximum entries.
I also had a fix for IVL_SVL_SELECT which is only valid for some chips,
but since this would only have an effect for !vlan_enabled, and we
always have that enabled, it isn't really worth fixing (and rather drop
the !vlan_enabled paths).
====================
Link: https://patch.msgid.link/20251102100758.28352-1-jonas.gorski@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'scripts/basic/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions
