> The I2C bus that's connected to this module (interface).
> We can add another reason for MDIO BUS errors or merge to one BUS error
> reason.
> >> + ETHTOOL_LINK_UNSUPP_EEPROM, /* Unsupported EEPROM */
> > Which EEPROM?
>
> Module EEPROM.
Which module? This is all very vague. Some of the Marvell 10G PHYs
have an EEPROM to boot from, for example. Would that count? Or are you
talking about the SFP 'EEPROM', which is not actually an EEPROM, in
that it is not Electrically Erasable, not is it a ROM, since things
like temperature changes with time.
> >> + ETHTOOL_LINK_OVERTEMP, /* Over temperature */
> >> + ETHTOOL_LINK_PWR_BUDGET_EXC, /* Power budget exceeded */
> >> + ETHTOOL_LINK_MODULE_ADMIN_DOWN, /* Module admin down */
> > It seems like these last 6 are all SFP issues? How about putting SFP
> > into the name?
>
> Might be a QSFP issue for example, we can put module in the name though.
What is the generic name of SFP, SFP+ QSFP, SFF?
Andrew
