netdev - Re: STMMAC Ethernet Driver support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2139624b-e098-457a-bda4-0387d576b53a@lunn.ch>
Date: Mon, 11 Dec 2023 17:16:03 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Richard Tresidder <rtresidd@...ctromag.com.au>
Cc: Jakub Kicinski <kuba@...nel.org>, vinschen@...hat.com,
	netdev@...r.kernel.org
Subject: Re: STMMAC Ethernet Driver support

> We use the SOC's internal  STMMAC interface to connect to a Marvel switch IC
> and expose each port individually using vlan, I'd forgot that part.
> It's an  88E6352-xx-TFJ2I000  device utilising the 'marvell,mv88e6085'
> compatible driver  in drivers\net\dsa\mv88e6xxx

Its odd you need VLANs. Each port should already be exposed to the
host as netdev interfaces. That is what DSA does.

     Andrew