[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <92d17d76-2423-9ab2-8fe4-0b86a0be5a45@nvidia.com>
Date: Fri, 26 Mar 2021 15:41:51 +0300
From: Moshe Shemesh <moshe@...dia.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Adrian Pop <pop.adrian61@...il.com>,
Michal Kubecek <mkubecek@...e.cz>,
"Don Bollinger" <don@...bollingers.org>, <netdev@...r.kernel.org>,
"Vladyslav Tarasiuk" <vladyslavt@...dia.com>
Subject: Re: [RFC PATCH V5 net-next 0/5] ethtool: Extend module EEPROM dump
API
On 3/26/2021 1:41 AM, Andrew Lunn wrote:
> External email: Use caution opening links or attachments
>
>
> On Thu, Mar 25, 2021 at 04:56:50PM +0200, Moshe Shemesh wrote:
>> Ethtool supports module EEPROM dumps via the `ethtool -m <dev>` command.
>> But in current state its functionality is limited - offset and length
>> parameters, which are used to specify a linear desired region of EEPROM
>> data to dump, is not enough, considering emergence of complex module
>> EEPROM layouts such as CMIS 4.0.
>> Moreover, CMIS 4.0 extends the amount of pages that may be accessible by
>> introducing another parameter for page addressing - banks.
> This is looking much better.
>
> Do you have a version of ethtool using this new API? WIP code is
> O.K. I will add basic support to sfp.c and test it out on the devices
> i have.
Sure.
> Andrew
Powered by blists - more mailing lists