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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 11 Dec 2022 13:02:26 +0100 From: Andrew Lunn <andrew@...n.ch> To: "mengyuanlou@...-swift.com" <mengyuanlou@...-swift.com> Cc: netdev@...r.kernel.org, jiawenwu@...stnetic.com Subject: Re: [PATCH net-next v2] net: ngbe: Add ngbe mdio bus driver. > > If you don't have the I2C bus, i'm wondering how you can actually > > driver the SFP and the MAC. You have no idea what has been > > inserted. Is it actually an SFF, not an SFP? Do you have any of the > > GPIOs normally associated with an SFP? TX_DISABLE, LOS, TX_FAULT? > > > 1、Yeah. We can't know what module is inserted That is a very odd design. You are going to get all sorts of reports of it being broken when some random module is interested. If it was my design, i would not use an SFP socket. I would solder down an SFF. They should be pin compatible. You then know exactly what you have, and how the MAC needs to be configured. Andrew
Powered by blists - more mailing lists