[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <A6AA2EF896BED345B0F23520D832A4B107C5A5@SJEXCHMB05.corp.ad.broadcom.com>
Date: Mon, 14 May 2012 18:57:00 +0000
From: "Yaniv Rosner" <yaniv.rosner@...adcom.com>
To: "Stuart Hodgson" <smhodgson@...arflare.com>,
"Ben Hutchings" <bhutchings@...arflare.com>
cc: "David Miller" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Eilon Greenstein" <eilong@...adcom.com>
Subject: RE: [PATCH ethtool] Add command to dump module EEPROM
> On 14/05/12 15:18, Ben Hutchings wrote:
> > On Mon, 2012-05-14 at 18:13 +0300, Yaniv Rosner wrote:
> >> Hi Ben,
> >> This patch adds a new option to dump (SFP+, XFP, ...) module EEPROM following
> >> recent support to kernel side. Below some examples:
> >>
> >> bash-3.00# ethtool -m eth1 offset 0x14 length 32 raw on
> >> JDSU PLRXPLSCS432
> >>
> >> bash-3.00# ethtool -m eth1 offset 0x14 length 32
> >> Offset Values
> >> ------ ------
> >> 0x0014 4a 44 53 55 20 20 20 20 20 20 20 20 20 20 20 20
> >> 0x0024 00 00 01 9c 50 4c 52 58 50 4c 53 43 53 34 33 32
> >>
> >> Please consider applying to ethtool.
> >
> > I agree there should be ASCII-hex and binary dump modes, but we should
> > also support decoding of recognised EEPROM types (as Stuart proposed
> > earlier).
>
> I have a patch to do this as well, but also parse the SFP+ EEPROM.
> I need to fix it up after some of the changes to the patches that added
> kernel support but can submit in the next day or so if this would be of
> use.
>
> Stu
Sounds good. I'll wait for your patch.
Powered by blists - more mailing lists