On 12/17/2015 12:38 AM, Hannes Reinecke wrote:
On 12/17/2015 12:12 AM, James Smart wrote:
Why isn't this special cased anymore? Is it now supported by all HBAs?
Yes - if and when/where an async event is generated by the adapter is in
the fw. The special casing wasn't needed in the first place.
Hmm. How does this pan out on older cards?
Does every card sending out this event support the optic
misconfiguration detection? Or is there a chance that we lose the link
just because the event isn't properly implemented and we detect it as
non-operational?
Every card could - but whether it does is specific to the card and how
it was built and the restrictions made on that card type. The adapter
itself manages that. The event to the driver is solely for reporting.
The driver can't influence optics behavior.
-- james s
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html