From: David Miller <davem@davemloft.net>
To: andrew@lunn.ch
Cc: vivien.didelot@savoirfairelinux.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com
Subject: Re: [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185
Date: Mon, 04 Apr 2016 21:31:57 -0400 (EDT) [thread overview]
Message-ID: <20160404.213157.1584495549318748510.davem@davemloft.net> (raw)
In-Reply-To: <20160404021313.GB22003@lunn.ch>
From: Andrew Lunn <andrew@lunn.ch>
Date: Mon, 4 Apr 2016 04:13:13 +0200
> On Thu, Mar 31, 2016 at 04:53:40PM -0400, Vivien Didelot wrote:
>> All packets passing through a switch of the 6185 family are currently all
>> directed to the CPU port. This means that port bridging is software driven.
>>
>> To enable hardware bridging for this switch family, we need to implement the
>> port mapping operations, the FDB operations, and optionally the VLAN operations
>> (for 802.1Q and VLAN filtering aware systems).
>>
>> However this family only has 256 FDBs indexed by 8-bit identifiers, opposed to
>> 4096 FDBs with 12-bit identifiers for other families such as 6352. It also
>> doesn't have dedicated FID registers for ATU and VTU operations.
>>
>> This patchset fixes these differences, and enable hardware bridging for 6185.
>
> Hi Vivien
>
> I added a test for in chip 6185 bridging, and it worked as expected.
>
> Tested-by: Andrew Lunn <andrew@lunn.ch>
Series applied to net-next, thanks.
prev parent reply other threads:[~2016-04-05 1:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 20:53 [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 Vivien Didelot
2016-03-31 20:53 ` [PATCH net-next v2 1/6] net: dsa: mv88e6xxx: protect SID register access Vivien Didelot
2016-03-31 20:53 ` [PATCH net-next v2 2/6] net: dsa: mv88e6xxx: protect FID registers access Vivien Didelot
2016-03-31 20:53 ` [PATCH net-next v2 3/6] net: dsa: mv88e6xxx: variable number of databases Vivien Didelot
2016-03-31 20:53 ` [PATCH net-next v2 4/6] net: dsa: mv88e6xxx: support 256 databases Vivien Didelot
2016-03-31 20:53 ` [PATCH net-next v2 5/6] net: dsa: mv88e6xxx: map destination addresses for 6185 Vivien Didelot
2016-03-31 20:53 ` [PATCH net-next v2 6/6] net: dsa: mv88e6131: enable hardware bridging Vivien Didelot
2016-04-01 12:45 ` [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 Andrew Lunn
2016-04-01 13:38 ` Vivien Didelot
2016-04-04 2:13 ` Andrew Lunn
2016-04-05 1:31 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160404.213157.1584495549318748510.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).