1. 14 7月, 2011 1 次提交
    • M
      tg3: Determine PCI function number in one place · 69f11c99
      Matt Carlson 提交于
      tg3 devices will need to know exactly what function number they are so
      that they can communicate their status to the other functions.  In a KVM
      environment, the function number of a device presented by the kernel
      might not be the true function number, so an alternative method to
      determine the function number is needed.
      
      This patch used to contain an implementation for the alternative method,
      but recently we discovered a hardware bug that renders it incorrect.
      While new method is not yet known, it is still useful to consolidate the
      code that determines the PCI function to one location and use the
      results throughout the code.
      Signed-off-by: NMatt Carlson <mcarlson@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      69f11c99
  2. 28 6月, 2011 1 次提交
    • J
      tg3: remove unnecessary read of PCI_CAP_ID_EXP · 708ebb3a
      Jon Mason 提交于
      The PCIE capability offset is saved during PCI bus walking.  Use the
      value from pci_dev instead of checking in the driver and saving it off
      the the driver specific structure.  It will remove an unnecessary search
      in the PCI configuration space if this value is referenced instead of
      reacquiring it.
      
      v2 of the patch re-adds the PCI_EXPRESS flag and adds comments
      describing why it is necessary.
      
      [ pdev->pcie_cap --> pci_pcie_cap(pdev) -DaveM ]
      Signed-off-by: NJon Mason <jdmason@kudzu.us>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      708ebb3a
  3. 15 6月, 2011 5 次提交
  4. 20 5月, 2011 3 次提交
  5. 29 4月, 2011 1 次提交
  6. 26 4月, 2011 1 次提交
  7. 22 4月, 2011 4 次提交
  8. 14 4月, 2011 3 次提交
  9. 08 4月, 2011 1 次提交
  10. 07 4月, 2011 7 次提交
  11. 31 3月, 2011 1 次提交
  12. 27 1月, 2011 1 次提交
  13. 26 1月, 2011 6 次提交
  14. 07 12月, 2010 2 次提交
  15. 25 11月, 2010 3 次提交