On 26 February 2015 at 16:18, Andrew Lunn [off-list ref] wrote:

On Thu, Feb 26, 2015 at 03:58:40PM +0100, Rafa?? Mi??ecki wrote:

quoted

On 25 February 2015 at 15:19, Andrew Lunn [off-list ref] wrote:

quoted

quoted

What do you mean by these recent patches? Has DSA recently received a
support for bridging ports in the hardware? Like setting VLANs using
some "bridge" comment (nl API) or something? Because I'm not aware of
that.

Yes. Scan over netdev list for the last week. e.g:

http://comments.gmane.org/gmane.linux.network/350754

Hm, I can see it was actually merged to the net-next already:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=bb66be1c549a0760500cfad404b3d79a136d0e44

But this dsa implementation is still totally unclear to me. So I can
see we now have
1) port_join_bridge
2) port_leave_bridge

How does it allow me to bridge few ports with specifying PVID /
(UN)TAG for some of them?

How about going back to the beginning. Look at the Starfigher 2 DSA
driver. Do you have similar registers? Can you map the Starfigher code
onto the b53 registers? If so, just write a new driver following the
Starfigher as a reference.

It doesn't really answer my question as I don't see functionality I'm
looking for in bcm_sf2. I don't see it handling (un)tagging or PVID
anywhere. It makes me believe such features are not implemented (and
not configurable) using bridges/dsa at all. Can you any API related to
untagging / PVID?

-- 
Rafał