[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <93AF473E2DA327428DE3D46B72B1E9FD41139D98@CHN-SV-EXMX02.mchp-main.com>
Date: Fri, 17 Nov 2017 19:33:47 +0000
From: <Tristram.Ha@...rochip.com>
To: <andrew@...n.ch>
CC: <davem@...emloft.net>, <f.fainelli@...il.com>, <pavel@....cz>,
<arkadis@...lanox.com>, <UNGLinuxDriver@...rochip.com>,
<netdev@...r.kernel.org>
Subject: RE: [PATCH v1 net-next 0/7] net: dsa: microchip: Modify KSZ9477 DSA
driver in preparation to add other KSZ switch drivers
> On Thu, Nov 16, 2017 at 06:41:24PM -0800, Tristram.Ha@...rochip.com
> wrote:
> > From: Tristram Ha <Tristram.Ha@...rochip.com>
> >
> > This series of patches is to modify the original KSZ9477 DSA driver so
> > that other KSZ switch drivers can be added and use the common code.
>
> Hi Tristram
>
> http://vger.kernel.org/~davem/net-next.html
>
> It is better to send an RFC patchset while netdev is closed and not
> send it to David. He will shout at you otherwise.
Noted.
I really need to monitor the DSA discussion to better contribute to its success.
I just found out the DSA API set_addr was removed last month due to not
everybody is using it. It cited the Marvell switch was the only switch using that
API and found a new way to program the MAC address. But looking at that
driver I found it simply uses a randomized MAC address.
For big switch with many ports where the main function is forwarding that MAC
address may not matter. For small switch with 2 ports it acts more like an Ethernet
controller where the switch is mainly used for daisy chaining in a ring network the MAC
address can be used in feature like source address filtering.
Powered by blists - more mailing lists