                              Release Notes
             Broadcom BCM5700 SCO OpenServer Release 5 driver

                          Broadcom Corporation
                          16215 Alton Parkway,
                          Irvine, CA 92619-7013

                Copyright (c) 2000-2006 Broadcom Corporation
                           All rights reserved


v10.0.3   (December 15, 2006)
==============================

    Fixes:
    -------------
        1) Problem : (CQ27832) 5755M fails IEEE tests.
           Cause   : PHY trim values suboptimal.
           Change  : Modify PHY trim values.
           Impact  : This problem only affects 5755M devices.


v10.0.2   (December 05, 2006)
==============================

    Fixes:
    -------------
        1) Problem : Certification tests fail to find the driver's
                     ISR.
           Cause   : During a code cleanup, the ISR name was changed.
                     The certification tests require the ISR name to
                     follow a particular convention.
           Change  : Changed the ISR name back to its old name.
           Impact  : None.


v10.0.1   (November 15, 2006)
==============================

    Enhancements:
    -------------
        1) Change  : Removed support for BCM5722.
           Impact  : None.


v10.0.0   (September 19, 2006)
==============================

    Enhancements:
    -------------
        1) Change  : Added support for BCM5722.
           Impact  : None.


v9.7.0   (August 24, 2006)
=============================

    Enhancements:
    -------------
        1) Problem : (CQ24704) Request removal of 1Gbps-HD from
                     documentation.
           Change  : Removed requested passages from documentation.
           Impact  : None.


v9.4.5   (July 11, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ25694) Invalid NVRAM type messages appear on
                     the console.
           Cause   : The NVRAM enumerations had changed since the
                     decoding logic was written.
           Change  : Code the NVRAM detection logic to use the new
                     NVRAM enumerations.
           Impact  : Most NVRAM types are unaffected.  The EEPROM
                     types will now be correctly detected as well as
                     any ATMEL AT45DB011 parts using the new
                     encoding.


v9.4.4   (June 27, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ25155 and CQ23480) Under rare circumstances,
                     5721 devices can encounter a read DMA overrun.
                     This would result in subsequent read DMA operations
                     not completing.  This in turn would lead to network
                     applications failing or "timing out".
           Cause   : This is due to a newly discovered corner case HW
                     bug in the 5721.  The same problem is also in 5751,
                     5753, 5789, 5752, and 5755 devices.  5787, 5705,
                     and devices introduced before the 5721 and 5751 are
                     not affected by this issue.  This HW issue can
                     occur under a rare circumstance where a very large
                     Rx BD read request is generated while the RDMA read
                     FIFO is partially filled with Tx data and the
                     TxMbuf memory is full.  Most network applications
                     would never generate this circumstance, and thus
                     this problem is hard to reproduce, and won't occur
                     with most network applications.  This problem could
                     theoretically occur at 1Gb speed but is more likely
                     to occur at 10mb or 100mb operation, and is more
                     likely to occur with applications that generate
                     lots of smaller (e.g. 82B) packets.  More
                     information about this issue will be included in
                     future 57xx chip errata documents for affected
                     devices.
           Change  : Modified the driver to limit how many BDs the HW
                     will try to fetch at any given time.  With this
                     workaround, the HW should never fetch more than 15
                     RX BDs in a read burst during runtime (not init
                     time).  This avoids the circumstance that could
                     expose the HW erratum.
           Impact  : The performance impact of this change is
                     negligible.

        2) Problem : (CQ9987) On a machine with heavy traffic, register
                     reads may return corrupted data.
           Cause   : The firmware and the driver register read timing
                     can collide causing the chip to return garbage
                     data.
           Change  : There exists a hardware fix, but the fix is
                     disabled by default.  The driver has been recoded
                     to explicitly turn on this fix.
           Impact  : None.


v9.4.3   (June 6, 2006)
=============================

    Fixes:
    -------------
        1) Problem : Devices with fastboot firmware will cause the
                     driver to issue an invalid NVRAM layout warning.
           Cause   : Fastboot firmware changes the layout of NVRAM.
           Change  : Recode NVRAM firmware version decoding to account
                     for new NVRAM layouts.
           Impact  : None.


v9.4.2   (June 5, 2006)
=============================

    Enhancements:
    -------------
        1) Change  : Added support for BCM5788, BCM5787, and BCM5786.
           Impact  : None.


v9.4.1   (May 12, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ24525) On rare occasions, 5755 device will fail
                     to acquire link at 1Gbps speeds.
           Cause   : The link partner is out of spec.
           Change  : Program the PHY to be more tolerant of
                     out-of-spec link partners.
           Impact  : None.


v9.4.0   (March 22, 2006)
=============================

    Enhancements:
    -------------
        1) Change  : Added support for BCM5755.
           Impact  : None.


v9.0.4   (February 28, 2006)
=============================

    Enhancements:
    -------------
        1) Change  : Remove support for BCM5755.
           Impact  : None.


v9.0.3   (January 19, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ22582) Link messages flood the console when
                     5714S and 5715S devices are configured
                     back-to-back.
           Cause   : Code which was meant to ensure link stability
                     was not being executed.
           Change  : Enable the link stability code.
           Impact  : None.


v9.0.2   (January 16, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ14603) Driver reports link down messages
                     when failover device is activated.
           Cause   : When the driver evaluates the PHY's configuration
                     settings, it reports a mismatch if there is one.
                     This state was improperly being stored in the
                     link status tracking field, instead of the more
                     generic "link down" state.
           Change  : If the link is not up, store a "link down" state
                     to the link status tracking field.
           Impact  : None.


v9.0.1   (January 12, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ22582) Link messages flood the console when
                     5714S and 5715S devices are configured
                     back-to-back.
           Cause   : The driver contains code which resets the PHY
                     when the device acquires link.  This code was
                     incorrectly being applied to 5714S and 5715S
                     devices.
           Change  : Only reset the PHY on 5703, 5704, and 5705
                     PHYs when link is acquired.
           Impact  : None.

        2) Problem : The driver intermittently fails to track and
                     notate the true link status of 5714S and 5715S
                     devices.
           Cause   : The use of the PHY_STATUS register to determine
                     the link status is unreliable.
           Change  : Use a MAC register to more competently determine
                     the link status.
           Impact  : None.


v9.0.0  (January 6, 2006)
============================

    Enhancements:
    -------------
        1) Change  : Added 5755 support.
           Impact  : None.


v8.3.6   (January 17, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ22582) Link messages flood the console when
                     5714S and 5715S devices are configured
                     back-to-back.
           Cause   : Code which was meant to ensure link stability
                     was not being executed.
           Change  : Enable the link stability code.
           Impact  : None.


v8.3.5   (January 12, 2006)
=============================

    Fixes:
    -------------
        1) Problem : (CQ22582) Link messages flood the console when
                     5714S and 5715S devices are configured
                     back-to-back.
           Cause   : The driver contains code which resets the PHY
                     when the device acquires link.  This code was
                     incorrectly being applied to 5714S and 5715S
                     devices.
           Change  : Only reset the PHY on 5703, 5704, and 5705
                     PHYs when link is acquired.
           Impact  : None.

        2) Problem : The driver intermittently fails to track and
                     notate the true link status of 5714S and 5715S
                     devices.
           Cause   : The use of the PHY_STATUS register to determine
                     the link status is unreliable.
           Change  : Use a MAC register to more competently determine
                     the link status.
           Impact  : None.


v8.3.4   (December 20, 2005)
=============================

    Fixes:
    -------------
        1) Problem : Driver does not load on 5715S devices.
           Cause   : There are preprocessor definitions in the code
                     which selectively include or exclude support
                     for 5714S and 5715S devices.  The preprocessor
                     condition was inverted such that these devices
                     were improperly being excluded from the build.
           Change  : Fix the preprocessor definition.
           Impact  : None.


v8.3.3   (December 15, 2005)
=============================

    Enhancements:
    -------------
        1) Change  : Added 5714S and 5715S support.
           Impact  : None.


v8.3.2   (October 19, 2005)
=============================

    Fixes:
    -------------
        1) Problem : (CQ14331) Incorrect branding on HP devices.
           Cause   : The subsystem vendor ID was incorrectly entered in
                     the configuration files.
           Change  : Fix the typo.
           Impact  : None.


v8.3.1   (October 17, 2005)
=============================

    Fixes:
    -------------
        1) Problem : (CQ13567) Link down messages are not displayed
                     immediately after adapter reset.
           Cause   : The reset code explicitly records the link
                     state as down without issuing a corresponding
                     message.
           Change  : Use another link state initializer in the reset
                     code.  The PHY code will then see the state
                     mismatch and issue the appropriate link state
                     message.
           Impact  : None.

        2) Problem : The PHY registers can become corrupted on all 5714S,
                     5715S, and 5780S devices.
           Cause   : The periodic link check code does not acquire the phy
                     lock before performing its task.
           Change  : Add phy lock acquisition and release code around
                     the link check function call.
           Impact  : 5714/5715/5780 fiber.

    Enhancements:
    -------------
        1) Change  : Removed 5903 support.
           Impact  : None.

        2) Problem : Health monitoring software does not register link
                     restoration events.
           Change  : Add code to the driver to send a message to the
                     health monitor software when link is restored.
           Impact  : None.

        3) Change  : Added ECD13216 fix for SERDES crosstalk problem.
           Impact  : None.

        4) Change  : Removed 5714S and 5715S support.
           Impact  : None.


v8.3.0   (August 23, 2005)
===========================

    Fixes:
    =============
        1) Problem : (CQ13033) ASF "Alive" heartbeat constant has changed.
           Cause   : Programmatic inconsistencies in previous
                     implementation forced the redefinition.
           Change  : Change driver to use the new constant.
           Impact  : None.

        2) Problem : (CQ13779) Poor performance on 5714 family devices.
           Cause   : DMA settings suboptimal in DmaReadWriteCtrl and
                     GrcLocalCtrl registers.
           Change  : Adjust DMA tuning bits in the DmaReadWriteCtrl
                     and GrcLocalCtrl registers.
           Impact  : None.


    Enhancements:
    -------------
        1) Change  : Add 5903F and 5903M support to the driver.
           Impact  : None.


v8.2.11  (August 10, 2005)
===========================

    Fixes:
    -------------
        1) Problem : Driver fails SCO certification tests.
           Cause   : Driver symbol does not conform to
                     mandated symbol standards.
           Change  : Rename symbol.
           Impact  : None.


v8.2.10  (August 02, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ10476) Tx statistic counters incorrect.
           Cause   : Tx statistic counters are overflowing in
                     hardware.
           Change  : Reduce the statistic refresh interval.
           Impact  : None.


v8.2.9  (August 01, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ11321) 5700 fails to initialize.
           Cause   : The 5700 DmaTest() function was incorrectly
                     failing due to DMA timeout.
           Change  : Change the code to return a success on DMA
                     transation timeout.  The data validation step
                     that follows will catch any DMA errors.
           Impact  : None.

        2) Problem : (CQ13576) 5704S fails flow control test.
           Cause   : The 5704 code was using the flow control
                     definitions of a different register.
           Change  : Use correct flow control definitions.
           Impact  : None.


v8.2.8  (July 22, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ13461) 5701 fails to receive traffic when
                     configured to 10Mbps, half-duplex, link forced.
           Cause   : The 5701 requires that the driver commit each
                     direct register write by performing a dummy
                     read to that same register.  The compiler was
                     optimizing the dummy read away, since the read
                     value was not being used.
           Change  : Force the compiler to keep the dummy read by
                     adding the "volatile" keyword to the destination
                     variable.
           Impact  : None.


v8.2.7  (July 20, 2005)
===========================

    Enhancements:
    -------------
        1) Change  : Remove 5714 and 5715 support from the driver.
           Impact  : None.


v8.2.6  (July 14, 2005)
===========================

    Fixes:
    -------------
        1) Problem : Serdes 325i devices not recognized correctly.
           Cause   : The driver's device list incorrectly linked
                     HP's serdes 325i subsystem device ID to
                     Broadcom's copper device ID.
           Change  : Point HP's serdes 325i subsystem device ID to
                     the correct Broadcom device ID.
           Impact  : None.


v8.2.5  (July 08, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ13319) Flow control fails to work in "auto"
                     mode.
           Cause   : The new flow control code requires that the
                     link's duplex configuration be known.  The
                     existing code failed to determine this.
           Change  : Determine the link's duplex setting before
                     setting up the flow control.
           Impact  : None.

        2) Problem : (CQ12986) 5714 devices do not fall back to
                     forced link if PCS_SYNCED is detected.
           Cause   : Incorrect detection of PCS_SYNCED and
                     RECEIVING_CFGS states.
           Change  : Modified code to get these states from the
                     PHY.
           Impact  : None.


v8.2.4  (June 20, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ13143) 5715 devices are not recognized on boot.
           Cause   : The code that recognizes supported devices was
                     changed and accidentally omitted 5715 devices.
           Change  : Include 5715 in the list of supported devices.
           Impact  : None.

        2) Problem : (CQ12922) Driver fails certification test.
           Cause   : When resetting the chip, the driver never
                     reclaimed the packet resources.  When the driver
                     attempts to fill the buffer rings afterwards,
                     there are no available resources.
           Change  : Fix the ResetAdapter() logic to reclaim packet
                     resources before resetting the chip.
           Impact  : None.

        3) Problem : (CQ12986) 5714 devices do not fall back to
                     forced link if PCS_SYNCED is detected.
           Cause   : Feature omission.
           Change  : Added force link fallback code.
           Impact  : None.


v8.2.3  (June 13, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ13057) Firmware version string missing
                     product name on 5714 devices.
           Cause   : The code that determines which version
                     string extraction method incorrectly
                     chooses the wrong method.
           Change  : Correct the method classification code to
                     include the 5714.
           Impact  : None.

        2) Problem : (CQ13022) 5703B1S never gets link.
           Cause   : The firmware autonegotiation code was bouncing
                     the link due to invalid flow control
                     configuration.
           Change  : Correct the flow control configuration code.
           Impact  : None.

        3) Problem : 5704S devices showing link up when link is
                     still being negotiated.
           Cause   : Code that forces link as a fallback does
                     not detect valid link up conditions strictly
                     enough.
           Change  : Only fallback to force link up if
                     autonegotiation is not in progress.
           Impact  : None.


v8.2.2  (May 6, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ12822) Flow control automation test fails.
           Cause   : The code, which classified what flow control
                     abilities the link partner was capable of, had
                     recently been rewritten.  In the case of
                     unidirectional flow control, the new code
                     accidentally classified the link partner's
                     flow control capabilities to the wrong direction.
           Change  : Correct the misclassification.
           Impact  : None.

    Enhancements:
    -------------
        1) Change  : Added support for new HP NC32Xi products.
           Impact  : None.


v8.2.1  (April 27, 2005)
===========================

    Enhancements:
    -------------
        1) Change  : Added 5715X support into driver.
           Impact  : None.


v8.2.0  (April 22, 2005)
===========================

    Enhancements:
    -------------
        1) Change  : Added 5714X / 5780X support into driver.
           Impact  : None.


v8.1.8  (April 5, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ12586) PCIE devices lock-up.
           Cause   : Hardware posts infinite data credits during PCIE
                     posted transactions.
           Change  : Find all locations where the chipset might
                     consolidate PCIE transactions and force them to
                     be separate.  Force setup code to read back all
                     register writes.
           Impact  : Minor performance impact on initialization.


v8.1.7  (March 31, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ12151) Link negotiation fails when 5751
                     LOM is connected back-to-back with another
                     device.
           Cause   : Driver was mistakenly forced to use the
                     MI interrupt mode.
           Change  : Correct the code so that it uses the
                     "link ready" mode.
           Impact  : None.

        2) Problem : (CQ12158) Driver incorrectly limits the
                     number of receive rules available for the
                     5714 family of devices.
           Cause   : The code which sets the limit on the
                     number of receive rules incorrectly
                     categorized 5714 family devices.
           Change  : Correct the categorization code.
           Impact  : None.

        3) Problem : (CQ12156) ATI transmit timeout -
                     "NETDEV WATCHDOG".
           Cause   : The ATI chipset did not call the driver ISR 
                     after the ISR did not service an INTx interrupt.
           Change  : The driver will check a register to determine if
                     the INTx should be claimed if the status block has
                     not been updated on ISR entry.
           Impact  : This fix may improve system performance on some
                     systems as it reduces the amount of spurious or
                     unclaimed interrupts.

    Enhancements:
    -------------
        1) Problem : Jumbo frame support on some systems caused device 
                     counters to increment CRC errors.
           Change  : Set TX elasticity bit in PHY when using jumbo
                     frames.
           Impact  : None. 

        2) Problem : 5714 device support needs to be removed for the
                     8.1b driver release.
           Change  : Removed 5714 family devices.
           Impact  : None. 

v8.1.6  (March 24, 2005)
===========================

    Enhancements:
    -------------
        1) Problem : Driver missing new HT-LE device IDs.
           Change  : Added missing device IDs.
           Impact  : None.


v8.1.5  (March 2, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ12303) Firmware version not displayed
                     for EEPROM devices.
           Cause   : Code failed to put EEPROM NVRAMs on newer
                     devices into the newer access mode.
           Change  : Ensure EEPROMS on newer devices are accessed
                     using the newer method.
           Impact  : Firmware version now displays correctly.


v8.1.4  (March 1, 2005)
===========================

    Fixes:
    -------------
        1) Problem : Driver crashes.
           Cause   : Not enough memory allocated for device
                     structures.
           Change  : Fix code to allocate the appropriate
                     amount of memory.
           Impact  : None.


v8.1.3  (March 1, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ12160) Capacitive coupling and preserve
                     preemphasis settings may be set incorrectly.
           Cause   : NVRAM configuration bits were not validated
                     before being used.
           Change  : Validate configuration bits before use.
           Impact  : Configuration bits set as expected.


v8.1.2  (February 7, 2005)
===========================

    Fixes:
    -------------
        1) Problem : (CQ11958) Driver shows a device identification
                     string of 5721(B0) instead of NC320T.
           Cause   : Configuration files had entries for BX devices
                     for the 5721 devices, but not for the NC320T
                     devices.
           Change  : Modify the configuration files to identify
                     NC320T BX devices.
           Impact  : Device identified correctly.

    Enhancements:
    -------------
        1) Change  : Added support for jumbo frames for 5714X and
                     HT2000 devices.
           Impact  : None.


v8.1.1  (January 11, 2005)
===========================

    Enhancements:
    -------------
        1) Change  : Added support for 5714X and HT2000 devices.
           Impact  : None.


v8.1.0  (January 07, 2005)
===========================

    Enhancements:
    -------------
        1) Change  : Added support for 5752 devices.
           Impact  : None.

        2) Change  : Updated copyright strings.
           Impact  : None.


v7.7.6  (December 14, 2004)
===========================

    Fixes:
    -------------
        1) Problem : (CQ11636) Device fails to get link when
                     connection is forced to 10Mbps.
           Cause   : Code which programs the LEDs programmed
                     the wrong shadow register.
           Change  : Changed code to program the correct
                     shadow register.
           Impact  : Device acquires link as expected.


v7.7.5  (December 2, 2004)
===========================

    Enhancements:
    -------------
        1) Problem : (CQ11011) PLL clock unstable.
           Change  : Set some hardware bits to stabilize the clock.
           Impact  : Device works as expected.


v7.7.4  (November 29, 2004)
===========================

    Fixes:
    -------------
        1) Problem : (CQ11448) 5704 LOM interfaces will not ping.
           Cause   : Peer device can hold NVRAM lock, which prevents
                     correct operation.
           Change  : Release NVRAM lock after reset.
           Impact  : Devices work as expected.


v7.7.3  (November 29, 2004)
===========================

    Enhancements:
    -------------
        1) Change  : Added support for more NVRAM types.
           Impact  : More NVRAM types supported.


v7.7.2  (November 9, 2004)
==========================

    Fixes:
    ------
        1) Problem : (CQ11088) Force the NC150T to autonegotiate
                     its linkspeed and duplex settings.
           Cause   : The 150T is a "LOM" connected to an onboard
                     switch.  Any other settings will cause a link
                     failure.
           Change  : Detect the NC150T and prevent changes to
                     requested link speed / duplex and autoneg
                     settings.
           Impact  : The NC150T will autoneg or fail to link.


v7.7.1  (November 8, 2004)
==========================

    Fixes:
    ------
        1) Problem : (CQ11270) Driver will not load on a BCM5700B2
           Cause   : BCM5700B2s do not have a valid EEPROM signature.
           Change  : Changed code to prevent an error return when
                     BCM5700 devices fail EEPROM signature check.
           Impact  : BCM5700 devices work once again.

        2) Problem : Firmware version number not displayed on 5750
                     family of devices.
           Cause   : NVRAM on 5750 family of devices requires the
                     "access enable" bit to be set before performing a
                     read.
           Change  : Set the access enable bit.  Also averted an offset
                     calculation on 5753 devices.
           Impact  : Firmware version shod up on both devices.

    Enhancements:
    -------------
        1) Problem : (CQ#11117) Preemphasis settings, set by the
                     firmware, need to be preserved.
           Change  : Added code to preserve preemphasis settings
                     enabled by the bootcode, when requested.
           Impact  : Better waveforms on particular serdes
                     implementations.



v7.7.0  (November 1, 2004)
==========================

    Fixes:
    ------
        1) Problem : (CQ10887) 5751B1 not recognized by driver.
           Cause   : New product was not yet supported.
           Change  : Added B1 support to configuration files for
                     all 5750 family devices.
           Impact  : 5750B1 family devices now supported.

    Enhancements:
    -------------
        1) Change  : Added support for 5753 series devices.
           Impact  : New devices supported.

        2) Change  : Backend (LM) code is now shared with UnixWare
                     and OpenServer.
           Impact  : Less maintenance overhead and speeds bugfix
                     and feature enhancement migration.

        3) Change  : Separated OpenServer and UnixWare frontends.
           Impact  : Enhanced platform flexibility at the expense
                     of a little maintenance overhead.

        4) Change  : Added firmware version to banner string.
           Impact  : It should be clearer which version of the
                     firmware is on the device.


v7.5.18  (June 18, 2004)
========================

    Fixes:
    ------
        1) Problem : NC1020 banner string inconsistant with others.
           Cause   : Documentation error.
           Change  : Fixed banner string.
           Impact  : Banner string displays correctly.


v7.5.17  (June 17, 2004)
========================

    Fixes:
    ------
        1) Problem : (CQ#10308)NC1020 showing as NC7722 in banner.
           Cause   : Incorrect string in config file.
           Change  : Fixed banner string in config file.
           Impact  : Banner string displays correctly.

    Enhancements:
    -------------
        1) Problem : Missing capacitive coupling support.
           Change  : Enable this feature if it is enabled in
                     NVRAM.
           Impact  : Capacitive coupled chips will work more
                     reliably.


v7.5.16  (June 7, 2004)
=======================

    Enhancements:
    -------------
        1) Problem : No support for 5751A3/B0, 5751F and 5789.
           Change  : Add support for 5751A3/B0, 5751F and 5789.
           Impact  : New supported products.


v7.5.15  (May 25, 2004)
=======================

    Fixes:
    ------
        1) Problem : TPM module cannot be tested.
           Cause   : Firmware contends with TPM for hardware
                     access.
           Change  : Shutdown the NIC CPU if 5750A3 family of
                     devices is detected.
           Impact  : TPM testing can continue.

    Enhancements:
    -------------
        1) Problem : 5751M not supported.
           Change  : Add support for 5751M.
           Impact  : 5751M chips will now be recognized
                     by this driver.


v7.5.14  (April 23, 2004)
=========================

    Fixes:
    ------
        1) Problem : (CQ9955) 5751M chips have not been tested.
           Cause   : No hardware available to test against.
           Change  : Remove 5751M support from driver.
           Impact  : 5751M chips will no longer be recognized
                     by this driver.


v7.5.13  (April 19, 2004)
=========================

    Fixes:
    ------
        1) Problem : Bit error rate too high in certain situations.
           Cause   : Corner cases causing bad hw interactions.
           Change  : Write several phy registers.
           Impact  : Corner cases correctly covered.


v7.5.12  (April 16, 2004)
=========================

    Fixes:
    ------
        1) Problem : The data LED of the NIC flashes too quickly when
                     the NIC is configured for Shared Traffic LED mode.
           Cause   : Hardware bug.
           Change  : Manually program the PHY for this mode.
           Impact  : Shared Traffic mode data LED works as expected.

        2) Problem : BCM5700 and BCM5701 NICs have high number of errors
                     with long cables.
           Cause   : These NICs cannot read the shadow registers, so they
                     must be blindly hard-coded. (no read-modify-write)
           Change  : Write hard-coded values into shadow registers if
                     these NICs are detected.
           Impact  : Errors subside with long cables.


    Enhancements:
    -------------
        1) Problem : Driver does not support enough multicast addresses.
           Change  : Moved multicast address tracking within the driver.
                     Added a flag in Space.c to enable support for more
                     multicast addresses.
           Impact  : Driver supports up to 64 multicast addresses.
                     There is a severe backwards compatibility issue if
                     the administrator does not also use the
                     accompanying dlpi/Driver.o file, obtainable
                     through SCO.


v7.5.11  (April 6, 2004)
========================

    Fixes:
    ------
        1) Problem : ANT test fails with delmca error.
           Cause   : Incorrect number of multicast address
                     entries compiled into driver.
           Change  : Fix build system to identify
                     the correct number of supported
                     multicast addresses.
           Impact  : ANT multicast test works.

    Enhancements:
    -------------
        1) Problem : Product banner message unsupported.
           Change  : Add product banner message.
           Impact  : New banner messages.


v7.5.10  (April 1, 2004)
========================

    Enhancements:
    -------------
        1) Problem : LEDs illuminated incorrectly.
           Change  : Moved LED configuration back under driver
                     control.
           Impact  : LEDs illuminate as they should for each
                     mode.


v7.5.9  (March 30, 2004)
========================

    Fixes:
    ------
        1) Problem : llistat -l reports wrong link speed.
           Cause   : Fake link speed was reported because
                     link had not been established at the
                     time of the query.
           Change  : Wait in the open() function until
                     link is established.
           Impact  : The link speed upon bootup will be
                     correctly reported.  Note that the
                     link speed does not change in response
                     to changes in link condition.

    Enhancements:
    -------------
        1) Problem : Firmware autonegotiation not supported.
           Change  : Added code to allow the firmware to do the
                     autonegotiation, if it is capable of doing
                     so.
           Impact  : With autoneg done in the firmware, the driver
                     consumes less CPU resources.


v7.5.8  (March 15, 2004)
========================

    Fixes:
    ------
        1) Problem : 5750 A1 devices hang on initialization.
           Cause   : PCIE "preserve data link" flag mistakenly
                     applied to standard PCI cases.
           Change  : Limit the PCIE fix to PCIE devices.
           Impact  : Device operates as suspected.  PCIE devices
                     unaffected.

        2) Problem : LEDs illuminate incorrectly.
           Cause   : Undetermined
           Change  : Starting with 575X and 572X NICs,
                     the driver lets the firmware
                     control how the LEDs are set.
           Impact  : Firmware LED fixes will be universal
                     to all drivers.


v7.5.7  (March 5, 2004)
=======================

    Fixes:
    ------
        1) Problem : 5750 family link LED does not illuminate to
                     the correct color in wireless combo mode.
           Cause   : Applied fix to wrong location.
           Impact  : LED modes should work as expected.


v7.5.6  (March 4, 2004)
=======================

    Fixes:
    ------
        1) Problem : 5750 family link LED does not illuminate to
                     the correct color in wireless combo mode.
           Cause   : Old LED mode bits need to be set to 1's
                     in order for new LED modes to be enabled.
           Change  : Set old LED bits to ones when a new
                     5750 family LED mode is selected.
           Impact  : LED modes should work as expected.
        2) Problem : 5750A1 family of chips displaying as
                     "Broadcom Compatible"
           Cause   : Installation files not updated to handle
                     A1 revision.
           Change  : Updated installation files.
           Impact  : 5750A1 family of devices are displayed as expected.


v7.5.5  (February 25, 2004)
===========================

    Enhancements
    ------------
        1) Change  : Set a register flag to facilitate PCIE
                     debugging, should a problem occur.
           Impact  : No impact to performance.  Easier debugging.


v7.5.4  (February 23, 2004)
===========================

    Fixes:
    ------
        1) Problem : 5721 is displayed as 575X device.
           Cause   : All 5750 family device IDs were lumped into
                     one configuration file with one descriptive
                     string.
           Change  : Separate 572X devices into a separate
                     configuration file.
           Impact  : 572X devices will correctly be displayed as such.
        2) Problem : Driver crashes on unload.
           Cause   : A race condition in the unload routine.
           Change  : The unload routine sets a flag to notify other
                     threads that the device is no longer accessible.
                     This flag was simply moved earlier in the unload
                     routine.
           Impact  : Race condition eliminated.
        3) Problem : GetAdapterInfo locks up system.
           Cause   : PXE sometimes does not shutdown properly.
           Change  : Detect improper shutdown conditions and issue a
                     GRC reset.
           Impact  : Chips is reset to a known state, and initialization
                     can continue.

    Enhancements
    ------------
        1) Problem : Driver missing 575X and 572X A1 support.
           Change  : Added code for 5750A1 family of devices.
           Impact  : 5750A1 family of devices properly supported.


v7.5.3  (January 26, 2004)
===========================

    Fixes:
    ------
        1) Problem : Normal TCP and UDP traffic not seen when adapter
                     is put into promiscuous mode.
           Cause   : Internal receive flags were not being preserved
                     when promiscuous mode was enabled.
           Change  : Preserve receive flags.
           Impact  : All cards.
        2) Problem : Netperf shows wildly incorrect transmit
                     statistics.
           Cause   : Driver was dropping packets it didn't necessarily
                     have to drop.  Dropped packets are seen as
                     having been transmitted successfully by upper
                     layers.
           Change  : Push packets back onto the queue for transmission
                     later during high load situations.
           Impact  : All cards.
        3) Problem : System hangs when loading the driver on a PCIE
                     system.
           Cause   : PCIE detection code incorrect, causing PCIE
                     specific codepaths not to be executed.
           Change  : Fix PCIE detection code.
           Impact  : All PCIE devices.


v7.5.2  (January 13, 2004)
===========================

    Fixes:
    ------
        1) Problem : 575X devices fail after GRC reset.
           Change  : Changed delay to 500 msec after GRC reset.
           Impact  : All 575X, and 572X cards.
        2) Problem : Some register writes fail on 575X cards.
           Change  : Add register read back on PCIE systems.
           Impact  : All PCIE devices.
        3) Problem : Some register writes fail on SMP systems.
           Change  : Make driver single threaded.
           Impact  : All PCIE devices.
        4) Problem : No link interrupts are delivered.
           Change  : Added code to poll for link interrupts.
           Impact  : All PCIE devices.
        5) Problem : Asf fails after GRC reset.
           Change  : Moved KevT assignment to before GRC reset.
           Impact  : All cards.

    Enhancements:
    -------------
        1) Problem : 575X cards missing new LED modes.
           Change  : Added new 5750 family LED modes.
           Impact  : All 575X, and 572X cards.



v7.0.5  (October 13, 2003)
============================

    Fixes:
    ------
    1. Problem : Driver locks up on load.
       Cause   : New link status code forces the driver to sleep
                 when it isn't necessary.
       Change  : Added a test to ensure it is necessary to sleep
                 before doing so.
       Impact  : All cards.



v7.0.4  (October 13, 2003)
============================

    Enhancements:
    -------------
    1. Problem : Missing some initialization strings for the
                 5705 A3.
       Change  : Added missing 5705 A3 initialization strings.
       Impact  : All 5705 A3 cards.


v7.0.3  (October 8, 2003)
============================

    Fixes :
    --------
        1) Problem : (CQ8520) NC7761 controller listed twice.
           Cause   : Accidental inclusion of a legacy AOF file.
           Change  : Deleted legacy file.
           Impact  : Most cards.

        2) Problem : (CQ8534) NC7761 controller listed as
                     "unknown" in syslog messages.
           Cause   : The device ID changed between the 5705A2
                     and the 5705A3.  The driver was not updated
                     to detect the new device ID.
           Change  : Added new device ID to the detection code.
           Impact  : NC7761 cards.


v7.0.2  (September 23, 2003)
============================

    Fixes :
    --------
        1) Problem : (CQ8485) Unable to identify 5704 B0 card.
           Cause   : Missing vendor and device ID's in AOF file.
           Change  : Added missing entries
           Impact  : 5704 B0


v7.0.1  (August 26, 2003)
=========================

    Fixes :
    --------
        1) Problem : Implementation of 1.2V change incorrect.
           Cause   : Some critical bits were not preserved,
                     potentially causing problems.
           Change  : Preserve the critical bits.
           Impact  : 5704S B0


v7.0.0  (August 25, 2003)
=========================

    Fixes :
    --------
        1. Problem : Slot number reported as "0" no matter which
                     physical port is being used.
           Cause   : The device structure stores the slot number
                     in two different locations.  One of the locations
                     was not updated with the correct information.
           Change  : Update the stale field.
           Impact  : All cards.


v6.1.0  (August 14, 2003)
=========================

    Fixes :
    --------
        1. Problem : Driver sometimes gets a MAC address of all zeroes.
           Cause   : In some rare timing related situations, the
                     firmware is behind in providing the MAC address
                     for the driver at the MAC control registers.
           Change  : Driver will get the MAC address from NVRAM when
                     the MAC address read from the MAC control
                     registers is all zeros.
           Impact  : All cards.

        2. Problem : Performance enhancement : ADC and gamma fix.
           Cause   : Suboptimal default configuration.
           Impact  : Decreases transmission error rate and improves
                     cable length.
           Impact  : All 5702/3/4 AX copper chips.

        3. Problem : Serdes drive level change for 5704S and 5704CIOBES.
           Cause   : Default configuration.
           Change  : Change drive transmission level to 1.2V.
           Impact  : 5704S and 5704CIOBES chips.

        4. Problem : On 5704 AX chips, a DMA transfer that uses the last
                     byte on the 4G boundary will trigger a
                     "Host address overflow" error.
           Cause   : HW bug.
           Change  : Add code to detect if the current DMA transfer
                     address and length intersect with the 4G boundary.
                     Fall back to a double copy method if they do.
           Impact  : 5704 AX chips only.

        5. Problem : (CQ8231) 5704 B0 devices show up in netconfig as
                     "Broadcom compatible".
           Cause   : Out of date configuration file.
           Change  : Add 5704 B0 configurations.
           Impact  : 5704 B0 chips.

        6. Problem : (CQ8049) Advanced option menu shows "-" in
                     line speed option menu for fiber cards.
           Cause   : Options that were not valid in fiber cards were
                     replaced with dashes ('-'s).  The dashes still
                     showed when the options were presented to the
                     user.
           Change  : Reordered the options so that all common options
                     between fiber and copper cards appear first.  All
                     placeholder dashes removed.
           Impact  : All fiber cards.

   Enhancements:
   -------------
        1. Problem : (CQ7592) Link messages missing slot and port numbers.
           Change  : Added slot and port numbers to link messages.
           Impact  : All chips.

        2. Problem : (CQ7590) Broadcom driver does not support event
                     logging.
           Change  : Added a function which calls a kernel facility, if
                     present, to report link failure.
           Impact  : All chips.


v6.0.13 (August 13, 2003)
=========================

   Enhancements:
   -------------
   1. Problem : 5704 B0 not supported.
      Change  : Added code to support 5704 B0.
      Impact  : 5704 B0

v6.0.10 (June 11, 2003)
======================

   Enhancements:
   -------------
   1. Problem: OEM branding was removed in ver 6.0.6.

      Change: Added branding for one major OEM.

      Impact: There may be duplicate devices listed in netconfig for
              this OEM's devices.

   2. Problem: Unsupported line speeds are listed as options in
               netconfig for fiber devices.

      Change: Added a new fiber-specific AOF file for 5704S and one
              major OEM's fiber devices.

      Impact: There may be duplicate devices listed in netconfig for
              this OEM's devices.

v6.0.6 (June 02, 2003)
======================

   Enhancements:
   ------------
   1. Problem: Multiple NICs are detected when subvendor and subsystem IDs
               conflict with the NIC devices.

      Change: Changed AOF files to use vendor and device IDs.

      Impact: Only netconfig.

   2. Problem: Link down messages are displayed at NOTICE level. 

      Change: Changed link down messages to WARNING.

      Impact: None.

v6.0.4 (May 29, 2003)
=====================

   Enhancement:
   ------------
   1. Problem: Driver does not have OEM IDs for 5703 B0 devices

      Change: Added new device ID and OEM IDs.

v6.0.2 (April 29, 2003)
=======================

   Fixes:
   ------
   1. Problem: In some extremely rare situations, 5703, 5704, and 5705
               Copper NICs may not link up after a PHY reset.

      Cause: On these 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.

v6.0.1 (02/25/03)

- Added a new OEM ID in AOF file.
- Fixed 5704S link up problem when it is set to autoneg and link partner has
  autoneg disabled.

v6.0.0 (02/14/03)

- Added new OEM IDs and new device IDs for 5705 A2/A3.
- Added MAC address override in space.c.

v5.0.10 (01/31/03)

- Added new OEM IDs in AOF file.

v5.0.9 (01/10/03)

- Added workaround for 5704S autoneg.
- Fixed problem detecting 5782.

v5.0.8 (12/20/02)

- Added OEM IDs.
- Improved flow control.

v5.0.7 (12/13/02)

- Added latest OEM IDs.
- Enabled Flow Control Advertisement by default.

v5.0.5 (11/12/02)

- Fixed 5704S linking problem.
- Updated driver for 5705 A1.

v5.0.4 (10/18/02)

- Added support for 5704S hardware autoneg.

v5.0.2 (09/26/02)

- Fixed problem that prevented multiple NICs from loading.

v5.0.1 (09/06/02)

- Added support for 5705.

v3.0.1 (05/21/02)

- Added function number to allow adding the second 5704 interface.

v3.0.0 (05/15/02)

- Added 5704 support.

v2.2.12 (05/14/02)

- Added new OEM IDs.

v2.2.11 (04/12/02)

- Added necessary delays after changing GPIOs.

v2.2.10 (04/05/02)

- Fixed 5701 fiber hang problem when booting without cable.

v2.2.9 (04/03/02)

- Added new OEM subsystem IDs.
- Fixed flow control problems when autoneg. is disabled.

v2.2.8 (03/27/02)

- Added new device IDs.

v2.2.7 (03/22/02)

- Made changes to Fiber autoneg.
- Implemented new scheme for LED modes.

v2.2.3 (02/27/02)

- Added new PCI IDs for 5702/5703.
- Added Ethernet@Wirespeed.
- Fixed parity errors on 5703 in PCIX systems.

v2.2.2 (02/07/02)

- Fixed the cable disconnection problem.

v2.2.1 (02/06/02)

- Fixed problems with 5702/5703.

v2.0.19 (10/26/01)

- Added 5702 support.

v2.0.18 (09/10/01)

- Fixed the problem of over reporting CRC errors.
- Fixed 1000 half duplex late collision problem.
- Fixed the problem of missing the first packet with fiber cards.

v2.0.15 (08/24/01)

- Fixed a hang problem on A3 Fiber cards.

v2.0.14 (08/18/01)

- Fixed a hang problem on BCM5700 NIC when set to 10Mbps.

v2.0.13 (08/13/01)

- Added latest device IDs.

v2.0.11 (08/02/01)

- Fixed a hang problem when booting up with no fibre cable connected.

v2.0.10 (08/02/01)

- Fixed fibre connection problems at boot up time.

v2.0.9 (07/21/01)

- Fixed the problem of multiple NICs sharing the interrupt.

v2.0.8 (07/19/01)

- Fixed some fibre autonegotiation problems.

v2.0.5 (07/02/01)

- Added support for new boards.

v2.0.3 (06/01/01)

- Fixed panic problem when doing flooding ping.

v2.0.2 (05/25/01)

- Added more OEM hardware support.
- Added man page.

v2.0.1 (05/23/01)

- Fixed symbol errors and other errors reported by ANT test.

v1.0.8 (05/16/01)

- Added BCM5701 support.

v1.0.7 (04/02/01)

- Fixed a symbol error reported by ANT test suite.

v1.0.6 (03/30/01)

- Added logic to free buffers on the write queue when it reaches high water
  mark.
- Added workaround for AMD Athlon systems.

v1.0.5 (03/23/01)

- Added fibre support.
- Added jumbo frames.

v1.0.4 (02/23/01)

- Fixed problems found by the ANT test suite.

v1.0.3 (02/14/01)

- First Release. 



