[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ccf7ea15-203e-4860-a85d-31641a26c872@lunn.ch>
Date: Mon, 16 Sep 2024 18:12:32 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Maxime Chevallier <maxime.chevallier@...tlin.com>
Cc: Daniel Golle <daniel@...rotopia.org>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
Kory Maincent <kory.maincent@...tlin.com>,
Edward Cree <ecree.xilinx@...il.com>,
Paolo Abeni <pabeni@...hat.com>, Jakub Kicinski <kuba@...nel.org>,
Eric Dumazet <edumazet@...gle.com>,
"David S. Miller" <davem@...emloft.net>,
John Crispin <john@...ozen.org>
Subject: Re: ethtool settings and SFP modules with PHYs
> A notification would indeed be better, and is something I can prototype
> quickly. I was hesitating to add that, but as you show interest in
> this, I'm OK to move forward on that :)
This might need further brainstorming. What are we actually interested
in?
The EEPROM has been read, we know what sort of SFP it is?
It happens to be a copper SFP, we know what MDIO over I2C protocol to
use, it responds, and the PHY device has been created? Does the SFP
layer actually know this? Are we actually adding a notification for
any PHY, not just an SFP PHY?
Andrew
Powered by blists - more mailing lists