Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-06-02 Thread Vivien Didelot
Hi Scott, On Jun 2, 2015, at 2:18 AM, Scott Feldman sfel...@gmail.com wrote: > On Mon, Jun 1, 2015 at 5:18 PM, Vivien Didelot > wrote: >> >> On May 29, 2015, at 1:02 AM, Scott Feldman sfel...@gmail.com wrote: >>> On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot >>> wrote: This RFC is based o

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-06-01 Thread Scott Feldman
On Mon, Jun 1, 2015 at 5:18 PM, Vivien Didelot wrote: > > On May 29, 2015, at 1:02 AM, Scott Feldman sfel...@gmail.com wrote: >> On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot >> wrote: >>> This RFC is based on v4.1-rc3. >>> >>> It is meant to get a glance to the commits responsible to implemen

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-06-01 Thread Vivien Didelot
On May 29, 2015, at 1:02 AM, Scott Feldman sfel...@gmail.com wrote: > On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot > wrote: >> This RFC is based on v4.1-rc3. >> >> It is meant to get a glance to the commits responsible to implement the >> necessary NDOs between DSA and the Marvell 88E6352 swi

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-06-01 Thread Florian Fainelli
On 31/05/15 14:21, Scott Feldman wrote: >> Hi Scott, >> >> If I understand you correctly, that means we would expect users to >> use bridge commands even on non-bridged dsa ports. I don't think we can >> make this kind of assumption. Users will expect configure VLANs on >> non-bridge ports as they

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-31 Thread Scott Feldman
On Sun, May 31, 2015 at 10:06 AM, Guenter Roeck wrote: > On 05/31/2015 09:48 AM, Scott Feldman wrote: >> >> On Fri, May 29, 2015 at 3:42 PM, Guenter Roeck wrote: >>> >>> Scott, >>> >>> >>> On 05/28/2015 10:02 PM, Scott Feldman wrote: On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-31 Thread Guenter Roeck
On 05/31/2015 09:48 AM, Scott Feldman wrote: On Fri, May 29, 2015 at 3:42 PM, Guenter Roeck wrote: Scott, On 05/28/2015 10:02 PM, Scott Feldman wrote: On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot wrote: This RFC is based on v4.1-rc3. It is meant to get a glance to the commits respons

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-31 Thread Scott Feldman
On Fri, May 29, 2015 at 3:42 PM, Guenter Roeck wrote: > Scott, > > > On 05/28/2015 10:02 PM, Scott Feldman wrote: >> >> On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot >> wrote: >>> >>> This RFC is based on v4.1-rc3. >>> >>> It is meant to get a glance to the commits responsible to implement the

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-29 Thread Guenter Roeck
Scott, On 05/28/2015 10:02 PM, Scott Feldman wrote: On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot wrote: This RFC is based on v4.1-rc3. It is meant to get a glance to the commits responsible to implement the necessary NDOs between DSA and the Marvell 88E6352 switch driver. With this suppor

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-29 Thread Vivien Didelot
Hi Scott, On May 29, 2015, at 1:02 AM, Scott Feldman sfel...@gmail.com wrote: > On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot > wrote: >> This RFC is based on v4.1-rc3. >> >> It is meant to get a glance to the commits responsible to implement the >> necessary NDOs between DSA and the Marvell 8

Re: [RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-28 Thread Scott Feldman
On Thu, May 28, 2015 at 2:37 PM, Vivien Didelot wrote: > This RFC is based on v4.1-rc3. > > It is meant to get a glance to the commits responsible to implement the > necessary NDOs between DSA and the Marvell 88E6352 switch driver. > > With this support, I am able to create VLANs with (un)tagged p

[RFC 0/3] DSA and Marvell 88E6352 802.1q support

2015-05-28 Thread Vivien Didelot
This RFC is based on v4.1-rc3. It is meant to get a glance to the commits responsible to implement the necessary NDOs between DSA and the Marvell 88E6352 switch driver. With this support, I am able to create VLANs with (un)tagged ports, setting their default VID, from a bridge. To create a bridg