[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150226151830.GD8806@lunn.ch>
Date: Thu, 26 Feb 2015 16:18:30 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Rafa?? Mi??ecki <zajec5@...il.com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Andy Gospodarek <gospo@...ulusnetworks.com>,
"David S. Miller" <davem@...emloft.net>,
Network Development <netdev@...r.kernel.org>,
Jonas Gorski <jogo@...nwrt.org>,
Hauke Mehrtens <hauke@...ke-m.de>,
Felix Fietkau <nbd@...nwrt.org>, Jiri Pirko <jiri@...nulli.us>
Subject: Re: [PATCH] net: phy: b53: switchdev driver for Broadcom BCM53xx
switches
On Thu, Feb 26, 2015 at 03:58:40PM +0100, Rafa?? Mi??ecki wrote:
> On 25 February 2015 at 15:19, Andrew Lunn <andrew@...n.ch> wrote:
> >> 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.
Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists