Broadcom Corporation
16215 Alton Parkway,
Irvine, CA 92619-7013
Release Notes
Broadcom BCM570x EFI Driver for IA-32 and IA-64
05/12/2003
Revision History
================
Version 6.1.2 May 12, 2003
----------------------------
Fixes:
========
1. Problem: Driver doesn't pass traffic if the fiber interface is
connected to a port that has AUTONEG turned off. (CQ#7781)
Cause: Fallback mechanism doesn't work when autonegotiation fails
and interface doesn't receive configuration change from
the link partner.
Change: Fixed the PHY setup routine so that fallback mechanism
works correctly.
Impact: None.
Version 6.1.1 May 08, 2003
----------------------------
Fixes:
========
1. Problem: DHCP process intermittently doesn't completely successfully.
Cause: This issue is caused by the following reasons:
* Status block is not updated in a certain race condition.
* Link might be completely before base code starts sending
out DHCP request packets. This causes packets not being
sent to DHCP server.
Change: Changed the UNDI_Initialize API call so that it checks for
link up before returning back to the callers when Cable Check
is requested.
Changed so that UNDI doesn't dynamically turn on and off
host coalescing block.
Impact: None.
2. Problem: Multicast packets are not filtered correctly. If
RECEIVE_FILTER UNDI API is called with
PXE_RECEIVE_FILTER_DISABLE is called, the controller
is mistakenly programmed to operate in promiscuous
mode.
Cause : If RECEIVE_FILTER API is called with PXE_RECEIVE_DISABLE,
the driver will receive unwanted packets from the network.
This can cause lower performance and packet drops.
Change: Changed so that correct filtering is disabled when this
API is called.
Impact:
None.
Enhancements:
=============
1. Request: Provide proper indication of media presence after UNDI
INIITIALIZE calls. This allows base code to abort PXE
boot if no cable is attached.
Change: Changed the UNDI Initialize API so that it polls for
link status.
Impact:
None.
2. Request: "Revision Level of Code/Data" in PCI ROM header should
contain version of EFI UNDI driver.
Change: Enhanced EFIROM.EXE utility to initialize the mentioned
field with correct UNDI version number.
Impact:
None.
Version 6.1.0 May 04, 2003
----------------------------
Fixes:
========
1. Problem: In some extremely rare situations, 5702/03/04 Copper NICs
may not link up after a PHY reset.
Cause: On some 5702/03/04 PHY cores, there is a small probability of
lock up after a PHY reset.
Change: Added code to detect PHY lock up after a PHY reset and
reset again if lock up is detected.
Impact: The added lock up detection and recovery code affects
driver reset and link down events where PHY resets are
performed.
Enhancements:
=============
2. Request: Enhanced to allow users to start diagnostics without specifying
the child handle.
Change: Changed diagnostics upper layer interface to retrieve child handle
from internal data structure with given controller handler.
Impact:
None.
Enhancements:
=============
3. Request: Enhanced to take advantage DUAL ADDRESS that is supported in
EFI 1.10.14.61.
Change: Changed initializing code to enable DUAL_ADDRESS feature for
PCI/IO of devices.
Impact:
None.
v6.0.2 (03/05/03) - Fixed a problem where register test fails on BCM5705 when
no cable is connected. (CQ7153)
- Added an interface to export UNDI driver version to
external management software entity.
- Enhanced EFIROM application so that it extracts UNDI driver
version from EFI UNDI driver and to put UNDI version
information into EFI ROM header.
v6.0.1 (02/27/03) - Added MAC and PHY loopback feature in addition to
current memory and register test. Driver transmits
2000 packets with incremental length (from 64 bytes to
1518 bytes) and verifies it can receive all packets
back correctly. (CQ6692)
- Fixed a typo in product description string. (CQ 7085)
v6.0.0 (02/13/03) - Added support for newer version of BCM5705 family.
- Enhanced so that packet is always padded with 0's if
the packet length is less than minimum ethernet packet
size. The padding is now padded by hardware ASICs
instead of software.
v5.0.5 (12/17/02) - Added EBC (EFI Byte Code) support. See section
"Integration driver with Option ROM" for details.
- Fixed a problem where generic banner is displayed
for newer version of BCM5703-based NICs.
v5.0.4 (12/11/02) - Added support for new PCI devices (0x14e4/0x16c7,0x14e4/0x16c6,
0x14e4/0x1696).
v5.0.3 (11/26/02) - Enhanced so that version in drivers command now contains
UNDI driver version.
- Fixed a problem where link monitoring timer is not stopped
when driver is shut down.
v5.0.2 (10/03/02) - Second channel of BCM5704 fiber NIC is not detected
in core firmware v1.02. (CQ5627)
v5.0.1 (09/17/02) - Fixed a problem where FTP file download hangs when B5700B2
is used. (CQ5501)
- Added BCM5704 Fiber support.
v5.0.0 (09/12/02) - Fixed a problem where MTFTP download fails. (CQ5444)
v3.0.4 (08/28/02) - Added EFI Driver Diagnostics Protocol Support.
- Added NII driver version 3.1 support.
- Removed support for BCM5705 and BCM5901.
v3.0.3 (08/27/02) - Fixed a problem where link comes up at 100Mbps when WOL
is enabled on a certain NICs. (CQ5292)
- Fixed a problem where system hangs if the content of
NVRAM is blank or corrupted.
v3.0.2 (08/13/02) - Added support for BCM5705 and BCM5901.
- Fixed a problem where driver failes to negotiate link to
highest denominitor when it's set from 10/100 to Auto. (CQ5058)
v3.0.1 (07/23/02) - Added EFI Component Name Protocol support.
- Added EFI Configuration Protocol support.
- Enhanced to comply with EFI 1.1 v0.95.
v3.0.0 (06/19/02) - Fixed a problem where only one channel of BCM5704-based NIC
is detected. (CQ4377)
- Fixed a problem where PCI-X command register is overwritten.
v2.1.6 (06/07/02) - Fixed a problem where base-code fails to transmit packets if
there is a lot of broadcast background traffic.
v2.1.5 (04/22/02) - Fixed a problem where driver doesn't work in some PCI-X systems.
v2.1.4 (03/21/02) - Fixed a problem where BCM5700C2 NIC does not work at
if connection is changed from 100Mbps to 1Gbps. (CQ3711)
- Added support for different LED configurations.
v2.1.3 (03/20/02) - Fixed a problem where BCM5700C2 NIC does not work at
100Mbps. (CQ3605)
- Fixed a problem where no device path found for BCM5700B2.
(CQ3586)
v2.1.2 (02/24/02) - Added support for Ethernet WireSpeed feature for
BCM5702/BCM5703 NICs/LOMs.
- Added support for NICs with device ID 0x16a6 and 0x16a7.
- Added machanism to protect serial EEPROM corruption.
v2.1.1 (02/12/02) - Fixed a banner typo.
v2.1.0 (02/02/02) - Fixed a problem where driver doesn't work in EFI 1.10.54
core firmware environment.
v2.0.5 (11/19/01) - Added description of what slot (PCI or PCI-X) the NIC/LOM is
installed on when it's detected.
- Released EFI driver in library format for LOM application.
v2.0.4 (11/16/01) - Added support for EFI core firmware v1.1.
- Fixed a problem where performance of TCP/UDP traffic
is intermittently slow.
v2.0.3 (10/29/01) - Built specificially for core firmware V1.02.12.32 and
older. This version of driver doesn't raise/restore
priority level as done to work around an issue
in SNP module of core firmware v1.02.12.36 Or newer.
v2.0.2 (10/26/01) - Fixed a problem Bond ID is not checked correctly.
v2.0.1 (10/19/01) - Added support for BCM5702 and BCM5703 NICs/LOMs.
v2.0.0 (09/06/01) - Fixed a problem where application (pktsnoop) cannot
monitor packet with invalid 802.3 length fields.
- Fixed a problem where system intermittently crashes during
continous file transfer.
- Added Fiber NIC support.
v0.03 (08/31/01) - Added support for BCM5701.
- Fixed problem with loading driver on IA-32 (CQ#2009).
- Fixed problem when assigning IP address on IA-32 (CQ#2300).
- Fixed pktxmit.efi crashing problem (CQ#2302).
- Added a workaround to minimize the race condition on SNP
v0.02 (08/18/01) - Fixed problem with ping on IA-64 (CQ#1960).
v0.01 (05/14/01) - First Release.
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.