dd3a93cf5a
When HW starts, first read the NVM to see if the crosstalk fix should be used on the given HW and cache that information in the HW structure. When we check_link we first see if 1) NVM requests this fix 2) if we are an SFP+ device 3) see if a module is not in the SFP+ cage. If all the above are true then don't bother checking the link, just say it is down. Signed-off-by: Xiao Wang <xiao.w.wang@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com> |
||
---|---|---|
.. | ||
base | ||
ixgbe_82599_bypass.c | ||
ixgbe_bypass_api.h | ||
ixgbe_bypass_defines.h | ||
ixgbe_bypass.c | ||
ixgbe_bypass.h | ||
ixgbe_ethdev.c | ||
ixgbe_ethdev.h | ||
ixgbe_fdir.c | ||
ixgbe_logs.h | ||
ixgbe_pf.c | ||
ixgbe_regs.h | ||
ixgbe_rxtx_vec_common.h | ||
ixgbe_rxtx_vec_neon.c | ||
ixgbe_rxtx_vec_sse.c | ||
ixgbe_rxtx.c | ||
ixgbe_rxtx.h | ||
Makefile | ||
rte_pmd_ixgbe_version.map |