               Broadcom NetXtreme Gigabit Ethernet Driver
                      For Solaris 2.6/7/8/9/10 for
                        i386 / SPARC platform

              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 : (CQ27743) 5700 and 5701 devices fail to load
                     due to memory allocation failures.
           Cause   : Driver attempts to minimize the number of
                     allocation requests to the system by requesting
                     one large chunk of memory and then dividing it
                     up as needed.  Some systems will fail large
                     memory allocations.
           Change  : The code was changed to make several smaller
                     memory allocations rather than one large memory
                     allocation.
           Impact  : This problem affects the following NetXtreme
                     products : 5700, 5701, 5702, 5703, and 5704.


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

    Fixes:
    =============
        1) Problem : Device generates two link interrupts for every
                     physical link event.
           Cause   : Driver contained some legacy code which toggles
                     the link polarity bit in the MAC for every link
                     event.  The polarity change is interpreted as a
                     link event in the MAC, so the MAC generates a
                     second link interrupt.
           Change  : Set the link polarity bit during initialization
                     or reset and leave it alone during link events.
           Impact  : 5702, 5703, and 5704 devices will only generate
                     one link interrupt per link event.

    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   (June 26, 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.4   (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.3   (June 5, 2006)
-----------------------------

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


v9.4.2   (May 12, 2006)
-----------------------------

    Fixes:
    =============
        1) Problem : (CQ24473) 5755 Device stops passing traffic after
                     starting and stopping the Chariot test a few
                     times.
           Cause   : The system is failing to return RX buffers back
                     to the driver under these conditions.
           Change  : Copy packets to a new buffer and send the copy up
                     to the system.
           Impact  : None.

        2) 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.1   (April 13, 2006)
-----------------------------

    Fixes:
    =============
        1) Problem : (CQ24279) DU image usage yields unknown keyword
                     "adapter" messages.
           Cause   : Device descriptions were accidentally word
                     wrapped.  Solaris needs device descriptions
                     to be on one line.
           Change  : Unword-wrap the device description lines.
           Impact  : None.

    Enhancements:
    =============
        1) Change  : Added Solaris 10 support back into DU images.
           Impact  : None.


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

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


v9.0.5   (April 13, 2006)
-----------------------------

    Fixes:
    =============
        1) Problem : (CQ24279) DU image usage yields unknown keyword
                     "adapter" messages.
           Cause   : Device descriptions were accidentally word
                     wrapped.  Solaris needs device descriptions
                     to be on one line.
           Change  : Unword-wrap the device description lines.
           Impact  : None.

    Enhancements:
    =============
        1) Change  : Added Solaris 10 support back into DU images.
           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.5   (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.4   (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.3   (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.2   (December 15, 2005)
-----------------------------

    Enhancements:
    =============
        1) Change  : Added 5714S and 5715S support.
           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) Change  : Added ECD13216 fix for SERDES crosstalk problem.
           Impact  : None.

        3) 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.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 : (CQ12766) After boot, the console has a message
                     that states "bcme mod_remove() failed rc=16".
           Cause   : The mod_remove() function is failing to remove
                     the module because it is still in use.
           Change  : Perform our own in-use check to prevent the
                     (harmless) error message from appearing.
           Impact  : None.

        2) 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 : 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 09, 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.

        2) Problem : (CQ12596) System crashes when unloading the bcme
                     module while devices are still configured.
           Cause   : Solaris 10 removed a check from the system that
                     prevented driver teardown if there were devices
                     configured.  In effect, the system attempts to
                     detach devices and our driver will comply without
                     performing its own checks.  A dereference of a
                     stale device handle is what causes the crash.
           Change  : Insert a check into the code to make sure the
                     device is not active before attempting to remove
                     it from the system.  If so, fail the detach
                     request.
           Impact  : None.

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


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

    Fixes:
    =============
        1) Problem : (CQ12767) Incorrectly deconstructing a DHCP
                     controlled device and then killing the dhcpagent
                     process causes the machine to reboot.
           Cause   : The deconstruction of the device causes the
                     device private memory to be freed.  Killing
                     the dhcpagent process causes the streams portion
                     of the driver to access the freed memory, which
                     causes a segfault.
           Change  : Add code to the device detach function to detect
                     whether or not the device is still in use.  If so,
                     fail the detach request.
           Impact  : The code changes will prevent the machine from
                     crashing when performing improper DHCP teardown.
                     The rest of the problem (i.e. a device that
                     remains open when it intuitively shouldn't be)
                     cannot be addressed by the driver.

    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 : (CQ12474) There is no way for the system to
                     reliably reread the bcme.conf configuration file.
           Cause   : Starting with Solaris 10, the administrator can
                     no longer unload and reload the driver to get
                     the configuration changes recognized by the
                     system.  The recommended way is to use update_drv.
                     Unfortunately update_drv has a bug which prevents
                     interfaces from being plumb'd back into the
                     system.
           Change  : Update readme to outline a new procedure on how
                     to get configuration changes into the system.
           Impact  : This solution will require that the administrator
                     keeps around the BRCMbcme.tar.Z file around so
                     that they can use it to make configuration changes.

        2) 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 : (CQ12463) DU image missing 64-bit driver.
           Cause   : Error in duimage processing script.
           Change  : Overwrite existing pkgmap file with patched
                     version.
           Impact  : DU image now supports x86_64 machines.

        2) 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.

        3) 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.

        4) 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)
---------------------------

    Fixes:
    =============
        1) Problem : (CQ12463) DU image missing 64-bit driver.
           Cause   : Existing tools not prepared to support new
                     feature.
           Change  : Modified our DU image manipulation script
                     to inject the 64-bit driver into the package.
           Impact  : DU image now supports x86_64 machines.

        2) Problem : (CQ12320) Driver fails to initialize 5751
                     devices on Solaris 10 32-bit.
           Cause   : When the driver allocates rx buffers, it uses
                     a system call that does not factor in constraints.
                     The system gives our driver a buffer that is not
                     physically contiguous.
           Change  : Use an allocation method that allows us to specify
                     constraints, such as contiguity.
           Impact  : This solution may exhaust DMA resources quicker.
                     If so, it may be necessary to redesign the buffer
                     allocations to use a pooling approach.

    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.

    Enhancements:
    =============
        1) Problem : Driver lacks support for new AMD64/EM64T chips.
           Change  : Add 64-bit support for these chips.
           Impact  : None.


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 : (CQ11900 and CQ11909) Unable to run high traffic
                     network utilities on Solaris 10 installations.
           Cause   : Code that reacts to DMA setup failures returns
                     an error code which causes the driver to drop
                     packets.
           Change  : Fix DMA setup failure code to return an error code
                     which will allow the driver to fall back to slower
                     transmission methods.  Fixed DMA setup code to
                     fail much less often.
           Impact  : Traffic passes as expected and performance is
                     retained.

    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 06, 2005)
---------------------------

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

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


v7.7.7  (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.6  (December 9, 2004)
---------------------------

    Fixes:
    =============
        1) Problem : (CQ11571) Driver crashes when using DU image
                     to install driver.
           Cause   : DU image using an older driver.
           Change  : Fix the DU image build process to use the
                     correct driver file.
           Impact  : Driver installs as expected.

        2) Problem : (CQ11368) Driver statistics not getting
                     updated.
           Cause   : Statistics-gathering timeout self-terminates
                     prematurely.
           Change  : Disallow timeouts the ability to self-terminate.
           Impact  : Statistics update as expected.


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

    Fixes:
    =============
        1) Problem : (CQ11443) System will freeze after 30 iterations
                     of the load / unload test with 5751 devices.
           Cause   : If the timing is just right, the driver can get
                     into an infinite interrupt loop.
           Change  : Reorganize the code to remove the infinite
                     interrupt loop.
           Impact  : Devices work as expected.

        2) Problem : (CQ11448) 5704 LOM interfaces will not ping.
           Cause   : Missing Single Write Disconnect fix.
           Change  : Added single write disconnect fix.
           Impact  : 5704 devices ping as expected.

        3) Problem : Kernel panics with a mutex violation.
           Cause   : Driver held a streams mutex across a qreply call.
           Change  : Reorganized code to release mutex before calling
                     qreply().
           Impact  : None.

    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 : (CQ11219) Driver freezes machine under stress.
           Cause   : Error in resource release code.
           Change  : Changed code so that previously erroneous test
                     will work.
           Impact  : All resources can be released properly.  Driver
                     works as expected.

        2) 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.

        3) 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) Change  : Added code to print the firmware version.
           Impact  : Checking the firmware version just got a little
                     easier.
        2) 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  (October 27, 2004)
--------------------------

    Fixes:
    ======
        1) Problem : (CQ10483) Driver will not load on 5700B3 with
                     WOL enabled.
           Cause   : Device was still in low-power mode.
           Change  : Bring device out of low-power mode before
                     attempting initialization.
           Impact  : Device works as expected.

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

        2) Change  : Added ASF / IPMI support.
           Impact  : New feature support.

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

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


v7.5.10  (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.


Version 7.5.9 (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.


Version 7.5.8 (April 6, 2004)
-----------------------------

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


Version 7.5.7 (April 1, 2004)
-----------------------------

    Enhancements :
    ==============
        1) Problem : LEDs illuminating incorrectly.
           Change  : Put LED configuration back under driver
                     control.
           Impact  : LEDs now illuminate correctly.


Version 7.5.6 (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.


Version 7.5.5 (March 12, 2004)
------------------------------

    Fixes :
    ========
        1) 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.


Version 7.5.4 (March 5, 2004)
-----------------------------

    Fixes :
    ========
        1) Problem : On 5750 family devices, ping only gets a couple
                     round trip packets before the interface
                     becomes unresponsive.
           Cause   : Watchdog timer interfering with normal
                     operation.
           Change  : Disable watchdog timer.
           Impact  : Ping packets are sent and received
                     indefinately.


Version 7.5.3 (February 24, 2004)
---------------------------------

    Fixes :
    ========
        1) Problem : Failed to retrieve MAC address from NVRAM.
           Cause   : Driver times out too early when waiting for
                     NVRAM data to be returned.
           Change  : Lengthen the timeout value.
           Impact  : MAC address retrieval more reliable.

        2) Problem : System locks up on driver initialization.
           Cause   : PXE sometimes does not shutdown properly.
           Change  : Detect improper shutdown conditions and
                     reset the hardware.
           Impact  : Chip is reset to a known state and initialization
                     can continue.

        3) Problem : Under extreme loads, the SPARC version of the
                     driver will not accept any more packet submissions,
                     and stays in this state indefinately.
           Cause   : The driver set an out-of-resources flag, but never
                     reevaluated it when conditions lightened.
           Change  : Insert code to reevaluate resource allocation and
                     unset the flag.
           Impact  : System flow controls all new packets as expected.

        4) Problem : ASF causes the driver to crash.
           Cause   : Driver attempts to access a value that ASF is also
                     attempting to access.  Driver was not previously
                     ASF aware.
           Change  : Pause ASF.
           Impact  : Driver conflicts resolved and operates as expected.

    Enhancements :
    ==============
        1) Change  : Added support for 575X and 572X A1 chips.
           Impact  : All software fixes to hardware problems in A0
                     silicon and have been addressed by the A1 version
                     of the chips have been disabled for faster
                     performance.

        2) Problem : Driver does not support Multipathing.
           Change  : Added "notification" support to the driver.
           Impact  : Broadcom devices should now be able to be set to
                     failover configurations.


Version 7.5.2 (January 13, 2004)
---------------------------------

    Enhancements :
    ==============
        1) Change  : Changed delay to 500 msec after GRC reset.
           Impact  : All 575X, and 572X cards.
        2) Change  : Add register read back on PCIE systems.
           Impact  : All PCIE devices.
        3) Change  : Added code for 5750 family SMP workaround.
           Impact  : All PCIE devices.
        4) Change  : Added new 5750 family LED modes.
           Impact  : All 575X, and 572X cards.
        5) Change  : Moved KevT assignment to before GRC reset.
           Impact  : All cards.
        6) Change  : Added polling code for link status.
           Impact  : All 5751*, and 572* cards.


Version 7.5.1 (December 12, 2003)
---------------------------------

    Enhancements :
    ==============
        1) Problem : Cardbus event support suboptimal.
           Change  : Enhanced cardbus event support.
           Impact  : All 575X, and 572X cards.


Version 7.5.0 (December 2, 2003)
---------------------------------

    Fixes :
    ========
        1) Problem : (CQ8294) Incorrect hwtype flag.
           Cause   : Incorrect structure initialization.
           Change  : Changed flag to correct type.
           Impact  : All cards.

        2) Problem : (CQ8559) IPV6 does not work.
           Cause   : It looks as though upper layers setup the IPV6
                     connection differently when the hwtype flag
                     changed.
           Change  : Fixed with hwtype flag change above.
           Impact  : All cards.

    Enhancements :
    ==============
        1) Problem : No 5750, 5750M, 5751, 5751M, 5720, or 5721
                     support.
           Change  : Added support for these devices.
           Impact  : All these cards now work.


Version 7.0.4 (October 13, 2003)
--------------------------------

    Enhancements :
    ==============
        1) Problem : Missing initialization strings for 5705 A3.
           Change  : Added more strings for 5705 A3.
           Impact  : 5705 A3.


Version 7.0.3 (August 27, 2003)
--------------------------------

    Fixes :
    ========
        1) Problem : Driver fails to load on beta versions of
                     Solaris 10.
           Cause   : Benign protocol violation.
           Change  : Removed offending code.
           Impact  : Solaris 10 beta.


Version 7.0.2 (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


Version 7.0.1 (August 21, 2003)
--------------------------------

    Fixes :
    ========
        1) Problem : Disabling flow control does not work.
           Cause   : The variable which holds the flow control settings
                     does not get zeroed before being OR'd with the
                     current bits.
           Change  : Zero the variable.
           Impact  : All cards.


Version 7.0.0 (August 20, 2003)
--------------------------------

    Fixes :
    ========
        1) Problem : (CQ8284 and CQ8296) 5704 B0 fails to load or
                     transmit, or hangs system.
           Cause   : The 5704 B0 required a software change to enable
                     some hardware fixes.  This change involved
                     writing to the high 16 bits of a 32 bit register
                     which has traditionally been 16 bits wide.
           Change  : Change the register definition to 32-bits.
           Impact  : 5704 B0.

        2) Problem : (CQ8348) "Phy reset failed" message shown
                     during a flow control change on a fiber card.
           Cause   : A call to reset the PHY was added as part of
                     a bugfix for another copper-related problem.
                     The addition failed to detect whether or not
                     the driver was really running on a copper card.
           Change  : Add a check for copper / fiber.
           Impact  : All fiber cards.


Version 6.8.0 (August 13, 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.
           Change  : 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.


Version 6.7.10 (August 6, 2003)
-------------------------------

    Fixes :
    ========
        1) Problem : New 5704 B0 support causes problems on some Compaq
                     machines.
           Cause   : Bit 27 causes the problem.
           Change  : Clear bit 27
           Impact  : 5704 B0


Version 6.7.9 (August 5, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : No support for 5704 B0
           Cause   : New product.
           Change  : Added support.
           Impact  : 5704 B0


Version 6.7.8 (June 19, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #8046) While running the load/unload stress
                     test, the remote end fails to link after 400
                     to 600 iterations.
           Cause   : When implementing hw autoneg for the 5704, and
                     fixing the phy lockup on 5703/4/5 cards, some
                     code was commented that forced the link down and
                     back up again.
           Change  : Reenable the commented code.
           Impact  : All fiber cards.


Version 6.7.7 (June 16, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #8032) Forcing speed causes kernel panic.
           Cause   : Any time the kernel detects two mutex_enter()s
                     on the same mutex in the same thread, it panics.
                     To fix CQ7947, a mutex was used to serialize
                     access to the PHY.  The crash in this case was
                     caused by a misplaced mutex_enter().
           Change  : Remove the offending mutex_enter() and
                     accompanying mutex_exit().  The phy access
                     they protect was done so at a later and more
                     appropriate place.
           Impact  : All 5700, 5701_B2, and 5701_B5 cards.


Version 6.7.6 (June 11, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #7979) BCM5703B0 crashes PCI100MHz system.
           Cause   : During a code cleanup, a test was accidentally
                     inverted.  This caused memory to be freed
                     prematurely, thus causing a crash on next
                     access.
           Change  : Inverted the inversion.
           Impact  : All cards.


Version 6.7.5 (June 9, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #7979) BCM5703B0 crashes PCI100MHz system.
           Cause   : Fix for previous 100MHz bug was not carried
                     forward.
           Change  : Included 5703B0 (all 5703 cards now) as part of
                     fix.
           Impact  : All 5703B0 cards running on PCI100MHz bus systems.


Version 6.7.4 (June 6, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #7947) Phy locks up when changing speed
                     duplex. 
           Cause   : On multiprocessor machines, the ISR and the
                     function which sets the speed/duplex contended
                     for phy access and configuration.
           Change  : Added a mutex to protect phy access.
           Impact  : All cards running on SMP machines.  The problem
                     is more visible with 5703/4/5 cards.


Version 6.7.3 (June 4, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #7102) Forcing the speed on fiber connections
                     causes 100% CPU utilization on the other side.
           Cause   : The driver would endlessly try reautonegotiating
                     instead of accepting the forced link.
           Change  : Modified the driver to correctly detect forced
                     link conditions and accept them.
           Impact  : All fiber cards.

        2) Problem : (CQ #7859) Broadcom DU does not prompt for
                     Solaris OS version.
           Cause   : Since the DU image contains a release.def file,
                     no prompting was necessary.
           Change  : Remove the release.def file.
           Impact  : All DU images now force OS version queries.

        3) Problem : (CQ #7936) macDeviceType displays BCM????
           Cause   : The driver was missing a deviceID type for the
                     5703.
           Change  : Added the new deviceID.
           Impact  : 5703 cards.


Version 6.7.2 (May 7, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : (CQ #7725) Repeatedly loading and unloading the
                     driver causes a crash or reboot.
           Cause   : On an internal failure, the driver failed to free
                     all resources it aquired.  This eventually
                     consumes all available physical memory, thus
                     causing a crash.
           Change  : Recoded driver initialization routine to carefully
                     monitor the process and, on error, properly free
                     allocated resources gathered to that point.
           Impact  : All chips and implementations.


        2) Problem : (CQ #7060) Driver missing warning if X-bar is
                     enabled.
           Cause   : Vendor request.
           Change  : Added detection and warning code.
           Impact  : All 5704 implementations.


Version 6.7.0 (April 29, 2003)
------------------------------

    Fixes :
    ========
        1) Problem : In some extremely rare situations, the 5703, 5704,
                     and 5705 copper NICs may not link up after a PHY
                     reset.
           Cause   : PHY Clocks can get out of sync during PHY reset or
                     forced reautonegotiation.
           Change  : Added PHY Lockup detection and workaround code.
           Impact  : 5703, 5704, 5705 copper.


Older Revisions
------------------------------

v0.1 (02/26/01)  - First Release.

v0.2 (03/01/01)  - Fixed a problem where driver transmits garbage data if packet
                   crosses multiple 4K pages.

v0.3 (03/05/01)  - Enhanced to log Link Up/Down events.
                 - Fixed a problem no more than 4 NICs can be installed in a
                   system.
                 - Fixed a problem where 10/100 Mbps doesn't work.

v0.4 (03/06/01)  - Fixed a problem where command "netstat -i" doesn't show NIC
                   statistics.
                 - Fixed a problem where driver might lock up if number of
                   bytes per fragments is less than 8.
                 - Fixed a problem where ping response time is large if ping
                   packet is big (such as 64K ...)

v0.5 (03/08/01)  - Fixed a problem where driver can no longer transmit after a
                   few hours of operation.

v0.6 (03/12/01)  - Fixed a problem where netperf performance degrades over time.

v0.7 (03/13/01)  - Added features to allow users to configure various driver
                   parameters with configuration file bcme.conf.

v0.8 (03/14/01)  - Fixed a problem where load/unload drivers many times can
                   lock up system.
                 - Driver is now released as standard PACKAGE format.
                 - Fixed a problem where FlowControl being set to 4 in
                   bcme.conf doesn't configure driver correctly.

v0.9 (03/16/01)  - Added Jumbo frame support.
                 - Added more statistics.  These statistics counters can be
                   viewed with netstat -k bcme[instance].
                 - Added support some OEM NICs/LOMs.

v1.0.0 (03/23/01)
                 - Enhanced driver configuration so that driver configurations can
                   be changed via ndd command.
                 - Added proprietory IOCTLs so that driver can be debugged via
                   debug application.
                 - Enhanced to display Broadcom banner when driver is loaded and
                   also display type of NIC detected.

v1.0.1 (03/28/01)
                 - Fixed a problem where driver doesn't load correctly in Dell
                   Viper system.  This is due issue where some PCI devices in the
                   Dell Viper system have the same Subsystem Vendor ID/Device ID.
                 - Added support for Athlon system.

v1.0.2 (04/02/01)
                 - Fixed a problem where Fiber NIC doesn't work when it is
                   connected to switch.

v1.0.3 (04/03/01)
                 - Fixed a problem where SUN compliance test failed after 18 hrs.

v1.0.4 (04/25/01)
                 - Added BCM5701 support.

v1.0.5 (05/02/01)
                 - Added support for new OEM NICs.
                 - Changed banners for Broadcom NICs to "Broadcom NetXtreme ..."

v1.0.6 (05/08/01)
                 - Fixed a problem where driver per-instance parameters cannot
                   be configured with bcme.conf.

v1.0.7 (05/11/01)
                 - Added support for new OEM NICs.

v2.0.0 (05/25/01)
                 - Added 64-bit driver support for SPARC platform (SPARC
                   version 9 instruction set).  It has been tested on
                   Ultra-30 and Utra-5 platform.
                 - Added Hot-plug support.

v2.0.1 (05/30/01)
                 - Fixed a problem where driver doesn't load on  Intel platform
                   with Solaris 7 O/S.
                 - Added support for Autonegotiate for individual speed.
                 - Enhanced to allow O/S to transmit when no link is detected.

v2.0.2 (06/01/01)
                 - Fixed a problem where driver doesn't recognize a certain
                   OEM NICs.
                 - Fixed a problem where dirver is unable to Autonegotiate
                   1000 Mbps Full Duplex ONLY.

v2.0.3 (06/24/01)
                 - Optimized data path.
                 - Added support for new NIC types.

v2.0.4 (06/25/01)
                 - Optimized data path via host coalescing parameters.

v2.0.5 (07/03/01)
                 - Added support for Solaris 2.6.
                 - Added ndd option to allow users to blink all LEDs of
                   a given NIC instance for a given duration.
                 - Fixed a problem where netperf intermittently fails in
                   a certain configuration.
                 - Added support for 32-bit version NICs.

v2.0.6 (07/06/01)
                 - Fixed a problem where interface hangs up when Jumbo
                   frame is enabled and under heavy traffic such as
                   Chariot performance testing.
v2.0.7 (08/04/01)
                 - Fixed a problem where promiscuous mode doesn't work.

                 - Fixed a problem where flow-control cannot be set
                   via ndd command on Fiber interface.
                 - Fixed a problem where not all LEDs are blinked via
                   ndd command on BCM5700-based NICs.
                 - Added software workaround AMD Athlon issue.
                 - Changed default host coalescing parameters to improve
                   Netpef Performance.

v2.0.11 (08/30/01)
                 - Fixed a problem where driver fails to initialize in
                   a certain Compaq machines.
                 - Added checksum offload support.
                 - Optimized Tx performance.
                 - Fixed a problem where per-instance parameters are not
                   set correctly if instance number is 16.
                 - Provided software workaround if NIC is behind an external
                   PCI-X bridge.

v2.0.12 (08/31/01)
                 - Fixed a problem where interface is hung under heavy traffic
                   and a lot of clients.

v2.0.13 (09/01/01)
                 - Fixed a problem where driver doesn't recover after DMA write
                   underrun is detected on the PCI-X platform.

v2.0.14 (09/10/01)
                 - Fixed FCS counter issue.
                 - Fixed some OEM strings.
                 - Fixed a problem systems might hang up during bootup time if
                   Fiber NICs are on some systems.
                 - Fixed a problem performance is low on 1000 Mbps Half.

v2.0.15 (09/13/01)
                 - Fixed a problem where link can come up at 10Mbps if pre-boot
                   WOL is enabled on the NIC in back-to-back configuration.
                 - Fixed a problem where setting speed/duplex with ndd command
                   doesn't work if speed/duplex is changed from Selective
                   Autoneg to Autoneg.

v2.0.16 (09/14/01)
                 - Fixed a problem where system might crash if cable is unplugged
                   under heavy traffic. This problem only occurs on BCM5700-based
                   NICs.  It also requires bootcode firmware version 2.4 or
                   newer.

v2.0.18 (09/24/01)
                 - Enhanced performance when running in the SPARC environment.
                 - Added a workaround where older version of OpenBoot firmware
                   (in some Sun systems) doesn't initialize upper 32-bit of
                   64-bit BAR.

v2.0.19 (10/18/01)
                 - Fixed a problem where driver doesn't work correctly when
                   single LED mode is utilized in BCM5701-based NIC/LOM.
                 - Added support for BCM5702 and BCM5703.

v2.0.20 (10/25/01)
                 - Fixed a problem where receiving data can be corrupted under
                   heavy traffic in high-speed (>100 MHz) PCI-X systems.

v2.0.21 (10/29/01)
                 - Fixed a problem where performance is degraded in Intel
                   platform.
                 - Fixed a problem where jumbo frame is broken in Intel platform.


v2.1.0 (01/20/02)
                 - Fixed display banners for BCM5702/BCM5703 NICs.
                 - Fixed a problem where BCM5702 LOM might not be initialized
                   correctly if subsystem Vendor ID/device ID  of all PCI
                   devices  in the system are identical.

v2.1.1 (01/22/02)
                 - Fixed a problem where interface hangs up if O/S requests
                   transmiting packets with over 256 fragments (CQ2710).

v2.1.2 (02/22/02)
                 - Added support for Ethernet WireSpeed feature for BCM5702/
                   BCM5703 NICs/LOMs.
                 - Fixed a problem where NFS copy/compare test stops
                   intermittently when 2 PCs connected back-to-back (CQ3296).
                 - Fixed a problem where bcm5703 fiber card comes up as
                   14e4,1647 instead of 14e4,a. (CQ3246)
                 - Added support for NICs with device ID 0x16a6 and 0x16a7.

v2.1.4 (03/22/02)
                 - Added support for different LED configurations.
                 - Enhanced performance for BCM5702/BCM5703-based NICs/LOMs.
                 - Fixed a problem where MAC device type/revision is not
                   displayed accurately for BCM5702/BCM5703.

v2.1.5 (03/22/02)
                 - Enhanced Fiber LED configuration per OEM's requirements.
                 - Added support for new OEM adapters.

v2.1.6 (04/01/02)
                 - Fixed a problem where BCM5701 doesn't work well in
                   Compaq 8500 PCI-X 100MHz Slot. (CQ3782)

v2.1.7 (04/03/02)
                 - Added support for new OEM NICs.

v2.1.8 (04/04/02)
                 - Fixed a problem where certification fails. (CQ3821)

v2.1.9 (04/10/02)
                 - Fixed a problem where driver doesn't work reliably on
                   Compaq DL850 PCI-X slot.

v2.1.10 (04/16/02)
                 - Fixed a problem where jumbo frame doesn't work in SPARC
                   environment.
                 - Fixed a problem where driver hangs up during stress test
                   with BCM5704-based NICs.

v2.1.11 (04/22/02)
                 - Removed BCM5704 support.

v3.0.0 (05/30/02)
                 - Added BCM5704 support.
                 - Fixed a problem where BCM5704-based NIC fails on the PCI-X
                   slots. (CQ4142)
                 - Fixed a problem where macDeviceType in statistics doesn't
                   indicate BCM5704-based NICs correctly. (CQ4161)
                 - Fixed a problem where Netperf UDP test fails with
                   BCM5704-based NICs. (CQ4170)
                 - Added support for Solaris 7 DU package.
                 - Fixed a problem where CPU utilization is high for
                   BCM5704-based NICs. (CQ4297)

v3.0.1 (06/26/02)
                 - Fixed a problem wher RIP packets are sent out with
                   invalid MAC type field in Solaris 7.0 environment. (CQ4497)

v5.0.0 (10/06/02)
                 - Added support for BCM5704 Fiber.
                 - Added support for BCM5705.
                 - Fixed a problem where kstats reports wrong information for
                   BCM5704A1 NICs.

v5.0.1 (10/10/02)
                 - Fixed a problem where DU image doesn't create floppy disk
                   label. (CQ4955)
                 - Removed "Driver" string from driver description. (CQ4304)
                 - Fixed a problem where BCM5703 A3 NIC doesn't work in PCI-X
                   100 MHz. (CQ5728)
                 - Fixed so that jumbo frame is not configurable for BCM5705.

v5.0.3 (10/27/02)
                - Fixed a problem where manual page file is not copied to
                  man directory in  i386 platform.
                - Fixed a problem wher BCM5705 interface might hang during
                  repeated sequence of load/unload. (CQ5845)

v6.0.0 (02/07/03)
                - Updated all copyright strings.
                - Default flow control is now 4 (auto)

v6.0.1 (02/10/03)
                - Added code to zero pad bytes of short (<64B) packets.
                - Added RDMA and WDMA clockfix for 5705_A3 cards
                - Disable Ethernet@Wirespeed for latest 5705 cards
                - Changed Compaq strings to HP.
                - Added new device IDs and strings for 5705A3, 5705MA3,
                  and 5901A3 revisions.
                - Added new deviceIDs to postinstall script.

v6.0.2 (02/12/03)
                - Additional ethernet@wirespeed changes.
                - Added a new macDeviceType entry for 5782
                - Fixed bcmedu.img file to support 5782
                - Fixed FlowControl bug
