============================
R E L E A S E
============================
Broadcom NetXtreme Gigabit Ethernet Driver
For Windows
bit versions , Windows XP 32/64 bit versions,
Windows 2000, Windows NT 4.0, Windows ME, Win98/SE.
Copyright (c)
Broadcom Corporation
All rights reserved.
Version 7.100
January 17, 2005
----------------------------------------
CQ11139, CQ11143 - PCI Config Offset 0x30 (rom base address)
is writable.
The windows device driver enabled making rom base address register
writable when only PXE should enable this register to be writable.
Modified the device driver to not make the rom base address reguster
Resolve CQ11139 issue.
Unable to read past offset 264 of the flash on
A change to support new flash devices for 5750 was causing the
device driver to incorrectly read from the flash.
Corrected flash support for
Unable to read serial eeproms on 5700 and 5701.
A change to support gpio and asf for 5750 was causing the device
driver to not properly initialize the serial eeprom support.
Corrected serial eeprom support for 5700 and 5701.
Version 7.99
January 11, 2005
----------------------------------------
1. Problem:
CQ11158 - Low performance when LSO is enabled on 5788 when
running chariot.
As a result for fix CQ11463 the minimum number of LSO segments
was set to 3. However the majority of chariot transactions consisted
of only 2 segments.
Changed the minimum number of LSO segments back to 2. Modified
the driver to scan for corner case transactions that was causing
CQ11463 and bypass the LSO firmware for the affected transactions.
Resolve CQ11158 issue.
2. Problem:
CQ11819 - Driver returns 0 for statistics when calling OIDs using a 32 bit buffer
The driver attempt to adjust data for 32 application put the result in wrong location.
Modified the driver to adjust data for 32 application to put the result in proper location.
Resolve CQ11819 issue.
3. Problem:
CQ11780 - MAC address corruption issue after cold or warm boot
CQ11764 - Burned in address shows up as Multicast or wrong address on NICs with IPMI
Recovery time needed between Rx CPU halt and first NVRam read (5704).
Modified the driver to not release the Rx CPU NVRam request if the Rx CPU was halted while
its NVRam request is pending. The request is removed the next time NVRam access is needed.
Longer init time may occur for 5704 devices (up to .5 seconds).
Version 7.98
December 21, 2004
----------------------------------------
1. Problem:
CQ11723 - Internal file name in properties for b57amd64.sys of v7.97
had extra characters and displayed b57netamd64.sys
The compile file specifier had b57netamd64 as OS name.
Changed the compile file specifier to b57amd64 for OS name.
Resolve CQ11723 issue.
This was only a cosmetics issue and had
no effect on operation of the AMD64 driver.
Version 7.97
December 06, 2004
----------------------------------------
1. Problem:
CQ11487 - AMD64 inf is missing Checksum Offload, LargeSend, and Wirespeed options
Advanced Option List was incomplete for AMD64 installation.
Added Advanced Option missing entries for AMD64 installation.
Resolve CQ11487 issue.
2. Problem:
CQ11532 - Need to remove 5753F support.
Unsupported device at this time.
Removed 5753F support from all install INF files.
Resolve CQ11532 issue.
3. Problem:
CQ11521 - Configuring ASF in Windows XP32 using ASFConfig
Corrupts Firmware on 5721 B1 (Flash
ST M45PE10)
Driver device support for ST M45PE10 had incomplete command
sequence for Write of NVRAM Flash device.
Corrected Driver device support for ST M45PE10.
Resolve CQ11521 issue.
Version 7.96
December 01, 2004
----------------------------------------
1. Problem:
CQ11151 - NDIS driver does not properly support Dot3Stats OIDs
Driver was returning wrong data size of 8 bytes instead of 4 bytes.
Modified driver to return 4 bytes data for all Dot3Stats OIDs.
Resolve CQ11151 issue.
2. Problem
CQ11472 Unstable PLL output can lead to the chip lock-up when
transitioning to D3 Cold.
Extremely rare HW lock-up on 5751 devices when going into S3/S4
that causes the 5751 to intermittently not be visible to the system
after resuming from S3/S4.
The lock-up occurs due to an unstable PLL output ,due to internal
clock switching when PERST# is asserted when entering S3/S4.
Set hardware control register to values that prevent
Phase Lock Loop to power down & do Core clock switching.
Higher power consumption in S3/S4 on the 5751 family of devices
3. Problem:
CQ11466 Add generic 5753 support to OEM desktop windows .inf files.
New ID support request.
Added new ID support.
Resolve CQ11466.
4. Problem:
CQ11453, CQ 11454 - BACS not working correctly under NT 4.
A change in v7.92 of the driver to address CQ 9949 introduced a new
problem that occurred only under NT 4 (not on W2K, XP, or W2K3).
new problem was that certain IOCTL calls down to the driver issued
by BMAPI (on behalf of BACS) would fail, because the driver was no
longer advertising support for private OIDs due to the change for
NT4 appears to block IOCTL calls for OIDs that are not
explicitly advertised.
Modified driver advertise all private OIDs in NDIS 4 and NDIS 3.1
versions of the driver.
Resolve CQ11453 and 11454.
This will not break CQ 9949 because that
issue was specific to newer operating systems (later than NT 4).
5. Problem:
CQ BSOD during WHQL 2c_OffloadTaskMisc test on server
Corner case in LSO firmware when the minimum number of segments
is set to 2.
Changed the minimum number of LSO segments from 2 to 3.
Resolve CQ11463.
Version 7.95
November 29, 2004
----------------------------------------
1. Problem:
CQ11446 - Unable to pass network traffic after resume from S3 when
cable is disconnected during S3 and reconnected in S0.
Stale phy dll state information was causing the driver to initialize
the controller with the dll powered off.
Modified resume code to always power up the phy dll and keep the
phy dll powered on during the entire controller reset sequence.
Resolve CQ11446.
Version 7.94
November 24, 2004
----------------------------------------
1. Problem:
CQ11433 - System gets NMI error during shutdown.
Fix for CQ11308 was causing the dll to not be powered up during
Modified fix for CQ11308 to not control the dll properly during
Resolve CQ11433.
Version 7.93
November 24, 2004
----------------------------------------
1. Problem:
CQ11147 - Performance lower than expected in a few rare test scenarios
with 5751 family of devices. When this occurred, throughput would
periodically drop to zero for short periods of time which would lower
the average throughput. This problem was only seen when running
high throughput peer-to-peer performance tests with a single Linux
The issue would not be seen in tests involving multiple
remote stations, or tests involving Windows clients
Algorithm to coalesce send producer index updates on 5705 devices
was also used on 5751 devices.
This is unnecessary on with 5751.
Do not coalesce send producer index updates on 5751 family devices
Resolve CQ 11147.
There are no side-effects of this change.
2. Problem:
CQ11187 - b57win32.inf file is recognized by WinXP AMD64
The default entry in the b57win32.inf file intended for Win2k
was being used by WinXP AMD64.
Added a blank WinXP AMD64 section to the b57win32.inf
Resolve CQ 11187.
Version 7.92
November 22, 2004
----------------------------------------
1. Problem:
CQ11323 INF entry for one of OEM ID is incorrect.
New ID support request entry had an error.
Corrected new OEM ID support.
Resolve CQ11323.
2. Problem:
CQ11316 Change default value of LargeSendMinNumSeg to 2 for 5705 family.
Better performance improvement.
Changed default value of LargeSendMinNumSeg to 2 for 5705 family.
Resolve CQ11316.
3. Problem:
CQA1 12x12 with 256k flash (SA25F020) is not detected by AsfConfig.
CQ11268 BACS does not show firmware version
CQ11269 System hangs on firmware upgrade
New flash device was not yet supported by driver.
Added new flash device support.
Resolve CQ11224, CQ11268, CQ11269.
4. Problem:
CQ11308 Cable Length Diagnostics reports cable length of zero.
The change for CQ11226 was interfering with the diagnostics accesses of
paged phy registers.
Changed the fix for CQ11226 to use diagnostic state information in
order to not interfere with the cable length diagnostics.
Resolve CQ11308.
5. Problem:
CQ9949 Blue Screen when 1cPrivateDevIOctl optional WHQL test script is run.
The 1cPrivateDevIOctl test script was calling our private vendor specific
OIDs with invalid information causing the driver to perform invalid hardware
Removed private OIDs from the structure returned by OID_GEN_SUPPORTED_LIST.
Resolve CQ9949.
6. Problem:
IPMI does not work on 5704 when adapter is in low power state and link
speed is forced to 10mb.
An optimization to use the 6.25mhz clock when link speed is forced to
10mb and the adapter is in low power state is not valid when IPMI is enabled.
Changed the adapter shutdown code to use the 12.5mhz clock.
Power consumption will be higher when the adapter is shutdown and
IPMI is enabled.
Version 7.91
November 05, 2004
----------------------------------------
1. Problem:
CQ11183 Adding support for two new OEM Mobile platforms.
New ID support request.
Added new ID support.
Resolve CQ11183.
2. Problem:
CQ11165 Add 5788 device ID's to support new OEM mobile project.
New ID support request.
Added new ID support.
Resolve CQ11165.
3. Problem:
CQ11132 OEM would like to default ChkSum Offload to TX
ONLY on their 5701 products.
New OEM customization support request.
Modified requested installation options for OEM products.
Resolve CQ11132.
4. Problem:
OEM would like to new IDs for
5703 and 5704 and wants them to default
ChkSum Offload to TX ONLY.
New OEM device and customization support request.
Modified requested installation options for OEM products.
Resolve CQ11209 and CQ11210.
5. Problem:
CQ11216 Wake On Link Option is not available in the
Advanced Tab of Network Properties on some 5751M
OEM laptop models.
New feature request by OEM.
Enabled Wake On Link on 5751M OEM devices.
Resolve CQ11216.
6. Problem:
CQ11226 Intermittent blue screen during BACS MII test on 5751.
The gphy dll was not powered on during MII accesses from BACS.
Added gphy dll power up / power down code to MII access code
used by BACS.
Resolve CQ11226.
Enhancement Request:
====================
1. Request:
CQ11104 Gpio2 pin should always be configured as an input pin for Shasta
12x12 implementations.
Modified gpio control code to not change the state of gpio2 pin on
Shasta 12x12 implementations.
Version 7.90
October 19, 2004
----------------------------------------
1. Problem:
Remove the ability to set speed and duplex on the
OEM specific model embedded adapter.
This OEM LOM device is hardwired for 1 gig speed only and speed options
only cause problems for customers who tried to modify them.
Used 4 ID matched PCI IDs to give custom non modifiable speed option,
only for this OEM LOM device installations.
Resolve CQ11088.
2. Problem:
CQ1.inf file needs to include 64-bit Windows 2003
in the header for applicable OS
Need to add Windows 2003-64 bit support comment in the install inf file.
Added Windows 2003-64 bit support comment in the install inf file.
Resolve CQ10714 issue.
3. Problem:
Poor performance on 5751 BX parts.
Excessive register accesses to the gphy power down code over MII interface
was slowing down processing of interrupts.
Added additional state information in the gphy power down algorithm to
further minimize MII interface accesses.
Performance on 5751 BX parts should be comparable to driver revisions
prior to 7.87.
Enhancement Request:
====================
1. Request:
Certain gpio pins should not be modified by the device driver on
LOM implementations.
Added code to preserve the state of the gpio pins in LOM implementations.
Version 7.89
October 11, 2004
----------------------------------------
1. Problem:
Poor performance on 5751 BX parts.
Excessive register accesses to the gphy power down code over MII interface
was slowing down processing of interrupts.
Modified gphy power down algorithm to minimize MII interface accesses.
Performance on 5751 BX parts should be comparable to driver revisions
prior to 7.87.
Enhancements:
=============
1. Request:
Add PCI ID Support for new Broadcom Devices: M, 5753F, and 5781
Added new PCI ID support to the XP64, XP32, AMD64, and NDIS4
installation INF files.
Version 7.88
October 08, 2004
----------------------------------------
1. Problem:
CQ10965 Excessive power consumption on 5751 BX parts when cable is disconnected.
A typo in the source code was causing the gphy power down code to execute in
the system standby states but not in D0.
Corrected typo in source code.
Resolve CQ10965 issue.
Version 7.87
October 07, 2004
----------------------------------------
1. Problem:
CQ10758 TPM - 5751 A4 LOM in OEM system with ASF Enabled fails S1
Waker/Dozer Test.
This is due to the driver "resuming" from a sleep state and reading PHY registers
while the ASF FW could be simultaneously reading those registers.
The fix to this problem is to gracefully stop the internal CPU before making any
PHY accesses in the "resume" code (the OID_SET_POWER handler).
2. Problem:
CQ10863 GEN_OID_RCV_ERROR is not incrementing when an error packet is received.
Original driver implementation did not increment this count when Oversized,
Undersized,
and Jabber packets were received.
Added count of Oversized,
Undersized, and Jabber packets to GEN_OID_RCV_ERROR
inquiry code in the driver.
Resolve CQ10863 issue.
3. Problem:
CQ10862 OEM would like to add 4 Vendor Specific OIDs for Receive Error counters.
New OEM support request.
Added four new OEM custom OIDs for inquiry of Receive error statistics.
Resolve CQ10862 issue.
4. Problem:
CQ10991 Change the default minimum number of segments that can be offloaded
by the hardware value from 8 to 2 on 575x Devices.
Performance testing shows that Large Send Offload operations can be improved on
575x devices, by changing the value of this parameter from 8 to 2.
Modified driver to set recommended value to this parameter for 575x devices.
Resolve CQ10991 issue.
5. Problem:
CQ10985 System cannot wake with Magic Packet using LAA MAC Network Address
set with Advanced Options when ASF is also enabled.
The driver shutdown handler did not update the WOL MAC Network Address with
custom LAA values in the case of ASF enabled condition.
Modified driver to set custom LAA values accordingly when Windows is doing shutdown.
Resolve CQ10985 issue.
6. Problem:
CQ10965 Excessive power consumption on 5751 BX parts when cable is disconnected.
The driver was not powering down the GPHY DLL when it is not needed.
Modified driver to power down the GPHY DLL when it is not needed.
Resolve CQ10965 issue.
7. Problem:
CQ1 ASF heartbeat PET stopped when system in S4 state, or after
wake from same S4 state.
The driver to ASF handshake and control register sharing needed update for
proper ASF operation in Standby mode or after wake from Standby.
Updated the driver to do proper ASF handshake and control register sharing
for resume of ASF PET operation.
Resolve CQ10350 issue.
Version 7.86 August 23, 2004
---------------------------------
1. Problem:
CHKINF fails in HCT12 for XP-SP2 installation.
An install section was missing in the b57win32.inf v7.85 INF file.
Added the missing install section.
Correct CQ10816 issue.
Version 7.85 August 19, 2004
---------------------------------
1. Problem:
CQ10748 The "LargeSendOffload" registry key was being mistakenly added to
the Windows 2000 registry. This key should not be added to the W2K registry
because of serious problems with LSO feature in the original release of W2K
(before the release of the W2K service packs).
This issue is applicable to the unified install inf file b57win32.inf and only one
specific OEM with PCI SubSystem ID of 0x1028.
Prior released versions of b57win32.inf that had this installation issue for OEM
with SubSystem ID of 0x1028 were 7.76 to 7.84.
This key was originally present only in the Windows XP INF. However, when
the Windows 2000 and Windows XP INF files were merged into a single INF,
the INF was not modified so that this key would only be added on Windows XP
and not added for Windows 2000.
The unified Windows 2000 and Windows XP INF was modified to not add
LargeSendOffload key to the registry when the driver is installed on
Windows 2000.
No side effects.
2. Problem:
OEM System with 57xx PCI-E Device does NMI (blue screen) after
PXE boot from Venturcom BXP PXE server.
The root cause of the problem is that the Venturcom BXP PXE Server does not
shutdown the UNDI driver after PXE boot has completed.
This problem does not occur with PXE server products from other vendors.
The 7.84 driver detects during initialization that the LAN device has not been
shutdown properly by the PXE/UNDI software, and it attempts to gracefully
workaround this by resetting the device.
During this attempt to reset the 57xx PCI-E device, the PCI-E link flaps
(link down/up) which causes an "unexpected link change" on the chipset side.
Depending on the chipset configuration, this can lead to an NMI.
This problem only occurs on PCI-E devices, and does not occur on standard PCI devices.
Modified the device driver to gracefully reset 57xx PCI-E devices without causing the
PCI-E link to go down/up,
in the case that the PXE UNDI driver had not been halted
at the time of
Windows initialization of the device driver.
Version 7.84 August 05, 2004
---------------------------------
1. Problem:
A NMI was observed when a Windows "shutdown" occurred on a
5751M LOM based platform running 10mb, with WOL disabled, no ASF enabled.
problem could only occur if WOL was disabled, and the system was running at 10mb.
The original driver Shutdown sequence (with no WOL and no ASF) powered off the GPHY
prior to disabling device TX and RX blocks.
The GPHY was powered-down to save
power. Since the GPHY was disabled, the clock to certain MAC registers was intended
to be switched to a slower clock derived from the core clock.
However, a bug was
recently discovered in this logic which could lead to those registers having a very slow
clock (or no clock) in this situation.
This in turn, could lead to scenarios where read transactions
to those registers was not completed in a timely manner.
This could cause the chipset to
assert an NMI after 10ms if the read was not yet completed.
In the failing case, it was
observed that the read did complete, but it took up to 21ms to complete..
Modified driver to first disable the device RX and TX blocks and then power off the PHY
if no WOL and ASF were enabled.
No side effects.
Version 7.83 August 05, 2004
---------------------------------
1. Problem:
LAN driver yellow bang, or TPM failure, during focused LAN driver
halt/re-initialize testing.
The driver could write to a new NVRAM control register in 5751 HW without
holding the NVRAM lock.
This coud cause a problem if the TPM function and
the LAN driver both simultaneously tried to access NVRAM.
This problem is
highly timing dependent.
Under normal circumstances, the only time that the
driver acceses NVRAM is when loading the driver.
Re-ordered some code fragments to ensure that Nvram control register
in question is only accessed while the driver is holding the NVRAM lock.
This driver is compatible with TPM.
2. Problem:
Sychronize AMD 64 device support with XP 32.
The AMD 64 install inf file did not have OEM PCI ID match for supported device.
Added OEM PCI ID device support to AMD 64 inf install file.
Fix CQ10532 issue.
Version 7.82 July 28, 2004
---------------------------------
1. Problem:
B57dtect.dll
had wrong File Version 1.0.0.0 instead of 1.12.0.0
The DLL resource file for build had wrong string defined for File Version.
the DLL resource file string definition for File Version.
Fix CQ10529 issue.
2. Problem:
Synchronize b57amd64.inf with b57win32.inf installation files.
Original limited support of AMD 64 platform.
Increased Windows AMD 64 device support to the same level as Windows XP 32.
Fix CQ10532 issue.
3. Problem:
OEM LOM shows "Fiber" in adapter properties.
Original name requested by OEM; which has now requested to remove Fiber word.
Change network adapter device name to string supplied by OEM.
Fix CQ10543 issue.
4. Problem:
Broadcom Server CD v7.6.3\b57dtect.dll displays wrong copyright date.
The DLL released in this CD and v7.81 driver was the same binary as 7.80 which had old copyright dates.
Released new DLL with proper copyright date.
Fix CQ10576 issue.
5. Problem:
CQ10575 Broadcom Server CD v7.6.3\b57dtect.dll - wrong DLL file version.
The DLL released in this CD and v7.81 driver was the same binary as 7.80 which had old file version.
Released new DLL with proper DLL version.
Fix CQ10575 issue.
6. Problem:
Broadcom 7.81 AMD64 INF has .CAT file section commented out.
Original version of AMD 64 release.
Uncommented .CAT file reference.
Fix CQ10578 issue.
7. Problem:
Add OEM new projects P1 & P1_C PCI 4 ID match.
New OEM device support.
Added new support.
Fix CQ10597 issue.
8. Problem:
Broadcom 5788 Device Performance decreased with latest driver compared to previous driver.
Driver 5788 special dummy register reads at the start of ISR, these were only needed for 5788 A0 chip.
Removed 5788 A0 support, support can be restored by defining POSTED_READ_PATCH in sources.
Fix CQ10539 issue.
9. Problem:
OEM LOM Design Wake On Link Change
while WOL by IP Ping & MP works OK.
This problem does not occur on Broadcom evaluation NICs.
Driver did not set Wake On Link Change option to hardware on one of code paths.
Verified driver now sets Wake On Link Change option whenever the advanced property has selected it.
Fix CQ10671 issue.
10. Problem:
OEM request to change default Flow Control setting to disable.
New request.
Change OEM default advanced option setting.
Fix CQ10681 issue.
11. Problem:
CQ10691 Running Chariot with 1Byte buffer size causes the interface to hang.
This problem only occurs when an application attempts to transmit a packet
that contains a huge number (e.g. hundreds) of very small buffer fragments
and that it would be highly unusual for a real application to do this.
This problem was found when using an artificial test scenario that intentionally
forced this condition.
The fix for CQ9262 related to highly fragmented transmit packet buffers
was implemented in the multi-processors code path but was not implemented
in the single processor code path.
Implemented fix for CQ9262 in the single processor code path.
Fix CQ10691 issue.
Version 7.81 July 1, 2004
---------------------------------
1. Problem:
b57xp32.cat was referenced in the v7.80 b57win.inf file.
Unified inf had uncorrected reference to b57xp32.cat instead of b57win32.cat file.
Corrected digital signature file reference to b57win32.cat file.
Fix CQ10473 issue.
2. Problem:
CQ10474 Add new support for OEM product.
New support request.
Added new device support.
Fix CQ10474 issue.
3. Problem:
CQ10475 Add new support for OEM AMD-64 products.
New AMD-64 support request.
Added new OEM AMD-64 device support.
Fix CQ10475 issue.
4. Problem:
CQ10486 Incorrect comments in OEM
Missing Windows2000 Support indication.
Added Windows2000 Support indication.
Fix CQ10486 issue.
5. Problem:
b57xp64.inf needs current year in copyright date (2001 - 2004)
Original release date.
Modified copyright dates.
Fix CQ10489 issue.
6. Problem:
CQ10491 OEM Server unified INF does not have proper OEM copyright notice.
Original release version.
Modified copyright notice.
Fix CQ10491 issue.
7. Problem:
CQ10502 Windows reports stop error 0x0000007f when using .Net
Framework 1.1
The kernel double faulted in driver's send routine due to kernel stack
space being exhausted.
Modified send routine to use less stack space.
Driver uses 2k less stack space when processing packet sends vs.
previous versions of the driver.
Version 7.80 June 19, 2004
---------------------------------
1. Problem:
CQ-B0 NIC not functioning in under Chariot stress condition
Failure under stress that could occur on multi-proc systems, was introduced
with change made in v7.76 to the driver interrupt handler code.
The change in v7.76 resulted in a race condition where under rare circumstances
on a multi-proc system, interrupts could be left disabled when exiting the
interrupt handler
Fixed a race condition in the interrupt handler by changing the order of two operations.
Fix CQ10421 issue.
2. Problem:
Unified INF has incorrect BaseDriverFilerVersion number.
BaseDriverFileVersion parameter was not updated when release was made.
Updated BaseDriverFileVersion with correct number.
Fix CQ10427 issue.
Version 7.79 June 17, 2004
---------------------------------
1. Problem:
CQ based adapters consume more power when configured for
10mb WakeOnLan vs. 100mb WakeOnLan.
The clock control register was not programmed correctly when the
device is configured for 10mb WakeOnLan during system shutdown.
Corrected programming of the clock control register for 5750
based adapters for 10mb WakeOnLan during system shutdown.
Lower power consumption for 5750 devices configured for 10mb WakeOnLan.
2. Problem:
CQ10167 OEM Request for specific device name with PCI 4 ID match.
New OEM request.
Added new support for OEM request.
Resolve CQ10167.
3. Problem:
CQ10369 OEM Request to add support for four new devices with
PCI 4 ID match.
New OEM request.
Added new support for OEM request.
Resolve CQ10369.
4. Problem:
CQ10391 Ndis drivers does not pass WHQL WakeOnLan tests on 5702 adapters.
Fix for CQ10032 which only applies to 5750 based controllers was
being applied to non-5750 controllers.
Qualified fix for CQ10032 to apply to only 5750 based controllers.
Resolve CQ10391.
5. Problem:
CQ10231 Put support for Junction NIC back into Windows drivers.
The .inf need to be updated. This was not done for XP64 and AMD64.
Modified the XP64 and AMD64 .inf to support the new device.
6. Problem:
Add support for Capacitive Coupling
Implemented support for Capacitive Coupling.
Support for this is required in the boot code and diagnostics.
Version 7.78 June 10, 2004
---------------------------------
1. Problem:
CQ10317 Using switch -hreset to perform reset adapter continuously overnight,
system would lock up
There is an extra write to the T3_PCI_PM_STATUS_CTRL_REG in LM_SetPowerState().
This problem was introduced while resolving CQ10032 in driver 7.77
Removed the extra write.
2. Problem:
CQ10336 System freezes when changing advanced driver properties on Intel PDK
PCI-E Slots
There is an extra write to the T3_PCI_PM_STATUS_CTRL_REG in LM_SetPowerState().
This problem was introduced while resolving CQ10032 in driver 7.77
Removed the extra write.
3. Problem:
CQ based adapters consume more power when configured for
10mb WakeOnLan vs. 100mb WakeOnLan.
The clock control register was not programmed correctly when the
device is configured for 10mb WakeOnLan during system standby or
hibernate.
Corrected programming of the clock control register for 5750
based adapters for 10mb WakeOnLan.
Lower power consumption for 5750 devices configured for 10mb WakeOnLan.
Version 7.77 June 8, 2004
---------------------------------
1. Problem:
CQ9033 Flow control does not work consistantly.
When the phy is initially powered on, the default behavior
is to not advertise flow control.
Restart autoneg when flow control is configured to notify
the link partner that flow control is desired.
2. Problem:
CQ b2 and b3
fails to pass traffic.
The DPC routine is broken.
Restored the old DPC routine, with the OEM suggested fix to resolve
CQ10151 added.
3. Problem:
CQ10275 Large Send Offload and IPMI does not co-function on 5721.
LSO is turned off when ASF is enabled. This was necessary for the 5705
device which implemented LSO in f/w.
Since LSO is done in h/w, it is not necessary to disable LSO
when ASF is running on 575x and 572x devices.
4. Problem:
CQ10032 System wakes up immediately after entering standby.
Set bit 26 of Mac control mode register to prevent more PME events from
the device when the OS has already acknowledged the PME event.
Version 7.76 June 3, 2004
---------------------------------
1. Change Request:
CQ10231 Put support for Junction NIC back into Windows drivers.
Reinstated support for Junction NIC back into Windows drivers.
2. Change Request:
Merge the winXP and win2k inf.
Requested by MSFT for logo certification.
There is now a single .inf for winXP and win2k. This .inf is called
b57win32.inf. This distribution still includes the old .inf, so to
test, instruct windows to use the win32 inf during driver install.
3. Problem:
CQ10151 Server ASRs when running IXIA stress test. The machine appears locked up
under heavy network load.
The DPC routine can run for an extended period if the NIC interrupt rate
Cap the amount of time the DPC routine can run. The DPC routine was
aso rewritten to improve clarity.
4. Problem:
CQ10034 Runt packets transmitted on 5700BX are not padded with zeros.
Archaic workaround code for the 5700AX parts was incorrectly padding
transmit packets for 5700BX with garbage.
Removed workaround code since 5700AX parts were never released into
production.
Version 7.75 May 26, 2004
---------------------------------
1. Problem:
5700 B2 LOM with v1.3 Bootcode does not pass traffic
when v7.73 driver is used.
Bootcode did not implement shared memory
driver- so the driver would not recognize nor
initialize the PHY.
Added a fal so that in case of older bootcodes
the driver would initialize the PHY for proper operation.
Fix CQ10033 issue.
2. Problem:
CQ nic may draw VAUX during device initialization when
only one port has been enabled.
Incorrect programming of GPIO2 when only one port has been enabled.
Corrected programming of GPIO2.
5704 nic will not draw from VAUX during device initialization.
3. Problem:
CQ10097 OID_GEN_RCV_NO_BUFFER or OID_GEN_RCV_ERROR
statistics not incremented when packets are dropped.
OID_GEN_RCV_NO_BUFFER was getting the count from
lower module's no more receive buffer descriptors.
Modified OID_GEN_RCV_NO_BUFFER to get count from
lower module's receive overrun counter.
Fix CQ10097 issue.
4. Problem:
OEM requested to add 4 PCI ID match support for 5751F
New support for 5751F installations.
Added new support for 5751F installations.
Fix CQ10073 new support request.
5. Change Request:
OEM Request to add 4 ID support to IA64 driver.
New support for OEM installations.
Added new support for OEM IA64 installations.
Fix CQ10165 new support request.
6. Change Request:
OEM Request to add 4 ID support to XP32 and NDIS5 Drivers.
New support for OEM installations.
Added new support for XP32 and NDIS5 Drivers.
Fix CQ10167 new support request.
7. Change Request:
Add support for WakeOnLink for requested OEMs.
New support for OEM.
Added new support.
Implemented CQ9791 change request.
8. Change Request:
CQ10193 Disable embedded cpu for
A3 revision parts.
Hardware errata for
A3 revision parts.
Added cpu halt routine in device initialization for affected parts.
Embedded cpu for affected parts will be halted.
9. Problem:
System will not go to standby properly when a 5705 is
linked at 10mb.
When the 5705 is linked at 10mb, the core clock speed is slowed
to reduce power consumption. When the device driver programs
the 5705 for Wake On Lan, the 5705 is not programmed properly
due to the reduced clock speed.
Changed the Wake On Lan configuration code to ensure that the
core clock speed is set to normal before configuring the part
for Wake On Lan.
Fix CQ9960 issue.
10. Problem:
System running NT4 may report IERR when saving a speadsheet
from a Win95/Win98 Client.
The operating system was presenting zero length buffers to the
ndis driver for transmission.
Added scan for zero length buffers and coalesce transmit buffers
that contain zero length buffers.
Fix CQ10106 new support request.
11. Change Request:
Log message to event log when Ethernet@Wirespeed is
New request from OEM.
Added check for Ethernet@Wirespeed status to event logger routine.
Fix CQ8102 new support request.
Version 7.74 May 20, 2004
---------------------------------
1. Problem:
Fiber NIC 5701 has intermittent connectivity at startup.
Unsuccessful negotiation at startup with fiber switch.
Increased loop attempts to negotiate with fiber switch from two to
four times and also added initialize of negotiation state machine
prior to actual negotiation attempt.
Fix CQ9812 issue.
2. Change Request:
Re: CQ9955 Restore support for 5751M devices.
Removed commented inf support entries.
Restored support for 5751M devices.
Version 7.73 April 29, 2004
---------------------------------
1. Problem:
CQ9997 ASF 2.0 enabled will not allow system to wake from standby.
The driver to ASF handshaking does not work as expected when the device
power state is changed. Specifically, the "last driver state" is not set
to WoL when it should be. Also, in 7.72, it is possible for the firmware
to use the WoL pattern table before it is completely setup by the driver.
Fixed the handshaking.
Version 7.72 April 28, 2004
---------------------------------
1. Problem:
CQ LOM link is disconnected when changed speed.
The driver change to correct CQ9124 and CQ9033 Flow Control
problem did not consider forced speed settings and caused the
link to disconnect.
Backed out the change for CQ9124 and CQ9033
until full regression testing has been done. Issues CQ9124 and CQ9033
will be resolved on a later driver release.
Commented the change for fix of CQ9124 and CQ9033 issues.
Fix CQ9989 issue.
Version 7.71 April 23, 2004
---------------------------------
1. Problem:
CQ9955 Need to remove support for 5751M devices in Release 7.5 on ALL drivers.
The 5751M device has not yet been fully tested.
Commented inf support entries.
Fix CQ9955 issue.
2. Problem:
CQ9872 Not able to install 57xx driver for NIC on Win-Me
The Windows 2000 installation inf file used was bigger than 64K bytes.
This is a Windows 98, 98SE, Windows Me install inf file limitation.
Created a new Win98Me file folder that contains new b57w9x.inf and driver
files for use in Win98, Win98SE, WinMe Operating Systems.
Fix CQ9872 issue.
3. Problem:
CQ9931 Network Properties for OEM Desk Top models should be limited.
Original implementation.
Modified installation inf files to comply with new OEM request.
Fix CQ9931 issue.
4. Problem:
OEM Friendly name is no longer displayed on the Event Viewer Logs.
The requested friendly name string was too long and it caused Windows to use
it's own internal name for event logs of 57xx device.
Reduced the OEM friendly name by removing
Controller.
Fix CQ9936 issue.
5. Problem:
CQ9950 Release 7.70 NT4 driver did not support 5705M device.
New device support.
Added 5705M install support for 7.71 NT 4 release.
Fix CQ9950 issue.
6. Problem:
CQ9943 Connection to BMC does not resume after disabling adapter in OS.
New driver to ASF firmware handshake needed to be implemented.
Added new driver to ASF firmware handshake implementation.
Fix CQ9943 issue.
Version 7.70 April 19, 2004
---------------------------------
1. Problem:
CQ9124 Flow control is not working with 5750 A0 on NT4
Flow control negotiation fails
On initial driver load, the flow control capability was not advertised
to switch link partner.
Added a PHY control write to during d to advertise
flow control capability
Fix CQ9124 and CQ9033 issues.
Enhancements:
=============
1. Request:
CQ9835 Change behavior of CLKRUN# for 5705 so CLKRUN# is asserted when link
is present and deasserted when link is not present.
Modified link detection code to manipulate the CLKRUN# signal with respect
to the link status reported by the phy.
Fix CQ9835
2. Request:
CQ9306 Add ability to disable TCP/IP options task offload support.
Added new bit definitions to UserTaskOffloadCapDisable that can be used
to disable TCP/IP options offload support.
Fix CQ9306
3. Request:
CQ9886 OEM request to add new PCI 4 ID checking support for Win2k and XP.
Added new requested PCI 4 ID support.
Fix CQ9886
4. Request:
CQ and 5750 have higher than expected BER rates.
Programmed the phy on affected devices to adjust the bias current of the
ADC on the phy.
Fix BER issue.
Version 7.69 April 14, 2004
---------------------------------
1. Problem:
CQ9613 Set power mode failed in TestApp.exe (Broadcom's internal test
program needed to test Reverse Nway and Power Save Mode operations).
A spin lock acquired by the driver when configuring the hardware for
power saving mode may not be released, causing the OS to lock up. This
lock up only occurred when the driver was configured for power saving mode
and the EEPROM "Power Save Mode" option (secfg option 38) was disabled.
The driver was modified to release the spin lock for all code paths in
the T3_OID_SET_POWER_MODE OID handler.
This same problem was also detected in the T3_OID_PHY_ON OID handler,
and so the problem was fixed here also.
Fix CQ9613 issue.
2. Problem:
CQ LOM stops send out ASF alerts after
40 seconds while in a S3 State.
CQ Connection to BMC fails in Window sleep states and Shutdown.
The driver to ASF handshake needed update to resume ASF operation in Standby mode.
Updated the driver to do proper ASF handshake for resume of ASF operation.
Fix CQ9573 and 9788 issues.
3. Problem:
CQ9726 OEM Enhancement request to make a few options preset to defaults
and not able to change in XP.
Original installation implementation.
Updated XP installation inf file to handle OEM enhancement request.
Fix CQ9726 issue.
4. Problem:
CQ9543 Driver version 7.68 had full Network Properties for OEM
where it should be have been limited to 8021.p , Flow Control, Speed, WakeOnLan choices.
Original installation implementation.
Updated installation inf files to support OEM mobile customer request.
Fix CQ9543 issue.
5. Problem:
CQ9809 Incorrect friendly name for OEM 575x adapters on NT 4.0
Original installation implementation.
Updated installation NT 4.0 inf file to display requested OEM friendly name.
Fix CQ9809 issue.
6. Problem:
CQ9816 WHQL 2c_OffloadCheckSum test is failing.
Fix for CQ9711 is causing the NIC to drop a packet after adapter restart.
Modified change for CQ9711 so restart of autoneg will only occur if
Ethernet@Wirespeed is disabled but the current link was achieved using
Ethernet@Wirespeed.
Fix CQ9816 issue.
7. Problem:
CQ9342 High CPU load and sluggish system behavior with BASP and heavy traffic.
Looping inside the DPC handler for performance reasons was causing excessive
CPU utilization.
Reduced the number of loops in the DPC routine from 100 to 20.
Fix CQ9342 issue.
Version 7.68 April 02, 2004
---------------------------------
1. Problem:
ASF stops responding after disabling/enabling ASF in Windows for 575x.
The driver to ASF handshake needed update to resume ASF operation.
Updated the driver to do proper ASF handshake for resume of ASF operation.
Fix CQ9446 issue.
2. Problem:
CQ Fiber NIC intermittently loses connection with a Cisco6509 when
system is rebooted or device is disabled and then enabled.
The driver link timer needed increase to 802.3z specification and attempted one time
to autonegotiate.
Updated the driver link timer and increased driver autonegotiate attempt from one to
two times.
Fix CQ9706 issue.
3. Problem:
CQ9748 Error in INF install section for PCI-Express NIC
Incomplete inf install section for OEM.
Added missing inf install section.
Fix CQ9748 issue.
4. Problem:
Change string display for 5788 to "Broadcom NetLink (TM) Gigabit Ethernet"
Original inf information.
Change to new friendly name.
Fix CQ9294 issue.
5. Problem:
57xx: Create OEM branded AMD64 driver.
New feature.
Added requested branded AMD64 driver for OEM.
Fix CQ9698 issue.
6. Problem:
ASF 2.0 In Standby, Shutdown or Hibernate will stop sending PETS.
The Driver to ASF handshake needed to be updated with latest ASF implementation,
Updated Driver to ASF handshake.
Fix CQ9553 issue.
7. Problem:
Add three new PCI subsys id's for OEM using 5751 silicon.
New Support for OEM.
Added three new PCI IDs for support of 5751 device installation.
Fix CQ9759 issue.
8. Problem:
Unable to disable Ethernet@Wirespeed
Incorrect phy initialization sequence when Ethernet@Wirespeed is disabled.
Corrected phy initialization sequence.
9. Problem:
Single registry key for speed/duplex option for certain OEMs.
New Support for OEM.
Added support for new single key speed/duplex options.
10. Problem:
CQ9481, CQ: Share traffic/link LED not working correctly in XP
(XP driver not changing LED mode)
LED mode is not programmed properly
Programmed the LED as requested. The LED setup code now mimics the Linux
implementation.
Version 7.67 Mar 19, 2004
---------------------------------
1. Problem:
CQ9548 WinXP 5701A3 fails PCI Compliance test in HCT 12.0 Beta 2 Test Kit
The driver would always assume that OOB WOL was enabled and therefore would
always set the PME# bit in pci config space.
Changed driver to read OOB WOL configuration directly from eeprom.
Fix CQ9548 issue.
2. Problem:
CQ9579 Add two ID VID/DID PCI match for OEM.
Customer request.
Updated driver install inf file.
Fix CQ9579 issue.
3. Problem:
CQ9627 %OEM2_DEV1% name will be displayed when generic system ID is installed.
Name string not initialized in installation inf file.
Updated driver install inf file.
Fix CQ9627 issue.
4. Problem:
CQ9666 Release notes states we support Win95/OSR2
Original Release notes.
Updated this Release.txt file.
Fix CQ9666 issue.
Enhancements:
=============
1. Request:
Add registry key to optionally force CLKRUN# on mobile platforms.
Added registry key to support forcing CLKRUN# on mobile platforms.
Version 7.66 Mar 12, 2004
---------------------------------
1. Problem:
CQ9603 WinXP .inf missing line for OEM customer.
Incomplete driver installation inf file.
Corrected driver install inf file.
Fix CQ9603 issue.
Version 7.65 Mar 11, 2004
-----------------------------
1. Problem:
CQ9148 No link LED at Gig on 5751 LOM.
CQ: Share traffic/link LED not working correctly in XP.
CQ-A1: Driver overwrites LED settings from NVRAM.
The Windows driver was not keeping Firmware initialized LED settings.
Modified driver to honor the Firmware set LED controls.
Fix CQ9148, CQ9481, and CQ9549 issues.
2. Problem:
CQ9435 Jumbo frames was not functioning in drivers v7.57 to v7.60
The driver was not keeping Advanced Option Jumbo Frame size as user specified.
Modified driver to honor the user input for Jumbo Frames.
Fix CQ9435 issue.
3. Problem:
Using "->CfgWr0" cycles rather then "->MWr32" for setting "D3 Hot"
Driver performed Configuration Writes for all 57xx devices for this control operation.
Modified driver to use Memory Writes for 575x devices and Configuration Writes for all other devices.
Fix CQ9551 issue.
4. Problem:
CQ9603 WinXP .inf missing line for OEM customer.
Incomplete driver installation inf file.
Corrected driver install inf file.
Fix CQ9603 issue.
5. Problem:
CQ9129 Adapter stops transmitting packets on ia64 and amd64 systems with more
than 4gb of memory.
On 64-bit operating systems it is possible to get transmit buffers from
the upper layers that span a 4gb boundary. The 57xx family of adapters are
not able to dma buffers that span a 4gb boundary and therefore the read
dma engine will hang.
Added code to double buffer transmit buffers that span a 4gb boundary
for all 57xx adapters.
Fix CQ9129 issue.
Version 7.64 Mar 5, 2004
-----------------------------
1. Problem:
CQ9571 Version 7.63 binaries contains incorrect file version information.
The 7.63 binaries were built incorrectly.
Recompiled with correct file version information.
2. Problem:
The ASF firmware is not able to access nic memory when WOL is enabled on
575X adapters.
The driver did not properly configure the Mac Control Mode register when
WOL is enabled on a 575X.
Corrected WOL code to properly configure Mac Control Mode register on
3. Problem:
CQ9505 Add option in advance options to allow disable of warning and informational logs
for a specific OEM customer's 4 part PCI ID set.
Original driver implementation.
Add new inf entry for OEM 4 part PCI ID and also modify driver to look for and
handle new Warning/Information Advanced Options.
Fix CQ9505
Version 7.63 Mar 1, 2004
-----------------------------
1. Problem:
Performance is not optimized for TCP/IP traffic.
TCP/IP data throughput is decreased by 5% when receive frame TCP payload
is not aligned on a 64-byte cache line boundary. This occurs on both x86
and AMD platforms.
Changed the internal offset in receive buffers to align the TCP payload on
a 64-byte boundary. Except for 5701/PCI-X and 5700/PCI-X, the default internal
receive buffer offset for all NIC's is now 10-bytes. Assuming 54-bytes are used for
the MAC, IP and TCP headers, a 10-byte offset will put the TCP payload
on a 64-byte boundary. The internal receive buffer offset for 5701/PCI-X and 5700/PCI-X
NIC's will always be forced to 0 and cannot be overridden.
Improved receive performance with TCP/IP frames.
Version 7.62 Feb 25, 2004
-----------------------------
1. Problem:
Missing support for Shasta A1 various device PCI IDs.
Missing support for Shasta A1 various device PCI IDs.
Changed driver installation inf file to support added IDs.
Version 7.61 Feb 25, 2004
-----------------------------
1. Problem:
Missing support for Shasta A1.
Disabled all A0 specific workarounds on A1 chips.
Changed driver for 5751 A1 by disabling PCIE reset during GRC reset.
Changed driver for 5751 A1 by enabing PCIE data fifo bug fix in the chip.
Version 7.60 Feb 18, 2004
-----------------------------
1. Problem:
CQ9390, Remove HP mobile PCI entries from Broadcom standard .inf files.
Installation inf file needed update.
Update installation inf file.
2. Problem:
CQ9420, Friendly name displays "%BCM5750A1% instead of
"Broadcom NetXtreme Gigabit Eithernet"
Installation inf file needed update.
Update installation inf file.
Version 7.59 Feb 12, 2004
-----------------------------
1. Problem:
CQ9262, Database file transfer come to a stop, ARP show 0's MAC address.
There was a corner case in the descriptor count check in SendPacketsMP().
This corner case in the NIC driver can occur only if the packet data received
from the upper layer is extremely fragmented. For example, one packet, which
triggered this corner case contained 563 bytes, but was fragmented across 511
4K pages, each containing one or two bytes. One of our OEM Java database
applications generated this type of packet. When the driver fails in this mode,
the NIC can still receive but will not transmit. The NIC will also increment the
NoSendBdLeft statistic counter for each packet transition attempt. Usually,
the NIC driver cannot be disabled and the Windows desktop freezes.
Version 7.58 Feb 11, 2004
-----------------------------
1. Problem:
Driver may not initialize properly when PXE is enabled.
If PXE is not shutdown properly, the hardware will be left
in a state that is not compatible with the driver's initialization
Added code the check to see if the hardware has been left in a
active state during the driver's load routine and reset the adapter
if needed.
2. Problem:
CQ/5704 may hang on systems with more than 4gb of ram.
There were several corner cases in the 4gb workaround code related to
extremely small or extremely large transmit buffers.
Removed corner cases.
3. Problem:
CQ9262, Database file transfer come to a stop, ARP show 0's MAC address.
There was a corner case in the descriptor count check in SendPacketsMP().
This corner case in the NIC driver can occur only if the packet data received
from the upper layer is extremely fragmented. For example, one packet, which
triggered this corner case contained 563 bytes, but was fragmented across 511
4K pages, each containing one or two bytes. One of our OEM Java database
applications generated this type of packet. When the driver fails in this mode,
the NIC can still receive but will not transmit. The NIC will also increment the
NoSendBdLeft statistic counter for each packet transition attempt. Usually,
the NIC driver cannot be disabled and the Windows desktop freezes.
Enhancements:
=============
1. Request:
Add LSO statistics for BMAPI
Added code to count the number of LSO transactions offloaded by the
2. Request:
CQ9270 Enable LSO for 5788
Enable LSO for 5788 devices.
2. Request:
CQ9199 Update OEM Product names.
Updated OEM Product names.
Version 7.57 Jan 22, 2004
-----------------------------
1. Problem:
CQ9161, ASF 2.0 Secure session cause HIGH cpu util seen in 10mb.
The driver sets bits 22 of the Pci Clock Control Register.
Do not set bit 22 of the Pci Clock Control Register for 575x
2. Problem:
CQ9184, No network connection in Windows Xp when ASF is enabled
The handshaking between the driver and the fw does not work.
Fixed the driver to f/w handshaking.
3. Problem:
CQ9168, When In OS present mode at 100mb the secure session fails.
The driver sets bits 22 of the Pci Clock Control Register.
Do not set bit 22 of the Pci Clock Control Register for 575x
4. Problem:
CIOBE parts with multiple split transactions enabled may cause the
system to hang.
CIOBE has an errata related to the multiple split transaction feature.
Disable multiple split transaction feature in CIOBE parts.
Version 7.56 December 30, 2003
-----------------------------
1. Problem:
Enforce a register read after each and every register write.
This is a workaround for a bug in the ASIC which causes
chip lockup @10MBS (all traffic stops).
Problem in the ASIC design.
Register writes are followed by register reads
Enhancements:
=============
1. Request:
Changed the interrupt processing slightly for the 5705 and 5750.
Attempt to reduce the number of forced status updates in the ISR.
This is only an optimization of the code.
Version 7.55 December 24, 2003
-----------------------------
1. Problem:
A3 Add support for new IDs (14e4
Added new IDs to the inf
2. Problem:
BCM5750 show as "fast ethernet" in device manager.
.inf text is incorrect.
Fixed the .inf
Enhancements:
=============
1. Request:
Report the PCI-E bus type to bmapi
Modified OID to report bus type to bmapi
2. Request:
Serialize all accesses to the 575X registers. This is a temporary
workaround for a problem in the Asic (CQ8912 and CQ8978).
Changed the code as requested.
There are significant changes in the register access code.
The driver size is increased from prior releases. The size with revert
to that of prior releases when the serialize all I/O patch is disabled.
Version 7.54 December 10, 2003
-----------------------------
1. Problem:
Bit 15 of register 0xc4 is not set properly (hardware bug workaround)
Set bit 15 of register 0xc4 using memory cycle (not config cycles)
Enhancements:
2. Request:
Change some of the driver code to remove magic numbers and use existing
macros to read and write registers.
Changed the code as requested.
Version 7.53 December 05, 2003
-----------------------------
Enhancements:
1. Request:
Add support for 5750 device and move driver version to 7.53
Added support for 5750 device.
5750 device supported.
2. Request:
Increase 5751 chip reset delay to 300 milliseconds.
Increased 5751 chip reset delay to 300 milliseconds.
5751 device chip reset has 300 milliseconds delay.
Version 7.36 December 02, 2003
-----------------------------
Enhancements:
1. Request:
Need registry key to configure frame length consistancy check.
Added registry key to configure frame length consistancy check.
Version 7.35 November 21, 2003
-----------------------------
1. Problem:
Incorrect BCM5705 send producer index register update. This problem
has been reported by one of our OEMs.
Contention issue in the NDIS driver on multiproc systems.
Protected the BCM5705 register update routine with a spin lock
Version 7.34 November 17, 2003
-----------------------------
1. Problem:
CQ8781 - No check for NULL from NdisQueryBufferSafe in Ndis 5.1 drivers
Bug in code that calls NdisQueryBufferSafe
Implemented a buffer prescan to insure that packet buffers are mapped before
attempting to process a packet. If any buffers are not mapped, fail the request
gracefully.
2. Problem:
CQ8781 - Use NdisQueryBufferSafe instead of NdisQueryBuffer in Windows 2000
Ndis 5.0 drivers in oem specific builds
Code was implemented to use NdisQueryBuffer
Implemented a buffer prescan to insure that packet buffers are mapped before
attempting to process a packet. If any buffers are not mapped, fail the request
gracefully.
Oem specific builds of the Ndis 5.0 driver will not load on Windows98.
3. Problem:
The nic will drop frames if the ethernet length field is inconsistent.
The nic was programmed to drop frames containing a inconsistent ethernet
length field.
Disabled ethernet length field checking in the hardware.
Version 7.33 October 16, 2003
-----------------------------
1. Problem:
A3 programmed with new ID (14e4 00) is not recognized by 7.32
OEM specific build.
Incorrect OEM specific NT4 inf.
Corrected the inf
2. Problem:
Multiple Mac Address (MMA) feature is only accepting two MMA addresses when it should
accept three.
Incorrect #define value in source file.
Corrected #define value
Version 7.32 October 15, 2003
-----------------------------
1. Problem:
A3 programmed with new ID (14e4 00) is not recognized by 7.31
Incorrect NT4 inf.
Fixed the inf
Enhancements:
=============
1. Request:
CQ7321, add registry key to control TCP/IP option checksum support.
Added keys to disable task offload (see word document attached to CQ for more
Version 7.31 October 13, 2003
-------------------------
1. Problem:
CQ 8497, 3 of 24 NIC reported a high Transmit Queue Length
in 72 hours stress test.
The OID handler is using an incorrect structure (big endian)
which causes the wrong dword to be incremented to reflect the
Switched to the correct stucture
2. Problem:
Fix CQ8545, OEM certification test fails with 7.15 driver but
passes with 6.67
Incorrect chip rev. identification in MM_GetConfig() prevented
TxCoalesce buffers from being allocated for some 5704s
Fixed MM_GetConfig()
3. Problem:
CQ7502, LargeSend Offload (LSO) capabilities differ in 5705
from the rest.
The driver was reporting inconsistant encapulation support for
LargeSend Offload.
Modified driver source to have same encapsulation support
for all devices.
Version 7.30 Sep 23, 2003
-------------------------
Enhancements:
=============
1. Request:
Do not set the PME_EN bit in PCI configuration space if OOB WOL
is not enabled in the nvram when the driver is unloaded.
Added check in the unload routine to not set the PME_EN bit
when the driver is unloaded.
2. Request:
Add support for 5705F
Added support in the inf files and driver code for 5705F.
Version 7.16 Sep 12, 2003
-------------------------
Enhancements:
=============
1. Request:
Add one key to control both phy auto-negotiation enable/disable and
desired link speed.
Defined new values for 'RequestedMediaType' that specifies both
auto-negotiation enable/disable and desired link speed.
2. Request:
Add support for multiple mac addresses on the same nic for the Ndis5.0
Changed compile flags to compile multiple mac address support in the
Ndis5.0 driver.
Version 7.15 Aug 29, 2003
-------------------------
1. Problem:
The network icon may intermittently disappear when changing driver
properties when PowerMon is loaded and QOS is enabled.
The driver was incorrectly restarting phy auto-negotiation excessively
causing the driver to take too long to report link up to the operating
Added code to only restart phy auto-negotiation when there is a change
in the state of ReverseNway.
Enhancements:
=============
1. Request:
Add "volatile" modifier to SendPass and DpcPass driver variables to
prevent the compiler from optimizing references in ia64 and amd64
environments.
Added "volatile" modifier to SendPass and DpcPass driver in ia64
and amd64.
Version 7.14 Aug 28, 2003
-------------------------
Enhancements:
=============
1. Request:
Add support for multiple mac addresses on the same nic.
Added registry keys and custom OIDs to allow third party software
to configure the nic with multiple mac addresses.
Version 7.13 Aug 25, 2003
-------------------------
1. Problem:
The crc error counter for 5700 and 5701 was not getting zeroed
out when T3_OID_RESET_STATS_COUNTERS is called.
The crc error counter for 5700 and 5701 was not getting zeroed out
when the OID call is made.
Added code to zero out the crc error counter for 5700 and 5701 when
T3_OID_RESET_STATS_COUNTERS is called.
2. Problem:
The retail WinXp32, WinXp64, AMD64 drivers were being compiled with
incorrect compiler flags.
The build environment was not configured correctly.
Corrected the retail build environment of the affected operating
systems to use the correct compiler flags.
Executables will be slightly smaller.
Version 7.12 Aug 20, 2003
-------------------------
1. Problem:
Driver Verifier complains about a possible deadlock problem.
The driver was holding a spinlock during Ndis calls in the send
Removed spinlocks during Ndis calls in the send path.
2. Problem:
System fault under heavy network load (verifier C4_31)
The driver may incorrectly use spin locks at ISR level
Remove all calls to acquire spin locks from the ISR.
3. Problem:
Improper use of spin lock in shutdown handler
The driver is using a spin lock in the shutdown handler
Remove calls to acquire spin locks from shutdown handler
Version 7.11 Aug 15, 2003
-------------------------
1. Problem:
The OID_GEN_RCV_OK statistic incorrectly included receive
overrun frames.
The driver needs to subtract the number of receive overrun
frames from the values reported by hardware.
The driver subtracts the number of receive overrun frames from
the value reported by hardware before reporting the statistic
to Windows.
Enhancements:
=============
1. Request:
Improve bit error performance of 5703A0 and 5704A0 when used
with long cable lengths.
Program the phy's ADC and Gamma registers to more optimum settings.
2. Request:
Improve serdes drive levels on 5704.
Programed the serdes config registers with the values recommended
by the hardware design team.
Version 6.82 Aug 5, 2003
-------------------------
1. Problem:
Incorrect operation after PHY loopback test. Reported against
Linux configuration.
PHY register 0x18 is not programmed properly after running the external
loopback test.
Changed the value written to PHY register 0x18 from 0x480 to
the correct value 0x400 (after external loopback test).
2. Problem:
Flow control does not function (CQ8181).
LM_SetupCopperPhy() does not always program the flow control
when the link comes up.
Program the flow control in all code paths when the link comes up.
3. Problem
Idle cycle fix in 5704 B0 has side effects on certain HP/CPQ
This hardware fix is not enabled in this version.
Version 6.80 July 29, 2003
-------------------------
Enhancements:
=============
1. Request:
Add support for external loopback with loopback plug.
Added new requested media type values for external loopback.
2. Request:
Enable hardware fixes in 5704_Bx parts for known erratas.
Added code to driver init routines to enable hardware fixes in
5704 B0 silicon.
See 5704 errata for more details info about
the changes/fixes in B0 silicon.
1. Problem:
AMD Solo System intermittently blue screens when installing driver for 5704
The driver is executing pageable code at high IRQ level (UM_Initialize()).
Isolated the code executing at high IRQ level to a non pageable routine.
Version 6.69 July 9, 2003
-------------------------
1. Problem:
In Windows Win98SE: System cannot go into sleep mode when "wake up frame" is set
Win98SE expects WakeOnLan capability of
MagicPacket
WakeUpFrame
during its query of
OID_PNP_CAPABILITIES; even if device Advanced Properties is set to
WakeUpFrame only.
Added setting of MagicPacket support during handling of OID_PNP_CAPABILITIES.
This change does not affect actual WOL function as specified in the Advanced Properties
of the device, and only allows Win98SE systems to go to Standby mode.
2. Problem:
5700BX will stop processing packets under heavy loads.
A CoalesceNow workaround for stale status block information on the 5705 was
causing the 5700BX to hang.
Qualified the CoalesceNow workaround to be applied to only the 5705.
Version 6.68 June 19, 2003
-------------------------
1. Problem:
The adapter doesn't drop link when WOL is disabled and the driver
is disabled.
If WOL is enabled and the adapter is linked at 1gb when the driver
is put into low power state, the adapter does not re-acquire link
at 1gb when the driver resumes.
A typo in v6.65 of the driver was causing the driver to assume that
ASF is always enabled.
A change in v6.65 of the driver was causing the driver to not restart
link autonegociation on resume.
Corrected typo causing the driver to assume that ASF is always enabled.
Changed the restart autonegociation routine to take into account the
changes made in v6.65
These changes affect all adapters in all versions of Windows.
Version 6.67 June 13, 2003
-------------------------
Enhancements:
=============
1. Request:
Increment version number for revision control purposes.
Changed version number from 6.66 to 6.67
Version 6.66 June 02, 2003
-------------------------
1. Problem:
CQ7927: System locks up when driver is unloaded on
A workaround that is not applicable to the 5700 and 5701 related to
nvram accesses was being executed which caused an access to a invalid
Qualified the asf and nvram access workaround to be executed on only
non 5700 and 5701 parts.
This change only affects 5700 and 5701.
Version 6.65 May 31, 2003
-------------------------
1. Problem:
CQ: Cannot get link after disabling power saving mode
with ReverseNway. Cannot get link after changing from 100mb switch
to 10mb hub.
There was a corner case in the ReverseNway logic that was causing
the phy not advertise correct capabilities when ReverseNway is
disabled while the control suite has the driver suspended.
There was a corner case in the ReverseNway logic that was causing
the to not be reset properly when the phy lockup errata was executed.
Corrected corner cases so the phy advertises correct capabilities to
it's link partner.
These changes only affect those platforms that have ReverseNway enabled.
2. Problem:
CQBX fails to pass traffic while running 2c_Simultaneous
WHQL tests.
A change in the 6.60 driver to address an errata on the 5704 inadvertently
broke an existing fix for the 5700_BX small fragment errata. The bug was
causing the driver to run out of coalesce buffers when run on 5700_BX
Corrected code so the driver will properly handle small fragment coalesce
buffers on 5700_BX devices.
This change only affects 5700_BX devices. Other devices will not see any
change in behavior.
Version 6.64 May 20, 2003
-------------------------
1. Problem:
CQ785207: Device is Yellow Banged out after disable/enable of the
There was a race condition in the halt cpu routine in which the
halted cpu could still be holding the NVRAM arbitration bit.
This was preventing the driver from reading the configuration
information from the NVRAM and caused the driver to unload.
Added check in the halt cpu routine to see if the halted cpu is
holding the NVRAM arbitration bit.
Version 6.63 May 20, 2003
-------------------------
1. Enhancements:
1. Problem:
CQ7807: Loopback- - Mac test fails
The driver was not correctly configuring the 5705 for mac loopback
if the device was linked at 10mb.
Changed code to correctly configure the device when linked at 10mb.
2. Problem:
CQ7827: System will freeze on shutdown when linked at 10mb half.
The phy was getting powered down during reset.
Changed code to not power down the phy during reset.
Version 6.62 May 15, 2003
-------------------------
1. Problem:
CQ7656: Driver get yellow bang on 5788.
A check for the device/bond id was detecting the 5788 as an
unsupported device and therefore was causing the driver to unload.
Removed the check that was causing the driver to unload.
2. Problem:
CQ7798, CQ7799: ChkInf found errors in the inf files.
Typos in the inf files.
Corrected the inf files.
3. Problem:
The workaround for the phy lockup errata was not being applied to all
versions of the 5703 and 5704.
There was a check for previous revisions of 5703 and 5704 that was
incorrectly carried over from a previous errata.
Removed check for specific versions of the 5703 and 5704 for the phy
lockup errata.
1. Enhancements:
CQ7795, CQ Full Duplex option in adapter advanced properties
for all inf files.
This option is suppose to be present in only inf files for specific
OEMs. Removed 1000 Full Duplex option from files that are not applicable.
Version 6.61 May 14, 2003
-------------------------
1. Problem:
CQ7777: Some of the OID tests are failing in win98me
Added parameter checks in the OID processing are not
valid in all cases. These were added in rev 6.54
Removed the checks, they do not work for all cases as implemented.
2. Problem:
The driver did not restart autoneg on Fast Ethernet only parts when resuming
from hibernate or standby.
This was originally intended behavior. However the driver needs to
restart autoneg on resume due to phy lockup errata.
During resume check for Fast Ethernet only capable parts and
restart phy auto negotiation.
1. Enhancements:
The following OEM device ID's are not in the inf files.
PCI\VEN_14e4&DEV_16c7&SUBSYS_00ca0e11
PCI\VEN_14e4&DEV_16c7&SUBSYS_00cb0e11
Added OEM device ID's
Version 6.60 May 12, 2003
-------------------------
1. Problem:
Fixed problem with link getting dropped when shutting down Windows
when using a 5703/2 with old versions of bootcode when OOB WOL is
The bootcode was not properly passing configuration information to
the ndis driver.
Modified the ndis driver to read the configuration information directly
from NVRAM.
2. Problem:
System bluescreens with random bugcheck values on .Ne}