============================
R E L E A S E N O T E S
============================
Broadcom 440x 10/100 Integrated Controller Ethernet Driver
for
DOS ODI
Copyright (c) 2002-2004 Broadcom Corporation
All rights reserved.
Revision History
================
version 3.10 August 26, 2004
-------------------------------
1. Problem:
When The ODI Driver is unloaded other devices that
shared the same IRQ are disabled.
Cause:
When The ODI Driver is unloaded, it masks off its own
IRQ which could also be shared with other devices. This
effectively disables those devices.
Change:
Driver preserves and restores the interrupt mask value
when it loads and unloads.
Impact:
None.
version 3.09 August 25, 2004
-------------------------------
1. Problem:
CQ #10827.
Cause:
Driver restores the flags register without preserving it
when its unloads.
Change:
Driver preserves the flags register and restores it
accordingly.
Impact:
None.
version 3.08 August 19, 2004
-------------------------------
1. Problem:
CQ #10794: When DOS ODI driver is unloaded, it does not
restore the interrupt mask bit.
Cause:
Driver does not restore the interrupt mask bit when its
unloads.
Change:
Driver restores the interrupt mask bit when its unloads.
Impact:
None.
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 #10590: DOS ODI 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. This problem was report against the DOS NDIS2
driver, but the DOS ODI uses the same logic that causes the
slowness in the DOS NDIS2 driver.
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:
None.
Version 3.05 June 15, 2004
-------------------------------
Fixes:
========
1. Problem:
CQ #10330: Unable to unload driver with LSL /f.
Cause:
Driver hooked its Timer Tick through DOS.
Change:
Driver hooked its Timer Tick using LSL's Support
MLIDSUP_SCHEDULE_AES_EVENT.
Impact:
None.
2. Problem:
CQ #7650: DOS ODI 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.
Enhancements:
=============
1. Request:
None.
Change:
Device, LineSpeed, and Duplex informations displayed similar
to NDIS2 driver.
Displays "forced" when LineSpeed and Duplex were forced in NET.CFG.
Impact:
None.
Version 3.04 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.03 October 31, 2003
-------------------------------
Fixes:
========
1. Problem:
CQ #8793: 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 #8513: Rx-Symbol Error fix for DOS-ODI 16.
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.
Notes:
========
1. Changed banner from "Broadcom 440x Fast Ethernet MLID" to
"Broadcom 440x 10/100 Integrated Controller MLID".
Version 3.00 August 21, 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:
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:
(CQ #7482) Driver reports line speed of 10Mbps when connected
to Extreme switch and the switch reports the speed as 100Mb.
Cause:
Driver did not allows sufficient time for the Phy to come up
before determine there is no link then reports the default
line speed of 10Mbps.
Change:
Driver delays approximate 10s before determine there is no
link and reports LineSpeed Unknown.
Impact:
None.
Notes:
========
1. No release for v1.16-v2.99.
Version 1.15 May 14, 2003
----------------------------
Fixes:
========
1. Problem:
(CQ #7345) Driver reports line speed as 10Mbps when cable is
disconnected.
(CQ #7352) Driver does not report link duplex.
(CQ #7482) Driver reports link speed of 10Mbps when connected
to Extreme switch.
Cause:
Drivers displays default values.
Change:
Update Line Speed and Duplex informations dynamically.
Impact:
None.
Enhancements:
=============
1. Request:
(CQ #7466) Added Keywords to force LineSpeed and Duplex in
NET.CFG file
Change:
Recognized LINESPEED and DUPLEX keyword and force the speed
and duplex mode accordingly.
Impact:
None.
v1.14
- Changed ISR chaining logic to pass control to the chained ISR only
if the interrupt is not generated by the NIC.
v1.07
- Fixed a register corruption problem in the timer function.
v1.06
- Fixed the hang problem when the network has a lot of broadcast traffic.
v1.05
- Fixed a frame size problem with 802.3 frames.
v1.04
- Reduced size of the driver to about 29K - 33K.
- Fixed hang problem running odinsup.
- Improved transmit performance by doing direct DMA.
- Implemented Virtual DMA Services (VDS) if available.
v1.03
- Reduced size of the driver.
v1.02
- More bug fixes related to hangs and lost connections.
v1.01
- Some bug fixes related to hangs and lost connections.
v1.00
- 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.