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
| ||
|
Message-ID: <e7b49a60-4422-4f3f-3e77-d924f967e939@csgroup.eu> Date: Thu, 14 Sep 2023 10:06:34 +0000 From: Christophe Leroy <christophe.leroy@...roup.eu> To: Maxime Chevallier <maxime.chevallier@...tlin.com>, "davem@...emloft.net" <davem@...emloft.net> CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Andrew Lunn <andrew@...n.ch>, Jakub Kicinski <kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Florian Fainelli <f.fainelli@...il.com>, Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, Vladimir Oltean <vladimir.oltean@....com>, Oleksij Rempel <linux@...pel-privat.de>, Nicolò Veronese <nicveronese@...il.com>, "thomas.petazzoni@...tlin.com" <thomas.petazzoni@...tlin.com> Subject: Re: [RFC PATCH net-next 0/7] net: phy: introduce phy numbering Le 07/09/2023 à 11:23, Maxime Chevallier a écrit : > [Vous ne recevez pas souvent de courriers de maxime.chevallier@...tlin.com. Découvrez pourquoi ceci est important à https://aka.ms/LearnAboutSenderIdentification ] > > Hello everyone, > > This is the first RFC series introducing ethernet PHY numbering, in an > effort to better represent the link components and allow userspace to > configure these. > > As of today, PHY devices are hidden behind the struct net_device from > userspace, but there exists commands such as PLCA configuration, > cable-testing, soon timestamping, that actually target the phy_device. > > These commands rely on the ndev->phydev pointer to find the phy_device. > > However, there exists use-cases where we have multiple PHY devices > between the MAC and the front-facing port. The most common case right > now is when a PHY acts as a media-converter, and is wired to an SFP > port : > > [MAC] - [PHY] - [SFP][PHY] FWIW when thinking about multiple PHY to a single MAC, what comes to my mind is the SIS 900 board, and its driver net/ethernet/sis/sis900.c It has a function sis900_default_phy() that loops over all phys to find one with up-link then to put all but that one in ISOLATE mode. Then when the link goes down it loops again to find another up-link. I guess your series would also help in that case, wouldn't it ? Christophe
Powered by blists - more mailing lists