============================
R E L E A S E N O T E S
============================
Broadcom 440x 10/100 Integrated Controller Ethernet Driver
for
DOS NDIS2 driver
Copyright (c) 2002-2004 Broadcom Corporation
All rights reserved.
Revision History
================
Version 3.07 July 21, 2004
-------------------------------
Fixes:
========
1. Problem:
Driver operates very slowly at time after reboot and after
disconnect/re-connect cable.
Cause:
Driver did not clear or initialize Link State Change bit of the
Interrupt Status Variable causes it to service the Link State
Change interrupt (reads the PHY) on every interrupt thereafter.
Change:
Driver clears Link State Change bit of the Interrupt Status
Variable before update interrupt events.
Impact:
None.
Version 3.06 July 19, 2004
-------------------------------
Fixes:
========
1. Problem:
CQ #10591: DOS NDIS2 driver shows Link and Activity LED
reversed.
Cause:
Driver initialized LED Control variable with incorrect
value.
Change:
Driver initializes LED Control variable with correct value.
Impact:
None.
2. Problem:
CQ #9867: NDIS2 driver Poor performance when using with Symantec
Ghost 7.5.0.335.
Cause:
Driver's Timer Tick reads the PHY to detect and service Link
State Change at 1 second interval. This 4401-A1 work-around
delays the Driver's ISR to deliver received packets to the
protocol. Resulted in Receive FIFO Error where the NIC has to
be reset.
Change:
Driver detects and services Link State Change using interrupt
for 4401-B0.
Impact:
Driver's down load time using with Symantec Ghost 7.5.0.335 is
comparable to 570x NIC and third party NIC.
Version 3.05 February 09, 2004
-------------------------------
Fixes:
========
1. Problem:
CQ #9374: Drivers force setting of BUS MASTER control bit.
Cause:
Some BIOS would not set BUS MASTER control bit.
Change:
Driver set BUS MASTER control bit in the PCI Command
Register during initialization.
Impact:
None.
Version 3.04 November 04, 2003
-------------------------------
Fixes:
========
1. Problem:
CQ #8477: NDIS2 DOS driver has poor Tx upload performance
when operating with TCPIP Window size of more than 8700.
Cause:
Driver transmits packets out of TCP/IP sequence, which
causes the Protocol to delay and retransmit.
Change:
Driver waits for the previous transmission to be completed
then process the current transmit request.
Impact:
None.
Version 3.03 October 31, 2003
-------------------------------
Fixes:
========
1. Problem:
CQ #8792: PHY Power Down.
Cause:
When having booted and shut down with Windows driver
v4.23, the next non-Windows based driver loaded will not
be able to connect, since the Windows driver has put the
PHY into a low power mode state.
Change:
Driver writes 0 to 'emaccontrol' register during
initialization.
Impact:
None.
Version 3.02 October 03, 2003
-------------------------------
Fixes:
========
1. Problem:
CQ #8512: Rx-Symbol Error fix for NDIS2.
Cause:
Driver resets the NIC when received packets with RXF_RXER.
This could results in poor throughput when connect to a
FJ LH1108C 10/100 hub. See CQ #8499 and #8502 for references.
Change:
Driver no longer checks for packets with RXF_RXER.
Impact:
None.
Version 3.01 September 11, 2003
-------------------------------
Enhancements:
=============
1. Request:
Remove EEPROM CRC8 checking to accommodate PXE's code usage
of the EEPROM.
Change:
Remove EEPROM CRC8 checking logic.
Impact:
None.
Fixes:
========
1. Problem:
CQ #8365: Driver does not display LineSpeed status when cable
is not attached.
Cause:
Driver does not display LineSpeed status.
Change:
Driver displays LineSpeed status.
Impact:
None.
Version 3.00 August 20, 2003
----------------------------
Enhancements:
=============
1. Request:
Add support for 4401 B0 silicon.
Change:
Added support for 4401 B0 silicon. There is no feature
enhancement.
Impact:
None.
Fixes:
========
1. Problem:
NDIS2 DOS driver causes divide over flow if IRQ is disabled
in BIOS.
Cause:
Driver still loads when BIOS provided with an invalid IRQ.
Change:
Driver only loads when BIOS provided with IRQ value between
2 and 15.
Impact:
None.
2. Problem:
NDIS2 DOS driver accepts and loads with keyword
"LineSpeed = 1000" is used in protocol.ini file.
Cause:
Incorrect maximum range in initialize routine.
Change:
Driver checks for range 10 to 100 and displays "forced" when
keyword "LineSpeed" is used in protocol.ini file.
Impact:
None.
Notes:
========
1. No release for v2.46-v2.99.
Version 2.45 June 16, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #7760: 4401 NDIS2 Intermittently loses network connection
when using NETBEUI.
Cause:
Unknown.
Change:
Driver's ISR handles Receive Overflow condition separately from
Receive and Transmit interrupts.
Impact:
None.
Version 2.44 May 06, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #7695: system locks up after multiple cable
disconnect/reconnect with link speed forced on AUT and switch.
Cause:
Driver polls the link status every 1 second, when its detects no
link it will continue to check again for 20 more times in
55ms interval before determines the link is lost. During this
time the cable might be reconnected and reset the counter. So
the system appears to be lock up.
Change:
Driver maintains the 1 second interval through out.
Impact:
When the cable is reconnected, it would takes about 7 seconds to
re-establish the network connectivity.
2. Problem:
Using NETBEUI protocol with link speed forced, while running
ReadRite test disconnect/reconnect the cable will cause the test
to fail in a few hours.
Cause:
Driver issues chip reset when its detects Receive Overflow which
causes by DMA engine lock-up. Because link speed was forced so
driver setup the PHY accordingly during the reset. This causes
link lost momentarily and was detected by the link status poll.
When link is re-established, a PHY reset is issued and the PHY is
getting setup again.
Change:
Driver chip reset will not setup the PHY after its initialized.
Impact:
None.
Version 2.43 May 01, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #7663: Load driver with LineSpeed forced in protocol.ini
with the far-end is set to AutoNeg. After driver initialized,
LineSpeed shown as forced but Link LED fluctuates and is not
stable. Switch shows line speeds continuously alternating
between speeds.
Cause:
Driver do PHY reset but never waits for the link to be stable
before forcing the desired speed.
Change:
Driver waits for AutoNegComplete bit to set before forcing the
speed. Also, use the SuperIsolate bit to simulate line drop
that allows the far-end to adjust to the forced speed and duplex.
Impact:
None.
Version 2.42 April 28, 2003
----------------------------
Fixes:
========
1. Problem:
CQ #7346: Force to any speed, device always connects
at 100 Full.
Cause:
Write PHY routine using incorrect bit size as input.
Change:
Write PHY routine use TypeCast to correct size.
Impact:
None.
2. Problem:
CQ #7623: loss connectivity when cable was disconnect
then reconnect.
Cause:
Driver does not detect link change condition.
Change:
Driver detects link change condition and reset the PHY
when regain connection.
Impact:
None.
04/09/03 - v2.41-
Support Multicast addresses.
Fixed transmit low performance with TCP/IP.
03/19/03 - v2.40-
Merged to current NDIS2 Upper Module.
Utilized ODI v1.07's Lower Module.
Reduced memory footprint to 39KB.
No release for v1.01-v2.39.
05/17/02 - v1.00-
First Engineering 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.