============================
R E L E A S E N O T E S
============================
Broadcom NetLink (TM) Gigabit Ethernet Driver
For Windows Vista (Longhorn) 32/64 bit versions
Copyright (c) 2000-2008 Broadcom Corporation
All rights reserved.
Version 11.22.0.0C Nov 21, 2008
----------------------------------------
1. Problem:
CQ38651 - 5784M laptop show a yellow bang in Device Manger
after 300-400 iteration of S4 tests.
Change:
Apply CQ29902 workaround for this issue.
Impact:
Fixed a yellow bang issue.
Enhancements:
=============
1. Request:
CQ38029,CQ38185,CQ38351,CQ38491,CQ38505 - Add 4 part IDs for specific OEM
Change:
Added new IDs
Version 11.22.0.0B Sep 11, 2008
----------------------------------------
Enhancements:
=============
1. Request
CQ37293 - Ndis 5.x and 6.0 driver should have product version key set to 12.8.0 in 11.7
Change:
Change the product version as required.
Impact:
None
Version 11.22.0.0 Sep 03, 2008
----------------------------------------
1. Problem:
CQ37154 - OEM 5784M platform observes the same S5 WOL issue as CQ35234
Cause:
CQ35234 GPHY workaround was applied when system is going into S1/S3/S4, not for S5.
Change:
Apply CQ35234 GPHY workaround for S5 as well.
Impact:
None.
2. Problem:
CQ35948: Bad TX performance BX630S2 W2K8
Cause: The Tx code path runs out of credit on some of the processors, so aborts without
sending anything. This is occuring because a software timer
failed to schedule the DPC responsible for calculating this credit. The DPCs were not
scheduled for more than 4 procs on x86 systems, and 8 procs on x64 systems.
This driver version fixes this problem
Impact:
None
Enhancements:
=============
1. Request:
CQ36843 - Add registry key to common mini-port driver in order to allow NDIS to discard VLAN tagged packets
Changes:
Added "DropVlanPkt" registry key to drop vlan packets when vlan is disable.
Impact:
None.
Version 11.21.0.0B July 23, 2008
----------------------------------------
1. Problem:
CQ36161- Win 7_inbox driver - Per Msft requirement WOL features should not
advertised in the Advanced network properties
Cause:
The inf is incorrect
Change:
Fixed the inf
Impact:
None
Enhancements:
=============
1. Request:
CQ36056 - Add 4 part IDs for specific OEM
Change:
Added new IDs
2. Request:
CQ36166 - Add 4 part IDs for specific OEM
Change:
Added new IDs
3. Request:
CQ36432 - Add 4 part IDs for specific OEM
Change:
Added new IDs
4. Request:
CQ36447 - Add 4 part IDs for specific OEM
Change:
Added new IDs
Version 11.21.0.0 June 19, 2008
----------------------------------------
1. Problem:
CQ35947 - B5764/B5761/B5784-When setting WOL speed to 10mb system will be come unresponsive and lose link.
Cause:
The CQ35234 workaround is incorrectly executed when driver is loaded with WOL speed setting as 10mb.
There is no problem when WOL speed is set to Lowest, Auto or 100mb.
Change:
Correct driver's abnormal behavior and make driver to apply the CQ35234 workaround precisely.
Impact:
None.
2. Problem:
35434 - Win7 Inbox: Please Remove OEM Pnp (product_string) from the driver INF.
Cause:
Change:
Changed the inbox inf as requested.
Impact:
None.
3. Problem:
35447 - Windows 7 Inbox: Please Make INF Header consistent with NXII Driver INF.
Cause:
Change:
Changed the inbox inf as requested.
Impact:
None.
4. Problem:
35449 - Windows 7 Inbox: Incorrect "Provider" String under [Version) in Driver INF.
Cause:
Change:
Changed the inbox inf as requested.
Impact:
None.
5. Problem:
35450 - Windows 7 Inbox: The Default Setting for Flow Control Should be Disabled per MSFT
Requirements.
Cause:
Change:
Changed the inbox inf as requested.
Impact:
None.
6. Problem:
35464 - Windows 7 inbox: Power Management Feature (WOL) Not Disabled in the INF per MSFT Requirement
Requirements.
Cause:
Change:
Changed the inbox inf as requested.
Impact:
None.
Version 11.20.0.0 June 9, 2008
----------------------------------------
1. Problem:
CQ35239 - 5784m stops passing traffic when running copy compare at 10 Mb half duplex and ASPM L1 w/ clkreq.
Cause:
The clock glitch that occurring with L0->L1->L0 transitions causes device RDMA doesn't work normally.
Change:
Make driver to disable device's clkreq when linked at 10H or 100H as a workaround.
Impact:
Resolve CQ35239.
2. Problem:
CQ35234 - 5784M/5764M will not assert Wake signal one the first Wake magic packet received.
Cause:
When device is connected to particular switch with specific PHY at 1G bps, with wol speed
set to lowest speed, driver will program GPHY to advertise 10M bps support and restart
auto-negotiation while system is going from S0 to S3/S4/S5. In the meantime, 100tx or 1000t
idle sent from the link partner can confuse the local 10M bps polarity state machine, which
in turn can corrupt the first 10Mbps packet received.
Change:
Make driver workaround to reset link porlarity state machine and restart auto negotiation.
Impact:
Resolve CQ35234.
Enhancements:
=============
1. Request:
CQ31051 - FlowControl Parameter for Broadcom NX1 Not Consistent With Microsoft Standards
Cause:
There is a discrepancy between the MSFT and Broadcom naming convention as applied
to the *FlowControl keyword.
Change:
Changed the BRCM naming convention to match the one MSFT mandates.
Version 11.19.0.0 May 12, 2008
----------------------------------------
1. Problem:
CQ34962 - 5784/5764/5761 system compatibility issue on particular OEM system.
Cause:
When BIOS sets root-complex's and device's Max Payload Size (MPS) to 256 bytes,
device's MPS will be incorrectly set to 128 by driver, then device will report
ERROR_FATAL and stop DMA when it makes Memory Read and receives completion
packets larger than 128 bytes.
Change:
Make driver to keep device MPS setting during initialization.
Impact:
Resolve CQ34962.
2. Problem:
CQ34822 - Network traffic drops after SUT wakes up from S3/S4 while WOL is disabled.
Cause:
The reason why device doesn't pass traffic after system resuming from S3 (with
"Allow computer to turn off xxx" is unchecked) is because the upper layer doesn't use
the OID_OFFLOAD_ENCAPSULATION OID to set the task offload encapsulation settings
of an underlying miniport, and this makes our driver fails to send certain packets
which need driver/device to take care of checksum offload tasks.
Change:
Make driver to cache/restore the OID_OFFLOAD_ENCAPSULATION parameters across suspend/resume.
Impact:
Resolve CQ34822.
3. Problem:
CQ34959 - Modify NDIS 6.0 driver WoL behaviour when the "allow the computer to turn off
the device to save power" box is unchecked
Cause:
When driver's halt handler is called, driver enables device magic packet wol function according
to nvram wol setting.
Change:
Make driver to take advantage of a HaltAction flag in the halt handler, then driver can use this
flag to determine the reason why it's Halt handler is called and behave accordingly.
Impact:
Resolve CQ34959.
Enhancements:
=============
1. Request:
CQ34973 - OEM requests to enable log options for sysetms w/ 5784M
Change:
Make inf changes to enable log options for OEM systems.
Impact:
Resolve CQ34973.
Version 11.18.0.0 April 22, 2008
----------------------------------------
1. Problem:
Ensure private OID buffer is not touched until signature
is validated.
Cause:
Could cause DTM failure if buffer is modified
when signature is invalid.
Change:
Move setting status until after signature is validated.
Impact:
None
Enhancements:
=============
1. Request:
Enable constant 500Khz MDIO interface speed regardless core clock frequency.
Change:
Change driver to set the enable bit in MII Mode register.
Impact:
The change applies to devices 5764M/5784M/5723/5761/5761E.
Version 11.17.0.0 April 19, 2008
----------------------------------------
Enhancements:
=============
1. Request:
CQ34699 - Add 4 part IDs for specific OEM
Change:
Added new IDs
2. Problem:
CQ34762 - The system will casue blue screen when changed the
bootcode setting on b5761e-B0.
Cause:
BSOD if accessing Soledad's PCI FunctionEventMask register.
Change:
Not touch the register if it is Soledad
Impact:
None.
3. Problem:
1c_ndisrequestcov may crash on newly added OIDs for new devices.
Cause:
Buffer size is incorrectly determined.
Change:
Change the driver to correctly detect the buffer size for affected
OIDs.
Impact:
Fixed the BSOD on 1c_ndisrequestcov.
Version 11.16.0.0 March 31, 2008
----------------------------------------
1. Problem:
CQ34467 - OEM system BSOD when running Copy/Compare test on Vista SP1 with 512MB RAM
Cause:
When system is with 512MB memory only, driver allocates only 64K for LSO coalescing buffer.
There is a bug in handling coalescing pool wrapped around condition when 64K LSO coalescing
buffer is used. BSOD happens while driver is accessing memory over coalescing pool boundary.
Change:
Make code change to handle wrapped around condition correctly.
Impact:
Resolve CQ34467.
Version 11.15.0.0 March 16, 2008
----------------------------------------
Enhancements:
=============
1. Request:
CQ34254 - Add 4 part IDs for specific OEM
Change:
Added new IDs
Version 11.14.0.0 March 12, 2008
----------------------------------------
Enhancements:
=============
1. Request:
CQ33775 - VLAN ID maximum range should be 4094.
Change:
Limit VLAN ID maximum range to 4094
Impact:
Resolve CQ33775.
2. Request:
CQ34135 - Add 4 part IDs for specific OEM
Change:
Added new IDs
Version 11.13.0.0 February 28, 2008
----------------------------------------
Enhancements:
=============
1. Request:
Enhance the fix for CQ33858.
Change:
Change CPMU Clock Policy Registers to increase the Core Clock Speed before issue
a GRC reset and restore these registers after boot code has completed initialization.
Impact:
Resolve CQ33858.
Version 11.12.0.0 February 24, 2008
----------------------------------------
1. Problem:
CQ33858 - Device loses connection while doing load/unload test.
Cause:
When driver is unloaded, driver does a GRC Reset. When the link doesn't come back
immediately, CPMU will put MAC core clock into slower speed. This makes boot code
to be reloaed and executed slower. This also makes driver exceed waiting loop.
Finally, GPHY register corrupted because of driver and boot-code racing condition.
Change:
Extend driver waiting time to make sure boot-code 2nd phase is finished.
Enhancements:
=============
1. Request:
Remove CQ33808 driver workaround for 5784M/5764M/5723.
Change:
Remove driver workaround added in previous release.
Impact:
Bootcode v3.31 & slefboot patch v2.18 have the workaround to fix CQ33808.
2. Request:
CQ33892 - Add 4 part IDs for specific OEM
Change:
Added new IDs
3. Request:
CQ25155 - 5784M/5764M/5723/5761/5761E implementation of this CQ is
done in hardware instead of the software implementation.
Cause:
New chip requiring different actions.
Change:
Activate hardware fix for this CQ in driver and not with code in
the receive packet processing logic.
Impact:
New devices have hardware support for this fix that must be
activated in the driver.
Version 11.11.0.0 February 11, 2008
----------------------------------------
1. Problem:
CQ33808 - BCM5784M: System hangs when user changes Device Property with clkreq enabled.
Cause:
Issuing a GRC reset with clkreq enabled is causing a global chip reset and PCI-E
completion timer timeout.
Change:
When ClkReq and L0s/L1 ASPM are enabled, driver will clear ClkReq enable bit before doing
GRC reset and restore it after GRC reset.
Impact:
Resolve C33808.
Enhancements:
=============
1. Request:
Remove CQ33752 driver workaround.
Change:
Remove driver workaround added in v11.10.0.0
Version 11.10.0.0 February 7, 2008
----------------------------------------
1. Problem:
CQ33752 - Small fragments of less than 8 bytes cause transmit DMA failure.
Cause:
Under investigation.
Change:
Coalesce transmit buffers before submitting to the chip.
Impact:
Resolve issue for 5764M/5784M/5723/5761/5761E.
Version 11.9.0.0 January 29, 2008
----------------------------------------
1. Problem:
CQ33564 - BACS MAC loopback test fails when test is running without cable.
Cause:
Bootcode version after v3.23 has enabled GPHY DLL Auto Power Down by default.
When there is no cable, GPHY DLL Auto Power Down starts to work and makes test fail.
Change:
Change driver to disable GPHY DLL Auto-Power Down when running MAC loopback test
and then retore GPHY DLL Auto-Power Down Bit to original value.
Impact:
Resolve issue and this is for 5764M/5784M/5723 B0 only.
Enhancements:
=============
1. Request:
Add GPHY APD and GPHY DLL Auto-Power Down for 5764M/5784M/5723 B0.
Change:
Driver needs to read the share memory to determine how the GPHY Auto Power Down
feature is enabled/disabled by the user.
2. Request:
The GPHY workaround needs to be applied with the GPHY DLL Auto-Power Down Bit set.
Change:
Set GPHY DLL Auto-Power Down Bit before applying GPHY workaround and then restore
GPHY DLL Auto-Power Down Bit to original value.
Impact:
This is for 5764M/5784M/5723 B0 only.
Version 11.8.0.0 January 25, 2008
----------------------------------------
Enhancements:
=============
1. Request:
Enable IPV6 RX Checksum Offload for 5764M/5784M/5723
Change:
Make driver to advertise IPV6 RX Checksum Offload capability for 5764M/5784M/5723.
Version 11.7.0.0 January 24, 2008
----------------------------------------
1. Problem:
CQ33519 - 5784M fails at external loopback test fail.
Cause:
Device doesn't get linked and test application can't receive enough packets during the test.
Change:
Disable Link Speed/Link Aware/Airplane Power Mode and avoid setting PHY trim registers
while in external loopback test.
Impact:
Resolve CQ33519
Enhancements:
=============
1. Request:
Disable Link Speed/Link Aware/Airplane Power Mode while running MAC Loopback Test for 5784M B0.
Change:
Make driver to disable Link Speed/Link Aware/Airplane Power Mode while running MAC loopback Test.
2. Request:
Implement CQ31680/CQ32765 CLKREQ workaround for 5784M Ax revision.
Change:
Clear bit_16 of register 0x7d00 and clear bit_29 of register 0x68A4.
3. Request:
Enable IPV6 LSO support for 5764M/5784M/5723
Change:
Make driver to advertise IPV6 LSO capability for 5764M/5784M/5723.
4. Request:
GPHY earl-wake-dac mode must be enabled before MAC 10mb rx only mode is enabled.
Change:
Whenever driver issues a reset to the GPHY, GPHY early-dac-dac mode will be disabled.
Driver needs to disable CPMU 10mb rx only mode before resetting GPHY. Then later
driver can re-enable the 10mb rx only mode. It's for 5764M/5784M/5723 B0 only.
5. Request:
Implement new GPHY Workaround for 5784M/5764M/5723 B0.
Change:
Driver reads workaround parameters from OTP Memory and then configures GPHY accordingly.
Version 11.6.0.0 January 11, 2008
----------------------------------------
1. Problem:
NDIS6 driver fails 1c_ioctlcoverage test.
Cause:
NDISTest is unable to query the OID : OID_GEN_SUPPORTED_GUIDS.
Change:
Make driver to report successful status while doing the query.
Impact:
Passing 1c_ioctlcoverage test.
Version 11.5.0.0 January 11, 2008
----------------------------------------
1. Problem:
CQ33072 - NDIS6 driver fails infTest in WLK 1.1
Cause:
Inf strings under [ParamsNT8021p] section are non-localizable.
Change:
Replaced hardcoded text with localizable strings.
Impact:
Resolve CQ33072.
2. Problem:
CQ33122 - NDIS6 driver fails 2c_mini6rsssendrecv in Ndistest 6.0 of WLK 1.1
Cause:
There is a logical error in code and it makes driver can't disable RSS as ndistest
expected while doing RSS disabling test with zero "Hash Function Information" and
non-zero "Indirection Table Size".
Change:
Correct the logical error to make driver disable device RSS function successfully.
Impact:
Resolve CQ33122.
3. Problem:
CQ32886 - Ndis6: SUT locks up when running cable analysis test while passing chariot traffic
Cause:
System hung while driver was trying to acquire a spin lock in UM_CheckForHang(). Driver was
making two continuous main lock acquisitions. The first one came from UM_QueryInformation(),
when BACS passed T3_OID_DIAG_SUSPEND to driver during the test. The second one came from
UM_CheckForHang(), which was called by NDIS every two seconds.
Change:
Make driver doesn't acquire main lock in UM_CheckForHang while cable analysis is still running.
Impact:
Resolve CQ32886 issue.
4. Problem:
CQ30853 - Soledad fails 1c_kernelcalls test script
Cause:
DbgBreakPoint() is used in free build driver
Change:
Remove DbgBreakPoint() from free build driver
Impact:
Resolve CQ30853 issue.
5. Problem:
CQ30850 - Soledad fails 1c_wmicoverage test script
Cause:
The WMI method that ndistest is using does NOT return any class derived from Win32_PerfRawData class.
It only returns "normal" WMI classes. However, the WMI class we provided is derived from Win32_PerfRawData
class and it's used for graphing driver data to perfmon.exe along with some OS¡¦s provided perf data.
Change:
Create a registry key to control driver for enabling/disabling WMI perf counts.
Impact:
Resolve CQ30850 issue.
Enhancements:
=============
1. Request:
CQ33252 - Add 4 part IDs for specific OEM
Change:
Added new IDs
2. Request:
Change the Copyright information to include 2008 for all SW modules
Change:
Change the Copyright information to include 2008 in related files.
3. Request:
Implement driver workaround for 5784M GPHY related issues.
Change:
Add code changes for the workaround.
Version 11.4.0.0 December 10, 2007
----------------------------------------
1. Problem:
CQ32573 - Failed to resume normal speedlink after power saving mode.
Cause:
Device has a problem with logic that handles the automatic switching of the burst mode
to non-burst mode when the core clock is switching from 62.5MHz to slow clock modes.
Change:
Disable WDMA Rx Accel mode to workaround this issue.
Impact:
Resolve CQ32573 issue.
2. Problem:
CQ32692 - BSOD in Vista with driver while running common scenario stress
Cause:
Driver incorrectly cleans 5784M RX return ring producer index during system suspend/resume
from sleep. This makes driver get stuck when OS is trying put system into sleep again.
While OS is telling driver to put device into D3, driver can't complete IRP (IRP_MJ_POWER
/IRP_MN_SET_POWER) and this causes system BSOD with Bug check - DRIVER_POWER_STATE_FAILURE.
Change:
Make driver to behave correctly - not clean 5784M RX return ring producer index during
system suspend/resume from sleep.
Impact:
Resolve CQ32692.
Enhancements:
=============
1. Request:
Add support for 5784M A2 devices.
Change:
Make driver to keep all SW A0/A1 workarounds for A2
2. Request:
CQ32683,CQ32780 - Add 4 part IDs for specific OEM
Change:
Added new IDs
Version 11.3.0.0 November 08, 2007
----------------------------------------
Enhancements:
=============
1. Request:
Add support for 5784M A1 devices.
Change:
Make driver to keep all SW A0 workarounds for A1
2. Request:
Disable Link Speed Mode and Link Aware Mode while running MAC Loopback Test for 5784M A0 & A1.
Change:
Make driver to disable Link Speed and Link Aware mode while running MAC loopback Test.
3. Request:
For CQ31702 - SW needs to Configure LED Mode default to MAC Mode instead of GPHY Mode
Change:
Configure LED Mode default to MAC Mode for 5784M A0 & A1.
Version 11.2.0.0 October 24, 2007
----------------------------------------
1. Problem:
CQ31830 - System hangs when put it into S3 and S4 or disable the adapter with WOL disabled.
Cause:
When WOL is not needed, driver will power down GPHY for saving power. When GPHY powers down,
GPHY DLL stops provinding clock to mac core and this causes memory read completion timeout.
Change:
Make mac core clock switching before powering down GPHY.
Impact:
Resolve CQ31830 issue.
Enhancements:
=============
1. Request:
CQ31815 - Blue screen on boot if no network cable attached.
Change:
Remove codes that enables GPHY APD (Auto Powerdown) in driver. The GPHY APD is now handled by
the CPMU when Link Aware is enabled.
2. Request:
CQ31619 - 5784M A0 failed DMA Write Engine Lock Up when Link Speed Mode Enabled with
10Mb Traffic and Core clock is 1.5MHz
Change:
Slow down the core clock to 6.25Mhz in 10mb, Link Aware Mode or 10mb Link Speed Mode for 5784M A0.
Version 11.01.0.0 October 17, 2007
----------------------------------------
1. Enhancement request
Merged 5784M code from branch to mainline.
Version 11.00 October 9, 2007
----------------------------------------
1. Initial release for 5784M
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.