1. 03 12月, 2012 8 次提交
  2. 28 11月, 2012 3 次提交
  3. 24 11月, 2012 1 次提交
  4. 14 11月, 2012 1 次提交
  5. 08 11月, 2012 1 次提交
  6. 03 11月, 2012 1 次提交
  7. 01 11月, 2012 1 次提交
  8. 03 10月, 2012 1 次提交
  9. 22 9月, 2012 1 次提交
  10. 14 9月, 2012 2 次提交
  11. 08 9月, 2012 1 次提交
  12. 31 8月, 2012 2 次提交
  13. 24 8月, 2012 1 次提交
  14. 10 8月, 2012 2 次提交
  15. 30 7月, 2012 1 次提交
  16. 23 7月, 2012 1 次提交
    • Y
      bnx2x: Add new 57840 device IDs · c3def943
      Yuval Mintz 提交于
      The 57840 boards come in two flavours: 2 x 20G and 4 x 10G.
      To better differentiate between the two flavours, a separate device ID
      was assigned to each.
      The silicon default value is still the currently supported 57840 device ID
      (0x168d), and since a user can damage the nvram (e.g., 'ethtool -E')
      the driver will still support this device ID to allow the user to amend the
      nvram back into a supported configuration.
      
      Notice this patch contains lines longer than 80 characters (strings).
      Signed-off-by: NYuval Mintz <yuvalmin@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c3def943
  17. 11 7月, 2012 1 次提交
  18. 27 6月, 2012 1 次提交
  19. 20 6月, 2012 8 次提交
  20. 08 6月, 2012 1 次提交
  21. 07 5月, 2012 1 次提交
    • A
      bnx2x: bug fix when loading after SAN boot · 24f06716
      Ariel Elior 提交于
      This is a bug fix for an "interface fails to load" issue.
      The issue occurs when bnx2x driver loads after UNDI driver was previously
      loaded over the chip. In such a scenario the UNDI driver is loaded and operates
      in the pre-boot kernel, within its own specific host memory address range.
      When the pre-boot stage is complete, the real kernel is loaded, in a new and
      distinct host memory address range. The transition from pre-boot stage to boot
      is asynchronous from UNDI point of view.
      
      A race condition occurs when UNDI driver triggers a DMAE transaction to valid
      host addresses in the pre-boot stage, when control is diverted to the real
      kernel. This results in access to illegal addresses by our HW as the addresses
      which were valid in the preboot stage are no longer considered valid.
      Specifically, the 'was_error' bit in the pci glue of our device is set. This
      causes all following pci transactions from chip to host to timeout (in
      accordance to the pci spec).
      Signed-off-by: NAriel Elior <ariele@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      24f06716