From: Or Gerlitz <ogerl...@mellanox.com> Date: Thu, 4 Jun 2015 19:30:35 +0300
> ISSI (Interface Step Sequence ID) defines the step sequence ID of the > interface between the driver to the firmware and is incremented by > steps of one. ISSI is used to enable deprecating/modifying features, > command interfaces and such, while maintaining compatibility. > > As the driver serves both ConnectIB (CIB) and ConnectX4, we carefully > made sure that the IB functionality keeps running also on older CIB > firmware releases that don't support ISSI. > > The Ethernet functionailty is available only on ConnectX4 where all > firmware releases support the feature since the very basic ISSI level. > So at this point no need for compatility code there. > > As done prior to this series, when the Ethernet functionlity is enabled, > during the initialization flow, the core driver performs a query of the > supported ISSIs using the QUERY_ISSI command, and then, if ISSI is supported, > sets the actual issi value informing the firmware on which ISSI level to run, > using SET_ISSI command. > > Previously, the IB driver wasn't ready to work on that mode, and hence > building both the IB driver and the Ethernet functionality in the core > driver were disallowed by Kconfigs, with this series, we allow users to > enable them both. Series applied, thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
