Netdev List
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Yaniv Rosner <yaniv.rosner@broadcom.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Stuart Hodgson <smhodgson@solarflare.com>
Subject: Re: ethtool enhancement proposal
Date: Wed, 18 Apr 2012 17:15:18 +0100	[thread overview]
Message-ID: <1334765718.2426.14.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <A6AA2EF896BED345B0F23520D832A4B10583EC@SJEXCHMB05.corp.ad.broadcom.com>

On Wed, 2012-04-18 at 13:05 +0000, Yaniv Rosner wrote:
> Hi Ben,
> I want to propose new enhancement for the ethtool to display the
> content of attached SFP+ module.
> The format should be similar to the "-e" option, and optionally parse
> it's content based on SFF-8472.
> Please let me know what you think.

Stuart Hodgson is working on something like this, though parsing is
unconditional.  I thought he had already posted a patch to netdev, but I
can't see it in the archive.

We discussed the different module formats and came to the conclusion
that:

- Most module types in current use have a 256-byte EEPROM, format
  defined in SFF-8079.
- SFF-8472 specifies two 256-byte EEPROMs/register files, the first
  identical to SFF-8079 and the second carrying diagnostic information.
- The ETHTOOL_GMODULE{EEPROM,INFO} commands should effectively
  concatenate the two.

The current Solarflare controller firmware only provides access to the
SFF-8079 EEPROM on SFP+ modules, so Stuart's code does not cover the
additional diagnostic information.  But that should be easy to add on
top.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

  reply	other threads:[~2012-04-18 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 13:05 ethtool enhancement proposal Yaniv Rosner
2012-04-18 16:15 ` Ben Hutchings [this message]
2012-04-18 17:20   ` Yaniv Rosner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1334765718.2426.14.camel@bwh-desktop.uk.solarflarecom.com \
    --to=bhutchings@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=smhodgson@solarflare.com \
    --cc=yaniv.rosner@broadcom.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox