[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YF46FI4epRGwlyP8@lunn.ch>
Date: Fri, 26 Mar 2021 20:46:28 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Don Bollinger <don@...bollingers.org>
Cc: 'Jakub Kicinski' <kuba@...nel.org>, arndb@...db.de,
gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
brandon_chuang@...e-core.com, wally_wang@...ton.com,
aken_liu@...e-core.com, gulv@...rosoft.com, jolevequ@...rosoft.com,
xinxliu@...rosoft.com, 'netdev' <netdev@...r.kernel.org>,
'Moshe Shemesh' <moshe@...dia.com>
Subject: Re: [PATCH v2] eeprom/optoe: driver to read/write SFP/QSFP/CMIS
EEPROMS
> In my community, the SFP/QSFP/CMIS devices (32 to 128 of them per switch)
> often cost more than the switch itself. Consumers (both vendors and
> customers) extensively test these devices to ensure correct and reliable
> operation. Then they buy them literally by the millions. Quirks lead to
> quick rejection in favor of reliable parts from reliable vendors. In this
> environment, for completely different reasons, optoe does not need to handle
> quirks.
Well, if optoe were to be merged, it would not be just for your
community. It has to work for everybody who wants to use the Linux
kernel with an SFP. You cannot decide to add a KAPI which just
supports a subset of SFPs. It needs to support as many as possible,
warts and all.
So how would you handle these SFPs with the optoe KAPI?
Andrew
Powered by blists - more mailing lists