← Back to team overview

kernel-packages team mailing list archive

[Bug 1219619] Re: [patch] bug fix for igb driver to support Avoton


Further patches are in net-next tree and maybe not be merged into kernel
3.12, but it is useable for bug fix

66f40b8 igb: Update version number
41fcfbe igb: Implementation to report advertised/supported link on i354 devices
f6878e3 igb: Get speed and duplex for 1G non_copper devices
f1b4d62 igb: Support to get 2_5G link status for appropriate media type
db476e8 igb: No PHPM support in i354 devices
dfc7075 igb: M88E1543 PHY downshift implementation
99af472 igb: New PHY_ID for i354 device
aa9b8cc igb: Implementation of 1-sec delay for i210 devices
53ea6c7 igb: Don't look for a PBA in the iNVM when flashless

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [patch] bug fix for igb driver to support Avoton

Status in intel:
Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Saucy:
  In Progress

Bug description:
  Intel have pushed patches to the igb driver to support Avoton on net-next tree.  These patches have a number of fixes in them which should be picked up for 13.10.
  These patches are in net-next tree and aren't included in 3.11 kernel.
  Some OEMs are interesting in these patches. Please backport to 13.10

  ed12cc9 igb: Expose RSS indirection table for ethtool
  c342b39 igb: Add macro for size of RETA indirection table
  7dc98a6 igb: Fix get_fw_version function for all parts
  53b87ce igb: Add device support for flashless SKU of i210 device
  ef3a009 igb: Refactor NVM read functions to accommodate devices with no flash
  5a823d8 igb: Refactor of init_nvm_params
  2ccd994 igb: Update MTU so that it is always at least a standard frame size
  5026719 igb: don't allow SR-IOV without MSI-X
  7f90128 igb: Added rcu_lock to avoid race
  e5c3370 igb: Read register for latch_on without return value
  8a650aa igb: Reset the link when EEE setting changed

To manage notifications about this bug go to: