1. 03 12月, 2012 1 次提交
  2. 28 11月, 2012 1 次提交
  3. 21 11月, 2012 1 次提交
  4. 08 11月, 2012 1 次提交
  5. 02 10月, 2012 1 次提交
  6. 02 9月, 2012 1 次提交
  7. 31 8月, 2012 1 次提交
  8. 13 8月, 2012 1 次提交
  9. 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
  10. 17 7月, 2012 1 次提交
  11. 11 7月, 2012 1 次提交
  12. 10 7月, 2012 1 次提交
  13. 27 6月, 2012 1 次提交
  14. 20 6月, 2012 9 次提交
  15. 14 6月, 2012 1 次提交
    • E
      bnx2x: fix checksum validation · d6cb3e41
      Eric Dumazet 提交于
      bnx2x driver incorrectly sets ip_summed to CHECKSUM_UNNECESSARY on
      encapsulated segments. TCP stack happily accepts frames with bad
      checksums, if they are inside a GRE or IPIP encapsulation.
      
      Our understanding is that if no IP or L4 csum validation was done by the
      hardware, we should leave ip_summed as is (CHECKSUM_NONE), since
      hardware doesn't provide CHECKSUM_COMPLETE support in its cqe.
      
      Then, if IP/L4 checksumming was done by the hardware, set
      CHECKSUM_UNNECESSARY if no error was flagged.
      
      Patch based on findings and analysis from Robert Evans
      Signed-off-by: NEric Dumazet <edumazet@google.com>
      Cc: Eilon Greenstein <eilong@broadcom.com>
      Cc: Yaniv Rosner <yanivr@broadcom.com>
      Cc: Merav Sicron <meravs@broadcom.com>
      Cc: Tom Herbert <therbert@google.com>
      Cc: Robert Evans <evansr@google.com>
      Cc: Willem de Bruijn <willemb@google.com>
      Acked-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d6cb3e41
  16. 24 4月, 2012 3 次提交
  17. 04 4月, 2012 5 次提交
  18. 28 3月, 2012 1 次提交
  19. 20 3月, 2012 3 次提交
  20. 21 2月, 2012 3 次提交
    • D
      0b0a635f
    • D
      bnx2x: add gro_check · fe603b4d
      Dmitry Kravkov 提交于
      The patch provides workaround for BUG in FW 7.2.16,
      which in GRO mode may miscalculate buffer and
      place on SGE one frag less than it could.
      It may happen only for some MTUs, we mark these MTUs
      with gro_check flag during device initialization or
      MTU change.
      
      Next FW should include fix for the issue and the
      patch could be reverted.
      Signed-off-by: NDmitry Kravkov <dmitry@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      fe603b4d
    • D
      use FW 7.2.16 · 621b4d66
      Dmitry Kravkov 提交于
      The patch integrates FW 7.2.16 HSI and implements driver
      part of GRO flow.
      
      FW 7.2.16 adds the ability to aggregate packets for GRO
      (and not just LRO) and also fixes some bugs.
      
      1. Added new aggregation mode: GRO. In this mode packets are aggregated
         such that the original packets can be reconstructed by the OS.
      2. 57712 HW bug workaround - initialized all CAM TM registers to 0x32.
      3. Adding the FCoE statistics structures to the BNX2X HSI.
      4. Wrong configuration of TX HW input buffer size may cause theoretical
         performance effect. Performed configuration fix.
      5. FCOE - Arrival of packets beyond task IO size can lead to crash.
         Fix firmware data-in flow.
      6. iSCSI - In rare cases of on-chip termination the graceful termination
         timer hangs, and the termination doesn't complete. Firmware fix to MSL
         timer tolerance.
      7. iSCSI - Chip hangs when target sends FIN out-of-order or with isles
         open at the initiator side. Firmware implementation corrected to drop
         FIN received out-of-order or with isles still open.
      8. iSCSI - Chip hangs when in case of retransmission not aligned to 4-bytes
         from the beginning of iSCSI PDU. Firmware implementation corrected
         to support arbitrary aligned retransmissions.
      9. iSCSI - Arrival of target-initiated NOP-IN during intense ISCSI traffic
         might lead to crash. Firmware fix to relevant flow.
      Signed-off-by: NDmitry Kravkov <dmitry@broadcom.com>
      Signed-off-by: NEilon Greenstein <eilong@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      621b4d66
  21. 20 2月, 2012 1 次提交
  22. 16 2月, 2012 1 次提交