| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 8 Nov 2012 01:39:52 +0100 From: Aurélien <footplus@...il.com> To: Ben Hutchings <bhutchings@...arflare.com> Cc: netdev@...r.kernel.org Subject: Re: Optics (SFP) monitoring on ixgbe and igbe On Wed, Nov 7, 2012 at 8:58 PM, Ben Hutchings <bhutchings@...arflare.com> wrote: > On Wed, 2012-11-07 at 13:27 +0100, Aurélien wrote: > > We just added the ETHTOOL_GMODULEINFO and ETHTOOL_GMODULEEEPROM > interface for this purpose. The diagnostics obviously aren't really an > EEPROM but I don't think that matters. > > These drivers should report a type of ETH_MODULE_SFF_8472 (assuming a > module is present) and expose an 'EEPROM' with the real EEPROM in the > first 256 bytes and the diagnostic registers in the next 256 bytes. > > Decoding of the diagnostic registers can be done in ethtool itself. > Hi Ben, Thanks for this reply. I did not see these interfaces in my searches, but from what I gather from the code, the missing part is the actual decoding of the data in ethtool. As soon as I get my card installed in a test server, I'll reboot on a kernel issued from the davem/net-next master, and will do some tests to see if ethtool correctly sees an SFF-8472 compliant module, and has the correct diagnostic data after the eeprom. Then I will port the decoding part from the kernel-side patches I to code in ethtool, and will do some basic tests. Thanks, Best regards, -- Aurélien Guillaume -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists