Broadcom (tg3) NetXtreme driver v3.92n for Red Hat Enterprise Linux 4 - IBM BladeCenter and System x
Applicable countries and regions
- IBM BladeCenter HS12
- IBM BladeCenter HS20
- IBM BladeCenter LS20 (8850)
- IBM System x3105 (4347)
- IBM System x3200
- IBM System x3200 M2 (4367, 4368)
- IBM System x3250
- IBM System x3250 M2 (4190, 4191, 4194)
- IBM System x3350 (4192, 4193)
- IBM System x3400
- IBM System x3455
- IBM System x3500 (7977)
- IBM System x3800
- IBM System x3850
- IBM System x3850 M2
- IBM System x3950 (8872, 8878)
- IBM System x3950 E
- IBM System x3950 M2 (7141)
- IBM System x iDataPlexdx320 (6388)
- IBM eServer 325, 326, 326m
- IBM xSeries 205, 206m, 225, 226, 235, 236, 255, 260
- IBM xSeries 305, 335, 336, 346, 365, 366
- IBM xSeries 440, 445, 460, MXE 460
- IBM IntelliStation A Pro (6217, 6224)
- IBM IntelliStation E Pro (6216, 6226)
- IBM IntelliStation M Pro (6218, 6219, 9229, 9230)
- IBM IntelliStation Z Pro (6221, 6223, 6227, 9228)
File details
| Version: | 3.92n | |
| Release Date: | 2009-03-11 |
| File link | File size | File description | ||
|---|---|---|---|---|
| brcm_dd_nic_tg3-3.92n_rhel4_32-64.tgz | 3324079 | Broadcom (tg3) NetXtreme driver v3.92n for Red Hat Enterprise Linux 4 | ||
| brcm_dd_nic_tg3-3.92n_rhel4_32-64.txt | 21423 | README for the Broadcom (tg3) NetXtreme driver | ||
| brcm_dd_nic_tg3-3.92n_rhel4_32-64.chg | 119547 | CHANGE HISTORY for the Broadcom (tg3) NetXtreme driver | ||
| brcm_dd_nic_tg3-3.92n_rhel4_32-64.xml | 47542 | XML for the Broadcom (tg3) NetXtreme driver |
Severity: Suggested
Change history
Version 3.92n
(Change file contents are per Linux format.)
commit 236ae64063faf7d3398b4f9a889421b0d27a69d2
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 16 22:20:59 2008 -0700
bnx2: Update version to 3.92n
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 10343cca2bad3f9fdad214385bed0a9aadf4ffd4
Author: Benjamin Li <benli@broadcom.com>
Date: Fri May 16 22:20:27 2008 -0700
bnx2: Pre-initialize struct cpu_reg.
Instead of assigning values for the struct cpu_reg's at runtime, we already know these values at compile time. Therefore, we can use designated initializers, to initialize these structures and not have to incur this assignment cost at run-time.
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 601d3d18b2c1e4c197aa3cd902fb77bd99c41f10
Author: Benjamin Li <benli@broadcom.com>
Date: Fri May 16 22:19:35 2008 -0700
bnx2: Rename RX_COPY_THRESH to BNX2_RX_COPY_THRESH.
To make the bnx2 code more consistent, all instances of RX_COPY_THRESH have been changed to BNX2_RX_COPY_THRESH.
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit d89cb6af41559a601e9cfe081d34de07945b0d8b
Author: Benjamin Li <benli@broadcom.com>
Date: Fri May 16 22:18:57 2008 -0700
bnx2: Remove the rx_offset field from the bnx2 structure.
The rx_offset field is set to a constant value and initialized only once. By replacing all references to the rx_offset field, we can eliminate rx_offset from the bnx2 structure. This will save 4 bytes for every bnx2 instance.
[Added parentheses to the definition of BNX2_RX_OFFSET, as noted by Ben Hutchings.]
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 6ff2da49c8a68320c2564006c94a492db58de5cd
Author: Wendy Xiong <wendyx@us.ibm.com>
Date: Fri May 16 22:18:21 2008 -0700
bnx2: Add EEH PCI recovery.
Add PCI recovery functions to the driver. The initial pci state is also saved so the the MSI state can be restored during PCI recovery.
Signed-off-by: Wendy Xiong <wendyx@us.ibm.com>
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 9a120bc570627342c17befaa6af9b0a556dfda48
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 16 22:17:45 2008 -0700
bnx2: Allow phy reset to be skipped during chip reset.
Andy Gospodarek <andy@greyhouse.net> found that netconsole would panic when resetting bnx2 devices.
>From Andy:
"The issue is the bnx2_set_link in bnx2_init_nic will print a link-status message before we are fully initialized and ready to start polling. Polling is currently disabled in this state, but since the __LINK_STATE_RX_SCHED is overloaded to not only try and disable polling but also to make the system aware there is something waiting to be polled, we really have to fix this in drivers.
The problematic call is the one to netif_rx_complete as it tries to remove an entry from the poll_list when there isn't one."
While this netconsole problem should be fixed separately, we really should not reset the PHY when changing ring sizes, MTU, or other similar settings. The PHY reset causes several seconds of unnecessary link disruptions.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Acked-by: Andy Gospodarek <andy@greyhouse.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 705d209168681b4408d10fca7257de3343be573d
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 2 16:58:18 2008 -0700
bnx2: Update version to 1.7.5.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit d25be1d3ecf0b1b95ae29919786372b87b2bfea6
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 2 16:57:59 2008 -0700
bnx2: Update RV2P firmware for 5709.
The new RV2P firmware fixes 2 issues:
1. The jumbo rx buffer page size is now configurable and set to the proper PAGE_SIZE. Before, it was assumed to be always 4K.
2. Driver sometimes would crash when receiving jumbo packets mixed with firmware management packets. This was caused by the old firmware DMA'ing to the wrong address.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 352f76879ebde543817360ce9c18c973d4300f4f
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 2 16:57:26 2008 -0700
bnx2: Zero out context memory for 5709.
We should zero out the context memory for 5709 before each reset. When we resume after suspend for example, the memory may not be zero and the chip may not function correctly.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 15b169cccff1503a88f12f104e5657c65c53ade7
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 2 16:57:08 2008 -0700
bnx2: Fix register test on 5709.
The register BNX2_CTX_STATUS (0x1004) should be skipped on 5709 as it contains reserved bits.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 543a827d7a5600a71855bd6afacac78536c86822
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 2 16:56:44 2008 -0700
bnx2: Fix remote PHY initial link state.
On some remote PHY blade systems, the driver receives no initial link interrupt. As a result, the GMII/MII MAC mode does not get setup properly. To fix this problem, we add an initial poll of the link state after chip
reset.
With this change, the setting of the initial carrier state in the init code can be eliminated.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
commit 74ecc62d6e595ca64bbef2471787bf53b94e5d3c
Author: Michael Chan <mchan@broadcom.com>
Date: Fri May 2 16:56:16 2008 -0700
bnx2: Refine remote PHY locking.
bnx2_set_remote_link() should be called under bp->phy_lock to protect against concurrent polling and interrupt calls. This change is needed by the next patch which will add one initial poll of the remote PHY
link status.
Signed-off-by: Michael Chan <mchan@broadcom.com>
Signed-off-by: Benjamin Li <benli@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Please see the CHANGE HISTORY file for complete details.
Applicable countries and regions
Worldwide
Document id: MIGR-5069617
Last modified: 2009-04-02
Copyright © 2009 IBM Corporation
