Thread (65 messages) 65 messages, 8 authors, 2015-03-04

Re: [PATCH RFC 2/2] net: dsa: bcm_sf2: implement HW bridging operations

From: Guenter Roeck <linux@roeck-us.net>
Date: 2015-02-19 05:59:58

On Wed, Feb 18, 2015 at 06:48:19PM -0800, Florian Fainelli wrote:
On 17/02/15 11:26, Florian Fainelli wrote:
quoted
Update the Broadcom Starfighter 2 switch driver to implement the
join/leave/stp_update callbacks required for basic hardware bridging
support.

There is not much to be done at the driver level but translating the
STP state from Linux to their HW values.

Joining a bridge means that the joining port and the other port members
need to be in the same VLAN membership as the CPU, while leaving the
bridge puts the port back into a separate VLAN membership with only the
CPU.
I found a couple additional issues while testing:

- manipulating UP/DOWN state of interfaces that are part of a bridge
would not restore their bridge membership

- removing an interface from a bridge and bringing it back up would
leave it in blocked state
Is this a problem with your implementation for sf2 or a generic problem
with the first patch, such as some missing state transitions ?

For sf2, you might have to set the port state as well as the bridge
association in the port_setup function. That is of course just a
wild guess.

Thanks,
Guenter
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help