1. 14 10月, 2015 1 次提交
    • C
      i40e/i40evf: Add module_types and update_link_info · 0a862b43
      Catherine Sullivan 提交于
      Add a module_types variable to the link_info struct to save the module
      information from get_phy_capabilities. This information can be used to
      determine which speeds the module supports.
      
      Also add a new function update_link_info which updates the module_types
      parameter and then calls get_link_info. This function should be called
      in place of get_link_info so that the module_types variable stays
      up-to-date with the rest of the link information.
      
      The EAS table does not reflect the values that are actually returned,
      so instead, basing these values on the Ethernet compliance codes
      specified in table 33 of SFF-8436 as these have been accurate.
      
      Use the new variable in ethtool to differentiate between a 10G/1G dual
      speed fiber module and a 10G only module.
      
      Change-ID: Ib7585cce321319c10ce15180054c41a6cbd41389
      Signed-off-by: NCatherine Sullivan <catherine.sullivan@intel.com>
      Tested-by: NAndrew Bowers <andrewx.bowers@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      0a862b43
  2. 09 10月, 2015 4 次提交
  3. 08 10月, 2015 4 次提交
  4. 30 9月, 2015 2 次提交
  5. 27 8月, 2015 5 次提交
  6. 23 7月, 2015 2 次提交
  7. 18 7月, 2015 1 次提交
  8. 15 7月, 2015 1 次提交
  9. 28 5月, 2015 3 次提交
  10. 15 4月, 2015 2 次提交
  11. 27 3月, 2015 1 次提交
  12. 10 3月, 2015 1 次提交
  13. 09 3月, 2015 1 次提交
    • S
      i40e: tame the nvmupdate read and write complaints · 29a0645c
      Shannon Nelson 提交于
      The NVMUpdate tool doesn't necessarily know the ReadOnly map of the current
      NVM image, and must try reading and writing words that may be protected.
      This generates an error out of the Firmware request that the driver logs.
      Unfortunately, this ends up spitting out hundreds of bogus read and write
      error message that looks rather messy.
      
      This patch checks the error type and under normal conditions will not print
      the typical read and write errors during NVMUpdate.  This can be overridden
      by enabling the NVM update debugging.  This results in a much less messy log
      file, and likely many fewer customer support questions.
      
      Change-ID: Id4ff2e9048c523b0ff503aa5ab181b025ec948ea
      Signed-off-by: NShannon Nelson <shannon.nelson@intel.com>
      Signed-off-by: NJeff Kirsher <jeffrey.t.kirsher@intel.com>
      29a0645c
  14. 07 3月, 2015 1 次提交
  15. 05 3月, 2015 3 次提交
  16. 03 3月, 2015 2 次提交
  17. 25 2月, 2015 3 次提交
  18. 24 2月, 2015 2 次提交
  19. 14 1月, 2015 1 次提交