During boot, the igb driver shows the following message(s) for each NIC:
  igb 0000:05:00.0: Intel(R) Gigabit Ethernet Network Connection
  igb 0000:05:00.0: eth0: (PCIe:2.5Gb/s:unknown) 00:23:7d:45:80:6f
  igb 0000:05:00.0: eth0: PBA No: 1000ff-0ff
  igb 0000:05:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)

When the device is on a PCIe link trained as x2, the 'hw->bus.width' is
currently shown as "unknown".  This patch adds support for reporting the
correct link width configuration when the device is on a x2 PCIe link -
  igb 0000:05:00.0: eth0: (PCIe:2.5Gb/s:Width x2) 00:23:7d:45:80:6f

Signed-off-by: Myron Stowe <[email protected]>
---

 drivers/net/igb/igb_main.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/drivers/net/igb/igb_main.c b/drivers/net/igb/igb_main.c
index 9dd13ad..93bcdae 100644
--- a/drivers/net/igb/igb_main.c
+++ b/drivers/net/igb/igb_main.c
@@ -1305,7 +1305,8 @@ static int __devinit igb_probe(struct pci_dev *pdev,
                 ((hw->bus.speed == e1000_bus_speed_2500)
                  ? "2.5Gb/s" : "unknown"),
                 ((hw->bus.width == e1000_bus_width_pcie_x4)
-                 ? "Width x4" : (hw->bus.width == e1000_bus_width_pcie_x1)
+                 ? "Width x4" : (hw->bus.width == e1000_bus_width_pcie_x2)
+                 ? "Width x2" : (hw->bus.width == e1000_bus_width_pcie_x1)
                  ? "Width x1" : "unknown"),
                 netdev->dev_addr);



------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel

Reply via email to