release.txt Driver File Contents (LAN_Broadcom_v10.46.0.0_Vistax86x64_XPx86.zip)

                          ============================
                           R E L E A S E    N O T E S
                          ============================

                       Broadcom NetXtreme Gigabit Ethernet Driver
                For Windows 2003  32/64 bit versions, Windows XP 32/64 bit,
                  Windows 2000, Windows NT 4.0, Windows ME, Win98/SE.

                  Copyright (c) 2000-2007 Broadcom Corporation
                               All rights reserved.

Version 10.42  July 22, 2007
----------------------------------------
1. Enhancement
       CQ30670 - disable LowPower mode for a requested 4part ID, when WOL is 
       disabled and ASF is not present.
 
      Cause:
        For the 5787M, when ASF is not present and WOL is disabled, on entering S3, 
        driver will allow bootcode to put the LOM into IDDQ
        LowPower Mode. 

          An OEM request that IDDQ LowPwr mode be disabled for one selected 
          platform.
 
      Change:
        Prevent the bootcode from putting our LOM into IDDQ LowPwr mode on 
        entering S3 for the requested platform.


Version 10.41d  July 18, 2007
----------------------------------------
   1. Bug Fix
       CQ30363 Incorrect NTamd64 decoration in the models section of 
       amd64 inf. Does not pass chkinf

      Cause:
        

      Change:

      Fixed reference to missing section


Version 10.41c  July 17, 2007
----------------------------------------
   1. Bug Fix

        CQ30363 Incorrect NTamd64 decoration in the models section of 
        amd64 inf 

      Cause:
        NTamd64.5. is not a recognized decoration

      Change:

        Changed the decoration to NTamd64


Version 10.41b  July 13, 2007
----------------------------------------
   1. Enhancment request

      CQ30433 add 4 part ID for new 5787M OEM system

      Cause:

      Change:

      Changed ID in W2K section from 88A2 to 8892

   2. Bug Fix

      CQ30363 Incorrect NTamd64 decoration in the models section 
      of amd64 inf

      Cause:

      Change:

      Changed the decoration to NTamd64.5.2 as requested
      

Version 10.41  July 12, 2007
----------------------------------------
   1. Enhancment request

      CQ30433 add 4 part ID for new 5787M OEM system

      Cause:

      Change:

      Added new ID
      
   2. Bug fix
   
      CG29916: Disable hardware fix that causes MAC loopback test to fail
      frequently when tested at 10Mbps (full or half duplex).
      
   3. Enhancement request
   
      CQ30337: Add 4 part IDs for NC7781 & NC7782
      
      Change:
      
      Added the new IDs
      

   2. Bug Fix

      CQ30363 Incorrect NTamd64 decoration in the models section 
      of amd64 inf

      Cause:

      Change:

      Changed the decoration to NTamd64.5.2 as requested

Version 10.40  June 28, 2007
----------------------------------------
   1. Bug Fix

         29858    - INF update -  add 4part ID for  a specific OEM 

      Cause:

      Change:

       Added new ID
       
Version 10.39b  June 6, 2007
----------------------------------------
   1. Bug Fix

         29838 , 29836,    - INF update -  add 4part ID for  a specific OEM 

      Cause:

      Change:

       Added new ID

 
Version 10.39  June 5, 2007
----------------------------------------
   1. Bug Fix
        CQ29255 5704 fails 2c_offloadlargesend test
        
      Cause:
        fw_tcpseg.h was checked into VSS and not PerForce.
        
      Change:
        Copy fw_tcpseg.h to PerForce projects for NDIS3-5 and NDIS6.
        

Version 10.38  June 4, 2007      
----------------------------------------
   1. Enhancement Request
        CQ29193 Add two part ID support for Caesar to HP specific INF file
      Cause:

      Change:
        Added ParamsM to 167d and 1601. Removed EPA from 16fd

   2. Bug Fix
        CQ29255 5704 fails 2c_offloadlargesend test
      Cause:
        This problem occurs whenever 32-bit TCP sequence number wraps around 
        during segmentation.   The TCP Seq# for this particular failure is 
        0xfffffffa.  This problem has been fixed in other offload firmware 
        modules in year of 2002 but was NEVER backported to TCP segmentation 
        ONLY firmware for BCM5701/02/03/04 used in Windows driver.  In other 
        words, LSO firmware for BCM5705 DOES NOT have this problem.  This 
        explains why hardware-based LSO doesn’t have this problem since it 
        was designed based on BCM5705-based firmware. 
        
      Change:
        New LSO firmware.
 

Version 10.37  June 1, 2007      
----------------------------------------
   1. Enhancement Request
        CQ29650 Add two part ID support for Caesar to HP specific INF file
      Cause:

      Change:
        Added new ID

   2. Enhancement Request
        CQ29625 2-part ID Match for 5756ME Missing from INF for NDIS 4/5/5.1/6
      Cause:

      Change:
        Added new ID

   3. Enhancement Request
         CQ29676 add 4 part ID for new 5787M with NVIDIA MCP73PV 
         for release 10.4c

      Cause:

      Change:
         Added new ID

   4. Bug Fix
         CQ29193 Enable EPA feature to support link negotiation for WoL to the 
        lowest advertised speed ( ie first 10 MBPS then 100 MPBS )

      Cause:
          Missing implementation

      Change:
          Fixed missing implementation



Version 10.36C  May 22, 2007      
----------------------------------------
   1. Bug fix
        CQ29482 - Improperly fixed again
      Cause:

      Change:
        CQ29482 is properly fixed this time


Version 10.36B  May 22, 2007      
----------------------------------------
   1. Bug fix
        CQ29482 - Improperly fixed
      Cause:

      Change:
        CQ29482 is properly fixed

   2. Enhancement Request
        Restore support for 5787 parts
      Cause:

      Change:
        Support restored

Version 10.36  May 18, 2007      
----------------------------------------
   1. Enhancement Request
        CQ29413,CQ29313 - Added OEM 4 part ID
      Cause:

      Change:
        Added OEM 4 part ID

   2. Enhancement Request
        CQ29482 - HP_WS: 10 Mbps WoL EPA Enhancement
      Cause:

      Change:
        Enabled EPA for 4-part IDs

   3. Enhancement Request
        CQ29193 Enable EPA feature to support link negotiation for WoL to the 
        lowest advertised speed ( ie first 10 MBPS then 100 MPBS )
      Cause:

      Change:
        Enabled EPA for 2-part IDs

Version 10.35B  May 08, 2007      
----------------------------------------
   1. Enhancement Request
        CQ29348 - Added OEM 4 part ID
      Cause:

      Change:
        Added OEM 4 part ID

Version 10.35  May 02, 2007      
----------------------------------------
   1. Enhancement Request
        CQ29344 - BugCheck 0x9c on IA64 system when installing the driver on
        a 5703.
      Cause:
        ASPM Code was being executed on devices that did not support ASPM.
      Change:
        Modified the driver to never enable ASPM on devices that do not support
        ASPM.

Version 10.34d  *** Inf Update Only ***  May 01, 2007      
----------------------------------------
   1. Enhancement Request
        Enable EPA EnergyStar feature for requested devices.
      Cause:
        OEM request.
      Change:
        Modified inf file entries for affected devices.

Version 10.34c  *** Inf Update Only ***  April 30, 2007      
----------------------------------------
   1. Enhancement Request
        Enable EPA EnergyStar feature for requested devices.
      Cause:
        OEM request.
      Change:
        Modified inf file entries for affected devices.

Version 10.34b  *** Inf Update Only ***  April 30, 2007      
----------------------------------------
   1. Problem
        CQ29321 - INF file fails chkinf.
      Cause:
        Missing inf file section.
      Change:
        Added missing inf file section.


Version 10.34  April 27, 2007      
----------------------------------------
   1. Problem
        CQ28879 - Intermittently unable to obtain DHCP Address on 5715S.
      Cause:
        When link is initially established, it is very unstable and the
        multiple link up and link down indications was causing the
        protocols to behave improperly.
      Change:
        Added code to debounce link negociation on serdes devices during
        driver initialization.

   2. Problem:
        ASPM is not always enabled when the device driver unloads.
      Cause:
        The device driver was not explicitly enabling ASPM on ASPM
        enabled devices.
      Change:
        Added code to enable ASPM when the device driver unloads.

   3. Enhancement Request
        Enable EPA EnergyStar feature for requested devices.
      Cause:
        OEM request.
      Change:
        Modified inf file entries for affected devices.


Version 10.33  April 18, 2007      
----------------------------------------
   1. Problem
        CQ29049 CRC error on 5703 Long Horn driver v10.10 on WinVistaX86
      Cause:
        5703 specific PHY setup code is not getting executed in all cases
        and a bad AUT is being used.
      Change:
        Change the driver to execute 5703 specific code correctly and destroy
        the bad AUT. 

   2. Problem:
        NDIS driver doesn’t detect iSCSI boot interface correctly.
     Change:
        Changed the NDIS driver to validate iSCSI signature correctly.


Version 10.32B  ** Inf Update Only ** April 13, 2007      
----------------------------------------
   1. Enhancement Request
        CQ29103 Add Thruman 4 part ID on 10.4 project
      Cause:
        OEM has requested the addition of a 4 part ID
      change:
        Added the requested 4 part ID

   2. Enhancement Request
        CQ#28935 remove OEM names from INF files
      Cause:
        Please refer to CQ#28935
      change:
        OEM names removed from affected INF files.


Version 10.32  April 06, 2007      
----------------------------------------
   1. Problem:
        CQ28373 - WinPE encounters Bugcheck 0xA when using 5715S Fiber
        Adapter and no Link cable or Switch connection.
      Cause:
        One of the NDIS Driver Timers dedicated to Fiber Link Auto Negotiation
        and renegotiations was getting armed/set; while it may have been cancelled
        as a result of same Driver getting Unloaded by the Operating System.
      Change:
        Added Driver code to check on the Auto Negotiation Retry Timer; so that
        it is properly Initialized, Set/Armed, and Cancelled during Driver unloading.
      Impact:
        Resolve CQ28373 issue.

   2. Enhancement Request
        CQ28320 - Add PCI 4 part Device ID to INF installation files. 
      Cause:
        New device support requested.
      Change:
        Added new 4 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ28320 Enhancement Request.

   3. Enhancement Request
        CQ28360 - Add PCI 4 part Device ID to INF installation files. 
      Cause:
        New device support requested.
      Change:
        Added new 4 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ28360 Enhancement Request.

   4. Enhancement Request
        CQ28362 - Add PCI 4 part Device ID to INF installation files. 
      Cause:
        New device support requested.
      Change:
        Added new 4 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ28362 Enhancement Request.

   5. Enhancement Request
        CQ28494 - Add PCI 4 part Device ID to INF installation files. 
      Cause:
        New device support requested.
      Change:
        Added new 4 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ28494 Enhancement Request.

   6. Enhancement Request
        CQ27719 - Add PCI 4 part Device ID to INF installation files. 
      Cause:
        New device support requested.
      Change:
        Added new 4 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ27719 Enhancement Request.

   7. Problem
        CQ28736 - Invalid WOL Speed Parameter Displays for NDIS 5 for Dell Desktop/Mobile. 
      Cause:
        Invalid reference to ParamsWOL in the registry setting.
      Change:
        Replaced reference with ParamsWOLNS.
      Impact:
        None.

   8. Problem
        CQ29028, CQ26482 - Blue screen on W2K 3when all offload tasks are
        disabled
      Cause:
        Improper handling of OID_TCP_TASK_OFFLOAD.
      Change:
        Changed the device driver to set OffsetFirstTask to zero when all
        offload tasks are disabled.
      Impact:
        None.

   9. Problem
        CQ28915 - 5703S/5704S serdes is not powered off when adapter is
        disabled.
      Cause:
        A change for CQ14387 had the side effect of leaving the 5703S/5704S
        serdes powered on when the adapter is disabled.
      Change:
        Modified the device driver to power off the serdes on 5703S/5704S
        if WOL is disabled when the adapter is disabled.
      Impact:
        None.

  10. Problem
        CQ28765 - UMP does not get correct link status.
      Cause:
        There is a corner case in the device driver in which it did not
        report link up during driver initialization.
      Change:
        Modified the device driver to always report link state during
        initialization.
      Impact:
        None.

  11. Problem
        CQ28765 - UMP does not get correct link status.
      Cause:
        There is a corner case in the device driver in which it did not
        report link up during driver initialization.
      Change:
        Modified the device driver to always report link state during
        initialization.
      Impact:
        None.

  12.  Enhancement Request:
        CQ28816 Add "L1 ASPM debounce" feature. 
      Cause:
        There is an interoperability issue between the Broadcom
        LAN controllers and the Intel ICH7/8 that may cause the 
        Rx-performance at 100 Mbps to be lower then expected when
        L1 ASPM is enabled along with system CPU C3E, or C4, or C4E 
        or higher state.
      Change:
        Along with the device driver change here, that will drive
        the PCI-E link less aggressively into L1 ASPM during
        network stress, the user must enable the feature
        by setting a configurable option inside the LAN 
        controllers NVRAM.
      Impact:
        There is no known impact from enabling this 
        feature.  As a matter of fact, enabling this
        feature will increase the power savings in
        case the system has disabled 'L1 ASPM' due to 
        the interoperability issue described above.

Version 10.31  February  13, 2007      
----------------------------------------
   1. Problem:
        CQ28164 - 5721/5751/5752 fails phy loopback test.
      Cause:
        Change for CQ26645 is not compatable with phy loopback mode.
      Change:
        Modified the phy loopback code to disable Auto-Mdix when
        phy loopback is enabled.
      Impact:
        None.

   2. Problem:
        CQ27978 - 5787M - On OEM system Hardware malfunction Blue Screen
        occurs after rebooting the system.
      Cause:
        Interrupt sharing driver code was claiming interrupts as per workaround
        for older 5700 device.
      Change:
        Added NDIS Driver code to only perform interrupt claiming for older 5700
        devices and not on the newer PCI-E devices like 5787M.
      Impact:
        Resolve CQ27978 issue.

   3. Enhancement Request:
        CQ28305 Add 5722 based 4 part id's for server customer
      Cause:
        New OEM device support requested.
      Change:
        Added new 4 part OEM PCI ID support in OEM specific NDIS INF files.
      Impact:
        Resolve CQ28305 Enhancement Request.

   4. Enhancement Request
        CQ28427 - Add PCI 4 part Device ID to OEM specific
        INF installation files. 
      Cause:
        New OEM device support requested.
      Change:
        Added new 4 part OEM PCI ID support in OEM specific NDIS INF files.
      Impact:
        Resolve CQ28427 Enhancement Request.

   5. Enhancement Request
        CQ28080 - Add PCI 4 part Device ID to OEM specific
        INF installation files. 
      Cause:
        New OEM device support requested.
      Change:
        Added new 4 part OEM PCI ID support in OEM specific NDIS INF files.
      Impact:
        Resolve CQ28080 Enhancement Request.


Version 10.30  January 18, 2007      
----------------------------------------
   1. Problem:
        When the ndis driver loads on a 5755M, 5787M or 5752M with the cable
        unplugged. The GPHY DLL was not being powered down.
      Cause:
        Corner case in the GPHY DLL power down code.
      Change:
        Corrected GPHY DLL power down code to properly handle the corner case.
      Impact:
        None.

   2.  Enhancement Request:
        CQ28151  Add NDIS driver support for 5756M (PCI DID: 0x1674)
        and 5722 (PCI DID: 0x165A) as part of SW Release v10.4
      Cause:
        Installation support expanded for above Devices.
      Change:
        Added PCI ID support in NDIS INF files, as requested.
      Impact:
        Resolve CQ28151 Enhancement Request.


        

Version 10.24D ** Inf Update Only ** January 8, 2007      
----------------------------------------
   1. Problem:
        CQ28059 Missing friendly strings in inf file.
      Cause:
        Changes ported over from release 9.7 were not complete.
      Change:
        Added missing friendly strings into the inf file.
      Impact:
        None.

Version 10.24C ** Inf Update Only ** January 5, 2007      
----------------------------------------
   1. Problem:
        CQ28059 Missing friendly strings in inf file.
      Cause:
        Changes ported over from release 9.7 were not complete.
      Change:
        Added missing friendly strings into the inf file.
      Impact:
        None.

Version 10.24B ** Inf Update Only ** January 5, 2007      
----------------------------------------
   1. Problem:
        CQ28057 OEM amd64 inf file fails infcheck.
      Cause:
        The inf file was missing a [DelReg.LgSnd] section.
      Change:
        Added missing inf file section.
      Impact:
        None.

Version 10.24  December 14, 2006      
----------------------------------------
   1. Problem:
        CQ27776 5906 intermittently fails BACS Phy Loopback test.
      Cause:
        The 5906 phy auto-mdix feature needs to be disabled during phy
        loopback test.
      Change:
        Modified the ndis driver to disable auto-mdix during phy
        loopback on 5906.
      Impact:
        None.

   2. Problem:
        CQ27867 5906 Fails WHQL Large Send Offload Test
      Cause:
        This feature is not supported on 5906.
      Change:
        Modified the ndis driver and inf file to not report this
        feature to the operating system during ndis driver initialization.
      Impact:
        None.

   3. Problem:
        CQ27832 5755M failing IEEE compliance on certain OEM platforms.
      Cause:
        The phy trim registers needed to be modified by the ndis device driver.
      Change:
        Modified the ndis driver to program the phy trim registers per
        recommendation from phy engineering team.
      Impact:
        None.

Version 10.23  December 8, 2006      
----------------------------------------
   1. Problem:
        CQ27759 5906 fails WHQL packet filter test.
      Cause:
        The 5906 uses a different mechanism to filter broadcast
        packets from previous controllers.
      Change:
        Modified the ndis driver to properly filter broadcast packets
        on 5906.
      Impact:
        None.

Version 10.22  December 4, 2006      
----------------------------------------
   1. Problem:
        CQ27717:Support for 5751F Missing from x64 INF.
      Change:
        Added an entry for this device in the x64 generic inf.
      Impact:
        None.

   2. Problem:
        Low throughput performance on DosXX-5906M with ASPM enabled.
      Change:
        The low performance we are seeing is due to a design flaw 
        in the ASIC. This flaw causes the PCI-e latency during DMA 
        transfer to become unecessarily large, and leads to a lower 
        throughput. The only way to get around this problem, is to 
        coalesce every tx packets for the the 5906, which this Windows 
        driver version does.
      Impact:
        Possibly higher CPU utilization with this version.

   3. Problem:
        CQ27306:Adding WOL support for 5715S, for Tyan S3997, 5715S A3
      Change:
        Added an entry for this device in the generic win32 and x64 
        infs.
      Impact:
        None.

   4. Problem:
        CQ27718:Please remove the following IDs from the b57w9x.inf
      Change:
        Removed the inf entry. 
        infs.
      Impact:
        None.

Version 10.21  November 30, 2006      
----------------------------------------
   1. Problem:
        Phy loopback test for 5906 is not implemented.
      Change:
        Implemented phy loopback test for 5906.
      Impact:
        None.

Version 10.20  November 22, 2006      
----------------------------------------
   1. Problem:
        CQ27551, CQ27500, CQ27498 EnergyStar WOL feature does not work.
      Cause:
        The code for did not configure the phy properly when dropping
        the feature was enabled.
      Change:
        Corrected the EnergyStar feature to configure the phy correctly.
      Impact:
        None.

   2. Problem:
        CQ27588, EnergyStar feature should be enabled by default for
        devices that require the feature.
      Cause:
        Feature request.
      Change:
        Changed the default behavior to enabled for devices that require
        the feature.
      Impact:
        None.

   3. Problem:
        CQ27536, Remove Large Send Offload feature from 5906M.
      Cause:
        Feature request.
      Change:
        Removed Large Send Offload feature from 5906M.
      Impact:
        None.

Version 10.19  November 16, 2006      
----------------------------------------
   1. Problem:
        CQ27477 Forced speed/duplex does not work.
      Cause:
        Changes picked up from the Netware driver disabled the phy
        initialization code.
      Change:
        Modified the changes from the Netware driver so the phy
        initialization code will be executed.
      Impact:
        None.

Version 10.18  November 14, 2006      
----------------------------------------
   1. Problem:
        5906 exhibits poor performance.
      Cause:
        Coalescing all buffers for the 5906 is slow (see fix in 10.17).
      Change:
        Restore the origninal logic which coalesces only when the OS submits
        packets with segments less than 8 bytes. In addition, disable the
        header coalesce logic for the 5906, since it generates segments less
        than 8 bytes (see CQ14560).
      Impact:
        None.

Version 10.17  November 14, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ26645 Enable Auto-MDIX for 5750, 5752, 5755, 5714, 5715 and 5780
        family of controllers.
      Cause:
        The affected contollers defaulted to Auto-MDIX disabled.
      Change:
        Modify the phy init code to enable Auto-MDIX.
      Impact:
        Resolve CQ26645 Enhancement Request.

   2. Problem:
        For the 5906, the driver still sends small Buffer Descriptors to the
        hardware. Due to a chip bug, small buffers cause the DMA engine to
        stall, so the driver is required to screen the packets received from
        the OS, and coalesce all packets which include small buffers.
        In addition, 5906 performance is poor when multiple buffers are sent
        to the hardware.
      Cause:
        Code added to resolve CQ14560 cause the driver to internaly
        generate buffers less than 8 bytes, and submit them to the hardware.      
      Change:
        To workaround these problems, all packets transmitted by the OS
        are coalesced.

   3. Problem:
        CQ27383 WHQL - Fails Duplicate WolPattern test.
      Cause:
        The latest test kit requires the ndis driver to return
        NDIS_STATUS_INVALID_DATA on duplicate patterns.
      Change:
        Modified the ndis driver to return NDIS_STATUS_INVALID_DATA on
        duplicate WOL patterns.

   4. Problem:
        CQ27389 - Fix for CQ14031 is not working.
      Cause:
        Fix for CQ26524 broke fix for CQ14031 by restarting autonegotiation
        when the link partner did not advertise flow control capability.
      Change:
        Modified fix for CQ26524 to not restart autonegotiation if the link
        partner does not advertise flow control.


Version 10.16  November 03, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ26642 VLAN support with iSCSI boot
      Cause:
        Enable VLAN if the interface is used for iSCSI boot and
        VLAN is enabled in the Multiple Boot Agent configuration.
      Change:
        Modify NDIS 5.1 driver to support described feature and
        update T3_OID_GET_DRIVER_INFO to indicate if the
        interface was used in iSCSI boot.
      Impact:
        Resolve CQ26642 Enhancement Request.



Version 10.15  October 28, 2006      
----------------------------------------
   1.  Problem:
        CQ27241, CQ27280 - Unable to pass traffic when the 5752M,
        5755M or 5787M is initialized with the Ethernet cable
        unplugged.
      Cause:
        A bug in the power saving enhancement for 5752M, 5755M and
        5787M controllers was powering down the GPHY DLL during
        controller initialization.
      Change:
        Modified the Ndis driver to not power down the GPHY DLL
        durring controller initialization.
      Impact:
        Resolve CQ27241 and CQ27280.

   2.  Problem:
        CQ27279 - Ndis 5.1 inf file fails HCT CHKINF test.
      Cause:
        New device sections to support OEM requested device IDs
        were not included in the inf file.
      Change:
        Added missing device sections to inf file.
      Impact:
        Resolve CQ27279.


Version 10.14  October 26, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ27189 Add PCI 4 part Device ID to OEM specific
        INF installation files. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in OEM specific
        NDIS INF files.
      Impact:
        Resolve CQ27189 Enhancement Request.

   2.  Enhancement Request:
        CQ27169 Ndis driver should not force PCI-E bus reset when
        shutting down due to bugcheck.
        INF installation files. 
      Cause:
        Engineering design review.
      Change:
        Modified the bugcheck shutdown routine to not reset
        the PCI-E bus when resetting the Ethernet controller.
      Impact:
        Resolve CQ27169 Enhancement Request.

   3.  Enhancement Request:
        CQ27246 Add PCI 4 part Device ID to INF installation files. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ27246 Enhancement Request.

   4.  Enhancement Request:
        CQ27254 Update ia64 build to use patched compiler from MSFT.
      Cause:
        Microsoft has identified a bug in their compiler tools which
        affects dual core Itanium systems. See Microsoft KB924449.
      Change:
        Patched the compiler to newer version of c2.dll.
      Impact:
        Resolve CQ27254 Enhancement Request.

   5.  Enhancement Request:
        CQ27038 Add 4 part PCI ID match support to fallback to lowest
        advertised link speed feature.
      Cause:
        OEM request.
      Change:
        Added new 4 part OEM PCI ID support in OEM specific
        NDIS INF files.
      Impact:
        Resolve CQ27038 Enhancement Request.

Version 10.13  October 13, 2006      
----------------------------------------
   1.  Problem:
        CQ27138 - 5787F Links intermittantly or takes 20 seconds to link.
      Cause:
        The Ndis driver was not handling the 5787F device as a Fast Ethernet
        device.
      Change:
        Modified the Ndis driver to recognize the 5787F as a Fast Ethernet
        device.
      Impact:
        Resolve CQ27138 issue.

Version 10.12  October 11, 2006      
----------------------------------------
   1.  Problem:
        CQ26942 - WHQL 2c_holdpackets test failed.
      Cause:
        The Ndis driver was not waiting long enough for the receive buffers
        to be returned by the upper layers.
      Change:
        Extended timeout for receive buffers to be returned to the device
        driver.
      Impact:
        Resolve CQ26942 issue.

   2. Enhancement Request:
        CQ26981 Add section to Ndis 5.1 inf file for Vista.
      Cause:
        Enhancement request to prevent Ndis 5.1 driver from automatically
        loading on controllers that are supported by the Ndis 6.0 driver.
      Change:
        Added section to Ndis 5.1 inf file to support only 5700,
        5701, 5702 based adapters in Vista.
      Impact:
        Resolve CQ26981 issue.

   3.  Enhancement Request:
        CQ26978  Add PCI 4 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ26978 Enhancement Request.

   4.  Enhancement Request:
        CQ26978  Add PCI 2 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 2 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ26979 Enhancement Request.

   5.  Enhancement Request:
        CQ26645  Add support to fallback to lowest advertised link speed
        for S3/S4.
      Cause:
        New feature request.
      Change:
        Added WOL speed configuration option. Added peer link partner capabilities check
        if fallback is enabled. 
      Impact:
        Resolve CQ26645 Enhancement Request.

   6.  Problem:
        CQ26645 - Auto MDI-X is not enabled on 5755 and 5787 based controllers.
      Cause:
        The embedded phy used on those devices default to Auto MDI-X disabled.
      Change:
        Modified phy init routine to enable Auto MDI-X on 5755 and 5787 based
        controllers.
      Impact:
        Resolve CQ26645 issue.


Version 10.11 C **** INF Update *****  September 22, 2006      
Same Driver Binary as Release v10.11  September 20, 2006
----------------------------------------
   1.  Enhancement Request:
        CQ26538 Add PCI 4 part Device ID for OEM project did not
        verify per one of the OEM installation name references.
      Cause:
        New OEM Device support added in v10.10 had an error in 
        OEM installation name reference.
      Change:
        Corrected the name reference of the 4 part OEM PCI ID
        support in NDIS INF files.
      Impact:
        Resolve CQ26538 Enhancement Request that did not verify.


Version 10.11  September 20, 2006      
----------------------------------------
   1.  Problem:
        CQ26799 - Add device id for 5722.
      Cause:
        The device id for 5722 was not in the inf file.
      Change:
        Added 5722 device id to inf file.
      Impact:
        Resolve CQ26799 issue.

   2.  Enhancement Request:
        CQ26738 Add PCI 4 part Device ID for OEM project did not
        verify.
      Cause:
        New OEM Device support added in v10.10 had an error in 
        PCI SubSystem ID part.
      Change:
        Corrected the PCI Subsystem part of the 4 part OEM PCI ID
        support in NDIS INF files.
      Impact:
        Resolve CQ26738 Enhancement Request that did not verify.

   3.  Enhancement Request:
        CQ26538 Add PCI 4 part Device ID for OEM project did not
        verify.
      Cause:
        New OEM Device support added in v10.10 had an error in 
        PCI SubSystem ID part.
      Change:
        Corrected the PCI Subsystem part of the 4 part OEM PCI ID
        support in NDIS INF files.
      Impact:
        Resolve CQ26538 Enhancement Request that did not verify.



Version 10.10  September 18, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ26465 Add PCI 4 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ26465 Enhancement Request.

   2.  Enhancement Request:
        CQ26272 Add TX and RX Tunable Parameters to 
        OEM NDIS Installation INF files. 
      Cause:
        OEM Device support enhancement requested.
      Change:
        Added TX and RX Tunable Parameters to 
        OEM NDIS Installation INF files. 
      Impact:
        Resolve CQ26272 Enhancement Request.

   3.  Enhancement Request:
        CQ26516 Changes to OEM NDIS 5.1 x32 and 
        x64 Installation INF files requested. 
      Cause:
        OEM Device support enhancement requested.
      Change:
        Edited and added the OEM Device support 
        enhancements that were requested.
      Impact:
        Resolve CQ26516 Enhancement Request.

   5.  Enhancement Request:
        CQ26538 Add three PCI 4 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added three new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ26538 Enhancement Request.

   4.  Enhancement Request:
        CQ26529 Add support for five PCI 4 part Device IDs in
        Broadcom INF install support files.
      Cause:
        New Device support requested.
      Change:
        Added five new 4 Part PCI IDs to Broadcom INF
        install support files. 
      Impact:
        Resolve CQ26529 Enhancement Request.

   6.  Enhancement Request:
        CQ26536 Add support for one PCI 4 part Device ID
        in Broadcom INF install support files.
      Cause:
        New Device support requested.
      Change:
        Added one new 4 Part PCI ID to Broadcom INF
        install support files. 
      Impact:
        Resolve CQ26536 Enhancement Request.

   7.  Problem:
        CQ26514 Not doing upgrades on 5704s Fiber card.
      Cause:
        When the 5704s Fiber Link was Down, the Media Type query
        reported by the NDIS Driver was not as expected Fiber type;
        and was Auto Type.
      Change:
        Changed NDIS Driver Configuration reporting to always
        return Media Type of Fiber regardless of Fiber Link Status 
        of Up or Down.
      Impact:
        Resolve CQ26514 issue.

   8.  Enhancement Request:
        CQ26482 Change OID_TCP_TASK_OFFLOAD from returning "NOT_SUPPORTED" when
        all offload options are disabled to returning a structure of all zeros.
      Change:
        Modified the NDIS driver to not return "NOT_SUPPORTED" when all offload
        options are disabled.
      Impact:
        Resolve CQ26482 issue.

   9.  Enhancement Request:
        CQ26696 Add PCI 4 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ26696 Enhancement Request.

   10. Problem:
        CQ26524 Flow Control may not function during initial link up.
      Cause:
        The ndis device driver was not properly verifying that flow
        control is being advertised on initial link up.
      Change:
        Modified the initialization code to verify that flow control
        is being advertised correctly.
      Impact:
        Resolve CQ26524 issue.

   11.  Enhancement Request:
        CQ26738 Add PCI 4 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ26738 Enhancement Request.

   12. Problem:
        CQ26317 Adjust 5906 phy vtrim as per asic team's recommendation.
      Cause:
        Request from asic team to improve ber rates.
      Change:
        Modified the initialization code to change the phy's vtrim to
        asic team's recommendation.
      Impact:
        Resolve CQ26317 issue.

Version 9.79  August 24, 2006      
----------------------------------------
   1.  Problem:
        CQ26485 DbgPrint statement was left in source code.
      Cause:
        Code with DbgPrint messages was checked in by mistake.
      Change:
        Commented out DbgPrint statement.
      Impact:
        Resolve CQ26485

Version 9.78  August 21, 2006      
----------------------------------------
   1.  Problem:
        CQ26178/CQ26316 5906 loses network connectivity running Chariot tests.
        CQ26149 5906 Fails 2c_Simultaneous and 2c_stressClient WHQL tests.
      Cause:
        The tests were submitting transmit requests that consisted of more than
        24 transmit buffers.
        The tests were submitting transmit buffers that contained fewer than 8 bytes.
      Change:
        Modified the device driver to coalesce sends with more than 24 buffers.
        Modified the device driver to coalesce sends that contained 1 byte buffers.
      Impact:
        Resolve CQ26178/CQ26149 issue.


Version 9.77  August 18, 2006      
----------------------------------------
   1.  Enhancement Request:
        Disable Device PLL Power Down.
      Cause:
        Recommendation from LSI team.
      Change:
        Modified the driver to disable Device PLL Power Down feature.
      Impact:
        Resolve CQ26371/CQ26382/CQ26403/CQ26420 issues.

   2.  Problem:
        CQ25342 -  5787M A2 LOM in new OEM System encounters PCI SERR
        during continuous sleep and wake from S4 Hibernate testing.
        This problem is observed only in the specific OEM new system in
        combination with Broadcom LAN 5787M Device.
      Cause:
        The new chip set in OEM specific system has Interrupt Sharing among
        Broadcom LOM 5787M and integrated chip set Audio Device. 
        This interrupt sharing during transitions to S4 Hibernate and Resume
        results in PCI SERR condition and the OS Blue Screens with no handler
        for this serious error condition.
      Change:
        Added Interrupt Enable and Disable flag in Broadcom NDIS Driver code.
        Also added check of Broadcom LOM Device powered down condition along
        with LOM Interrupt Disabled; so that Shared Interrupts are passed to chip
        set Audio Controller for Interrupt sharing.
      Impact:
        Resolve CQ25342 issue.



Version 9.76 B **** INF Update *****  August 17, 2006      
Same Driver Binary as Release v9.76  August 15, 2006
----------------------------------------
   1.  Enhancement Request:
        CQ26125 and CQ25620  New Updated Device Friendly names
        specified by OEM for its supported 4 Part PCI ID Devices.
      Cause:
        New friendly device name request by OEM.
      Change:
        Updated the Friendly Name for the 4 part OEM specific
        device support listed in CQ26125 and CQ25620.
      Impact:
        Resolve CQ26125 and CQ25620 Enhancement Requests.

   2.  Enhancement Request:
        CQ26257 and CQ26260 and CQ26264 New Updated Device
        Friendly names specified by OEM for its supported 2 Part 
        PCI ID Devices.
      Cause:
        New friendly device name request by OEM.
      Change:
        Updated the Friendly Name for the 2 part OEM specific
        device support listed in CQ26257 and CQ26260 and CQ26264.
      Impact:
        Resolve CQ26257 and CQ26260 and CQ26264 Enhancement Requests.

Version 9.76  August 15, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ26260  Did Not Verify for  its Friendly Name for 5787M Device
        with 4 part PCI ID for OEM.
      Cause:
        Incomplete Enhancement Request for New OEM Device support.
      Change:
        Updated the Friendly Name for the 4 part 5787M OEM specific
        device support.
      Impact:
        Resolve CQ26260 Enhancement Request. 

   2.  Problem:
        CQ26373 Poor LSO performance
      Cause:
        Changes for CQ26149 and CQ26178 was causing too many LSO transactions
        to become coalesced.
      Change:
        Modified the device driver to coalesce sends with more than 24 buffers.
      Impact:
        Resolve CQ26373 issue.

Version 9.75  August 14, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ26260  Friendly Name for add 2 Part PCI ID support
        for 5906M to OEM NDIS 5.0 and 5.1   x32 and x64 Installation
        INF Files; was not specified in the original request.
      Cause:
        Incomplete Enhancement Request for New OEM Device support.
      Change:
        Updated the Friendly Name for added 2 part PCI ID to OEM specific
        INF files.
      Impact:
        Resolve CQ26260 Enhancement Request again. 

   2.  Problem:
        CQ25580  5704s Fiber Device Fails to do WOL after S5 Shutdown
      Cause:
        Device Driver setup for WOL performed during Windows Shutdown
        was not completed as needed and prevented proper WOL from S5.
        This problem is limited to 5704s Fiber Devices.  
      Change:
        Added the required Driver setup configuration code for handling the
        setup of the Fiber Link during transition to S5 Shutdown.
      Impact:
        Resolve CQ25580 issue.

   3.  Problem:
        CQ26246 Flow control does not function on 5906.
      Cause:
        The device driver required changes to support flow control on 5906.
      Change:
        Added the required changes to 5906 phy init code to advertise flow
        control support.
      Impact:
        Resolve CQ26246 issue.

   4.  Problem:
        CQ26339  5906 and 5906M have wrong adapter description names 
        displayed in NT4.
      Cause:
        Device addition in NT4 INF file did not get new requested name.
      Change:
        Corrected the Device name string in NT4 INF file.
      Impact:
        Resolve CQ26339 issue.

   5.  Problem:
        CQ26340    5906 and 5906M have Jumbo MTU configurable parameter
        in NT4 O.S. This option should not be present.
      Cause:
        5906 and 5906M Device additions in NT4 INF file did not get the
        required Advanced Options customization needed.
      Change:
        Corrected the 5906 and 5906M Device Advanced Options.
      Impact:
        Resolve CQ26340 issue.

   6.  Problem:
        CQ26159/CQ26178 5906 Loses connectivity during Chariot test.
      Cause:
        5906 and 5906M have a 24 send buffer descriptor limit.
      Change:
        Added change to the driver to coalesce send that contain more than
        16 buffer descriptors.
      Impact:
        CQ26159 and CQ226178 still require additional driver changes.




Version 9.74 C **** INF Update *****  August 08, 2006      
Same Driver Binary as Release v9.74  July 28, 2006
----------------------------------------
   1.  Problem:
        CQ26145  Support for Devices 5906 and 5906M Missing in 9.74
        and 9.74 B Release for NT4 Driver. 
      Cause:
        New Device support for install of NT4 Driver for 5906 and 5906M
        did not get added by error.
      Change:
        Added the NT 4 Device supports for install of 5906 and 5906M
        Broadcom Devices.
      Impact:
        Resolve CQ26145 issue.

   2.  Enhancement Request:
        CQ26257 Add 2 Part PCI ID support for 5906 to OEM NDIS 5.0
        and 5.1   x32 and x64 Installation INF Files.
      Cause:
        New OEM Device support requested.
      Change:
        Added 2 part PCI ID to OEM specific INF files.
      Impact:
        Resolve CQ26257 Enhancement Request.

   3.  Enhancement Request:
        CQ26260 Add 2 Part PCI ID support for 5906M to OEM NDIS 5.0
        and 5.1   x32 and x64 Installation INF Files.
      Cause:
        New OEM Device support requested.
      Change:
        Added 2 part PCI ID to OEM specific INF files.
      Impact:
        Resolve CQ26260 Enhancement Request.

   4.  Enhancement Request:
        CQ26264 Add 2 Part PCI ID support for 5756ME to OEM NDIS 5.0
        and 5.1   x32 and x64 Installation INF Files.
      Cause:
        New OEM Device support requested.
      Change:
        Added 2 part PCI ID to OEM specific INF files.
      Impact:
        Resolve CQ26264 Enhancement Request.




Version 9.74 B **** INF Update *****  August 1, 2006      
Same Driver Binary as Release v9.74  July 28, 2006
----------------------------------------
   1.  Enhancement Request:
        CQ26125 Add support for two PCI 4 part Device IDs to OEM
        specific INF install support files.
      Cause:
        New OEM Device support requested.
      Change:
        Added two new OEM 4 Part PCI IDs to OEM specific INF
        install support files. 
      Impact:
        Resolve CQ26125 Enhancement Request.



Version 9.74  July 28, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ25695 Add PCI 4 part Device ID for OEM project did not
        verify for AMD64 Installation INF file.
      Cause:
        New OEM Device support requested for AMD64 had incomplete
        OEM advanced option setting.
      Change:
        Corrected AMD64 installation INF file for OEM advanced options.
      Impact:
        Resolve CQ25695 Enhancement Request that did not verify.

   2.  Problem:
        CQ26011  XP32 and AMD64 Installation INF files for OEM should
        have matching Advanced Option Parameters.
      Cause:
        The original OEM Advanced Options request did not have detailed
        specifications and now it has been updated.
      Change:
        Corrected AMD64 and XP32 installation INF files for OEM 
        Advanced Options as detailed in OEM request.
      Impact:
        Resolve CQ26011.

   3.  Enhancement Request:
        CQ26098 Enable clkreq for 5755M, 5754M and 5787M.
      Cause:
        New product feature.
      Change:
        Enabled clkreq and pll power down feature.
      Impact:
        Resolve CQ26098 Enhancement Request.

   3.  Problem:
        CQ25849/CQ26645 5906 fails to connect when forcing link speeds.
      Cause:
        When link speed is forced, auto MDIX is not enabled.
      Change:
        Modified 5906 phy init code to force auto MDIX.
      Impact:
        Resolve CQ25849.



Version 9.73  July 21, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ25620-Updated:  Add 2 new OEM 4 Part PCI IDs to AMD64
        OEM specific installation INF file.
      Cause:
        Change in Enhancement Request details requested by OEM.
      Change:
        Added two new OEM 4 Part PCI IDs to OEM specific AMD64 INF
        install support files. 
      Impact:
        Resolve CQ25620 Updated Enhancement Request.



Version 9.72  July 19, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ25620 Remove OEM 4 Part PCI ID Support from
        Broadcom INF files and add them to OEM specific INF
        install support files. 
      Cause:
        Change in Enhancement Request details requested by OEM.
      Change:
        Removed OEM 4 Part PCI ID Support from Broadcom INF
        files and added them to OEM specific INF install support files. 
      Impact:
        Resolve CQ25620 Enhancement Request.

   2.  Problem:
        CQ25839 when the driver is unloaded/loaded on 5906, the controller
        links at 10mb.
      Cause:
        The ndis device driver was not properly configuring the phy for
        low power mode.
      Change:
        Corrected the ndis driver to put the phy into iddq state when wake on
        lan is not enabled.
      Impact:
        Resolve CQ25839

   3.  Enhancement Request:
        CQ25695 Add PCI 4 part Device ID for OEM project. 
      Cause:
        New OEM Device support requested.
      Change:
        Added new 4 part OEM PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ25695 Enhancement Request.

   4.  Problem:
        CQ25849 5906 fails to connect when forcing link speeds.
      Cause:
        New support for 5906 phy was required to support forced link speeds.
      Change:
        Added code to properly configure 5906 phy for forced link speeds and forced
        autoneg link speeds.
      Impact:
        Resolve CQ25849

   5.  Problem:
        CQ24950 Unable to pass traffic during driver load/unload test when connected
        to Cisco 6506.
      Cause:
        The adapter occasionally requires more than 4 seconds to acquire link when
        connected to this switch. Waiting more than 4 seconds to indicate link status
        causes the Microsoft packet scheduler to hang and not pass traffic.
      Change:
        Modified the ndis driver to not wait for than 3.8 seconds to indicate link status.
      Impact:
        Resolve CQ24950

Version 9.71  July 10, 2006      
----------------------------------------
   1.  Problem:
        CQ25115, CQ24126  ASF firmware may read incorrect data from internal
        registers under heavy traffic.
      Cause:
        A fix for a hardware errata was not enabled by the device driver.
      Change:
        Corrected the ndis driver to enable the fix for the hardware errata.
      Impact:
        Resolve CQ25115, CQ24126

   2.  Problem:
        CQ25701, CQ25701 5906 gets NMI when going into S4/S5.
      Cause:
        An errata on the 5906 causes the device to not complete a indirect
        memory read to a undefined memory location on the device.
      Change:
        Removed references to the undefined memory location on the device.
      Impact:
        Resolve CQ25701

   3.  Problem:
        CQ25729, Incorrect nvram checksum in Winfwupg on 5755 using 45DB021B.
      Cause:
        A fix for CQ25020/CQ25382 introduced a problem on 5755.
      Change:
        Corrected the ndis driver to handle this memory type properly.
      Impact:
        Resolve CQ25729

Version 9.70  June 30, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ24351 Add PCI 2 part Device ID for 5755-ME 
        support.
      Cause:
        New Broadcom Device support requested.
      Change:
        Added new 2 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24351 Enhancement Request.

   2.  Enhancement Request:
        CQ24352 Add PCI 2 part Device ID for 5906
        and 5906M product support.
      Cause:
        Two new Broadcom Device support requested.
      Change:
        Added two new 2 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24352 Enhancement Request.

   3.  Problem:
        CQ25292   5701  High Percent Processor Usage in Interrupt Time 
        when in  AMD64  platform.
      Cause:
        Memory Coherency issue prevented driver from disabling Interrupts
        as part of its procedure to process DPC operations.
        This problem is only applicable to AMD64 platforms.
      Change:
        Apply Windows DDK recommended macro  KeMemoryBarrier() to
        Driver Register Writes and Register Reads done while in the
        Interrupt Service Routine; so that all memory operations are
        coherent and completed.  The normal Driver Register Writes and
        Reads (not in the Interrupt context) were already using the
        KeMemoryBarrier() macro in their definition.
      Impact:
        Resolve CQ25292 issue.

   4.  Problem:
        CQ25020 Unable to modify nvram when 5714 or 5715 is using 45DB011B flash.
        CQ25382 Unable to upgrade bootcode on 5751 using eeprom.
      Cause:
        The ndis driver did not recognize this memory type.
      Change:
        Corrected the ndis driver to handle this memory type properly.
      Impact:
        Resolve CQ25292, CQ25382 issue.

   5.  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.


   6.  Enhancement Request:
        CQ25620 Add new PCI Four Part Device IDs for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new Four Part PCI IDs to be supported in NDIS INF files.
      Impact:
        Resolve CQ25620 Enhancement Request.



Version 9.52  May 10, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ24107 Add new Device ID for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24107 Enhancement Request.

   2.  Enhancement Request:
        CQ24401 Add new 5787M Device ID for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new 5787M PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24401 Enhancement Request.

   3.  Problem:
        CQ24390 Incorrect adapter name displayed for 5786 
        in Win98/ME installation.
      Cause:
        An edit error caused the wrong adapter name to be listed.
      Change:
        Corrected the 5786 Adapter name for Win98/ME install file.
      Impact:
        Resolve CQ24390 issue.

   4.  Enhancement Request:
        CQ24525 Difficulty acquiring 1000T link when link partner jitter
        is above IEEE limit on 5755 and 5787 controllers.
      Cause:
        Enhancement request to improve compatibility with out of
        specification link partners.
      Change:
        Added workaround to phy reset code. 
      Impact:
        Resolve CQ24525 issue.

   5.  Enhancement Request:
        CQ24520 Add support for ASF firmware to detect if the Ndis driver
        is present.
      Cause:
        Enhancement to support new ASF firmware requirement.
      Change:
        Added support for NICDRV_DRV_IDLE_TIME_CHANGE command to ASF
        firmware.
      Impact:
        Resolve CQ24520 issue.

   6.  Enhancement Request:
        CQ24584 Add new Device ID for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24584 Enhancement Request.

   7.  Problem:
        CQ24316 When a system is continually reboooted, and a 5721 device
        is physically connected to a Cisco Catalyst 6500 switch, and the
        link speed and duplex is forced to 100mb FDX, the driver may
        very intermittently believe that link is down, even when it is up.  
        This results in no network connectivity.  This problem is hard to 
                reproduce (it could take many hours, or even days, of reboots).
      Cause:
        Intermittently when connected to this Cisco switch, the link will 
        "bounce" (it will go down->up->down->up in rapid succession) 
        instead of just going "up".  If the timing of the link bounce meets
        a very narrow window of vulnerability (it must go down->up->down->up
        all in the span of a few milliseconds), the driver may "miss" the 
        interrupt for the final link up indication. This results in the 
        driver thinking that link is down instead of up, and this in turn
        results in no network connectivity since the OS protocols think that
        link is down.
      Change:
        Modified the code in the driver that checks the link state to close 
        the narrow window of vulnerability.  If the driver detects a link
        "bounce", it will re-call a certain initialization routine to ensure
        that the driver doesn't miss the final link up indication after a link
        bounce.
      Impact:
        Resolve CQ24316 issue.  There should be no negative side-effect of this
                change.

   8.  Enhancement Request:
        CQ24691  Add Two PCI 4 Part Device ID for OEM Projects.
      Cause:
        Two new OEM Device support requested.
      Change:
        Added two new 4 part PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24691 Enhancement Request.

   9.  Enhancement Request:
        Improve power savings for CQ23438.
      Change:
        Modified driver code to enable power down of the GPHY DLL and modify
        read dma thresholds when link is not present.
      Impact:
        Power consumption will be lower than versiion 9.50 when link
        is down.



Version 9.51  April 05, 2006      
----------------------------------------
   1.  Enhancement Request:
        CQ23713 Add new 5789 device ID's for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23713 Enhancement Request.

   2.  Enhancement Request:
        CQ23712 Add new 5789 device ID's for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23712 Enhancement Request.

  3.  Problem:
        CQ23560 Device ID in INF for OEM 4 Part ID support not 
        as expected.
      Cause:
        An edit error caused the wrong OEM ID to be listed.
        The correction in v9.51 was for the device friendly name.
      Change:
        Corrected the specified OEM 4 Part Device ID for correct installation.
      Impact:
        Resolve CQ23560 issue.

  4.  Problem:
        CQ23583 The add of two new 5755 Device ID's to support
        OEM customer in Broadcom generic and OEM specific
        INF install files in v9.50 was missing the OEM NT4 Install
        file support.
      Cause:
        The NT 4 OEM specific install file did not get requested new ID.
      Change:
        Added the missing new PCI ID support in OEM NT NDIS INF file.
      Impact:
        Resolve CQ23583 issue.

  5.  Problem:
        CQ23581 The add of new 5755 Device ID's to support
        OEM customer in Broadcom generic and OEM specific
        INF install files in v9.50 was missing the OEM NT4 Install
        file support.
      Cause:
        The NT 4 OEM specific install file did not get requested new ID.
      Change:
        Added the missing new PCI ID support in OEM NT NDIS INF file.
      Impact:
        Resolve CQ23581 issue.

  6.  Problem:
        CQ24080 Device 5786 Two part device ID is missing from 
        Windows2000 INF file. 
      Cause:
        The add of new 5786 2 Part ID was not complete for Win2000.
      Change:
        Added new 5786 2 Part ID  for Windows2000 INF file.
      Impact:
        Resolve CQ24080 issue.

   7.  Enhancement Request:
        CQ24099 Add new 5755 device ID's for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24099 Enhancement Request.

   8.  Enhancement Request:
        CQ24104 Change ASIC usage from 5787 to 5755, 
        4 part PCI ID match checking change required for OEM
      Cause:
        OEM decision to change from 5787 to 5755 Device.
      Change:
        Updated 4 part PCI ID for OEM.
      Impact:
        Resolve CQ24104 issue.

   9.  Enhancement Request:
        CQ24189, CQ24190, and CQ24192 Add new 5788  
        Device IDs for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24189, CQ24190, and CQ24192 Enhancement
        Requests.

   10.  Enhancement Request:
        CQ24186 Add new 5786  Device ID for OEM customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ24186 Enhancement Request.

The following changes #11 to #14 were part of Release v9.51;
but the initial release notes did not reflect them:

   11.  Problem:
        CQ23743 Unable to read/write AT45DB041B on 5787/5754/5755.
      Cause:
        Fix and code cleanup for CQ22619 inadvertently broke support
        for AT45DB041 on 5787/5754/5755.
      Change:
        Corrected driver to handle AT45DB041 properly on 5787/5754/5755.
      Impact:
        Resolve issue.

   12.  Problem:
        CQ22380 OID_PNP_SET_POWER waits for link up when it should return 
        NDIS_STATUS_PENDING.
      Cause:
        Original implementation waited for link before completing
        OID_PNP_SET_POWER.
      Change:
        Modified Driver to return NDIS_STATUS_PENDING and to use a timer to
        complete OID_PNP_SET_POWER asynchronously once link has been established.
      Impact:
        Resolve issue.

   13.  Problem:
        CQ23855 5714S doesn't reconnect to the network after running the BACS
        diagnostics.
      Cause:
        A code change that should have only been applied for Netware driver was
        also applied to the Ndis driver.
      Change:
        Added a conditional compile directive to the code that applies to Netware.
      Impact:
        Resolve CQ23855 issue.

   14.  Problem:
        CQ23877 BACS doesn't display the "Firmware Version" correctly.
      Cause:
        Fix for CQ22619 inadvertently introduced a problem where flash memory types
        were not being read properly on 5703/5704/5705/5750 controllers.
      Change:
        Corrected the code to handle flash devices proper on affected controllers.
      Impact:
        Resolve CQ22619 issue.



Version 9.50  March 21, 2006      
----------------------------------------
  1.  Problem:
        CQ23438 System with 5752M fails to get DHCP address on boot
        if LAN cable was disconnected during OS boot and later 
        connected after user log on to Windows.
      Cause:
        A non recoverable Read DMA error occurs in this test scenario, 
        due to NIC's internal core clock being automatically slowed down
        by logic in the device when the GPHY DLL is  automatically powered
        down when CAT 5 cable is disconnected.
        The GPHY DLL automatically gets powered down and NIC's internal
        core clock gets slowed down when the CAT 5 cable disconnected, 
        this is an intended design power saving feature.
        Unfortunately, the slowed down of the core-clock causes Read DMA 
        error, which resulted in the system failed to acquire the IP address
        via DHCP.
      Change:
        Modified driver code to Not  Enable the GPHY DLL Auto-Power-Down
        feature of hardware for 5752M Devices.
      Impact:
        Higher power consumption on these devices when the device is
        enabled, but the network link is down.
        Resolve CQ23438 issue.

  2.  Problem:
        CQ23551 Disable GPHY DLL power-down on 5752M, 5754M, 
        5755M, and 5787M Devices.
      Cause:
        Same problem as CQ23438 would occur for the listed devices.
        A non recoverable Read DMA error occurs in this test scenario, 
        due to NIC's internal core clock being automatically slowed down
        by logic in the device when the GPHY DLL is  automatically powered
        down when CAT 5 cable is disconnected.
        The GPHY DLL automatically gets powered down and NIC's internal
        core clock gets slowed down when the CAT 5 cable disconnected, 
        this is an intended design power saving feature.
        Unfortunately, the slowed down of the core-clock causes Read DMA 
        error, which resulted in the system failed to acquire the IP address
        via DHCP.
      Change:
        Modified driver code to Not Enable the GPHY DLL Auto-Power-Down
        feature of hardware for all  5752M, 5754M, 5755M, 5787M Devices.
      Impact:
        Higher power consumption on these devices when the device is
        enabled, but the network link is down.
        Resolve CQ23551 issue.

  3.  Problem:
        CQ23560 Incorrect device ID in INF for OEM 4 Part ID support.
      Cause:
        An edit error caused the wrong OEM ID to be listed.
      Change:
        Corrected the specified OEM 4 Part Device ID for correct installation.
      Impact:
        Resolve CQ23560 issue.

   4.  Enhancement Request:
        CQ23575 Add two new 5715S device ID's to support
        OEM server customer.
      Cause:
        Two new OEM project IDs requested.
      Change:
        Added two new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23575 Enhancement Request.

   5.  Enhancement Request:
        CQ23576 Add new 5788M device ID's for OEM mobile customer.
      Cause:
        New OEM project IDs requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23576 Enhancement Request.

  6.  Enhancement Request:
       CQ23663  Add  Fiber WOL support to OEM Fiber 4 Part ID.
      Cause:
        OEM request to add Fiber WOL feature.
      Change:
        Added Fiber WOL support to OEM 4 part PCI Device ID.
      Impact:
        Resolve CQ23663 Enhancement Request.

  7.  Problem:
        CQ23647 5714S - Cable Disconnect/Connect Test fails
        and is not able to resume network activity.
      Cause:
        Earlier fix for "CQ22620 Link LED stays on 5714S/5715S devices"
        did an unconditional PHY Reset to bring the PHY out of Low
        Power Mode. However this would cause a 5714S that was not
        in Low Power Mode to lose connectivity and not get Link connection.
      Change:
        Added driver code to Read PHY Power Mode and only assert 
        PHY Reset if the PHY is in actual Low Power Mode. So that 
        normal cable connect and disconnect events do not trigger
        Serdes PHY Reset operation.
      Impact:
        Resolve CQ23647 issue.

  8.  Problem:
        CQ23703 5701 does not link at correct speed after changing adapter
        properties.
      Cause:
        Fix for CQ23647 was applied to all devices when it should have only
        been applied to serdes devices.
      Change:
        Modified fix for CQ23647 to only apply to serdes devices.
      Impact:
        Resolve CQ23703 issue.

  9.  Problem:
        CQ23798 Wake from ping doesn't work after running 2m_WOLPattern script. 
      Cause:
        A bug in the device driver did not remove WOL test patterns from test
        script which was causing the regular WOL patterns from the OS to be
        rejected.
      Change:
        Corrected driver to remove WOL properly.
      Impact:
        Resolve CQ23798.

  10.  Enhancement Request:
        CQ23583 Add two new 5755 Device ID's to support
        OEM customer in Broadcom generic and OEM specific
        INF install files.
      Cause:
        Two new OEM project IDs requested.
      Change:
        Added two new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23583 Enhancement Request.

  11.  Enhancement Request:
        CQ23581 Add new 5755 Device ID to support
        OEM customer in Broadcom generic and OEM specific
        INF install files.
      Cause:
        OEM project ID requested.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23581 Enhancement Request.

   12.  Enhancement Request:
        Add new 5786  Two part Device ID to Broadcom
        generic install INF files.
      Cause:
        New Broadcom Device support requested.
      Change:
        Added 2 part PCI ID support for 5786 in NDIS INF files.
      Impact:
        Resolve Enhancement Request.



Version 9.19 February 27, 2006
----------------------------------------
  1.  Problem:
        CQ22619 Unable to set NWay Power Saving in nvram.
      Cause:
        Implementation for support of STM45PE10 and STM45PE20
        on 5752 controllers was incorrect.
      Change:
        Corrected support for STM45PE10 and STM45PE20 on 5752.
      Impact:
        Resolve CQ22619 issue.

  2.  Problem:
        CQ23349 5704 BSOD on NdisTest 1c_FaultHandling
      Cause:
        The Ndis driver was acquiring a spinlock from a pageable routine.
      Change:
        Wrapped the spinlock routine in a seperate non-pageable routine.
      Impact:
        Resolve CQ23349 issue.



Version 9.18 February 22, 2006
----------------------------------------
  1.  Enhancement Request:
        CQ22977  Remove unused or duplicate INF Registry
        for OEM specific Setup.
      Cause:
        Some OEM unused Registry setup was present in install
        OEM specific INF Files.
      Change:
        Removed unused and duplicate  Registry setup from 
        install OEM specific INF files.
      Impact:
        Resolve CQ22977 Enhancement Request for OEM.

  2.  Enhancement Request:
        CQ23213 Remove REV_A2 Distinction and 
        Limited WOL Settings for 5714/5715 from INF files.
      Cause:
        Chip version REV_A2 of 5714/5715 had limited 
        WOL Registry Settings to show limited WOL options.
      Change:
        Removed REV_A2 specific handling of 5714/5715
        devices as well as the limited WOL Registry setup.
      Impact:
        5714 and 5715 REV_A2 Hardware chip version
        will not support Interesting Pattern WOL operations.
        Resolve CQ23213 Enhancement Request.

  3.  Problem:
        CQ23271 Drivers for v9.17 Release do not load
        for Win98 and WinMe Operating Systems on the 
        following devices 5754, 5754M, 5755, 5755M,
        and 5787.
      Cause:
        New devices supported were not added to Win98 and
        WinMe INF files in prior release.
      Change:
        Added the new devices supported in  Win98 and
        WinMe INF files.
      Impact:
        Resolve CQ23271 issue.

  4.  Problem:
        CQ22477 Earlier Enhancement Request for NDIS small
        Packets less that 14 bytes; did not get expected results.
      Cause:
        Driver handling of very small packets was not as required
        for all combinations of Serialized and Deserialized Miniport
        Driver implementations as guided by Windows NDIS DDK.
      Change:
        Added driver code to handle Serialized and Deserialized 
        miniport drivers accordingly per Windows NDIS DDK.
      Impact:
        Resolve CQ22477 issue.

  5.  Enhancement Request:
        CQ23332  Add 4 part PCI ID support for new OEM project.
      Cause:
        Two new OEM project IDs requested.
      Change:
        Added two new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ23332 Enhancement Request.




Version 9.17 February 10, 2006
----------------------------------------
  1.  Enhancement Request:
        CQ22946  Add 4 part PCI ID support for new OEM project.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ22946 Enhancement Request.

  2.  Problem:
        CQ22952  Wrong service name in AMD64 INF (x64) for OEM product.
      Cause:
        There was an error in device service name for OEM product.
      Change:
        Corrected the device service name for OEM product.
      Impact:
        Resolve CQ22952 issue.

  3.  Enhancement Request:
        CQ22956  Add 4 part PCI ID support for new OEM project.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ22956 Enhancement Request.

  4.  Enhancement Request:
        CQ22977  Remove unused or duplicate INF Registry Setup.
      Cause:
        Some unused Registry setup was present in install
        INF Files.
      Change:
        Removed unused and duplicate  Registry setup from 
        install INF files.
      Impact:
        Resolve CQ22977 Enhancement Request.

  5.  Problem:
        CQ23008 Need to set bit 15, and clear bit 14 of DMA 
        Control Register offset 0x6c on 5714, and 5715 devices.
      Cause:
        Device initialization detail recommended by Hardware team.
      Change:
        Modified driver initialization of 5714, and 5715 devices
        to set Bit_15 and clear Bit_14 of DMA Control Register.
      Impact:
        Resolve CQ23008 issue.

  6.  Enhancement Request:
        CQ23049 Friendly name pointers for Stanford Device IDs
        are incorrect in v9.16 INF file. 
      Cause:
        The friendly name was displaying correctly to the user;
        but inside the INF file the device name string call was not
        matching actual identified device.
      Change:
        Edited the INF file to use proper matching string call for
        the Stanford device.
      Impact:
        Resolve CQ23049 Enhancement Request.

  7.  Enhancement Request:
        CQ23125 OEM Device Friendly Name and Advanced
        Options Needs Update in v9.16 INF file. 
      Cause:
        OEM Requested update to friendly name displayed and
        an update to Advanced Options Listed for OEM Devices.
      Change:
        Edited the INF file to show updated name and options
        for OEM Devices requested.
      Impact:
        Resolve CQ23125 Enhancement Request.

  8.  Problem:
        CQ13853 Slow performance on NT4 SP6a when linked at 10mb.
      Cause:
        When the controller is using the slow core clock, the
        interrupt coalescing registers are slower by a factor of 10.
        This was causing interrupts to be excessively delayed.
      Change:
        Modified the driver to properly program the interrupt
        coalescing registers by dividing the registers by 10 when
        the controller is clocked by the slow core clock.
      Impact:
        Resolve CQ13853 issue.


Version 9.16 January 27, 2006
----------------------------------------
  1.  Enhancement Request:
        CQ22446 Add Interesting Packet WOL Support to 5714 and 
        5715 chip version A3 and later in installation INF files.
      Cause:
        The 5714 and 5715 versions A3 and later can support Interesting Pattern WOL.
      Change:
        Enabled Interesting Pattern WOL for 5714 and 5715 for A3 and greater
        versions in installation INF files.
      Impact:
        Resolve Enhancement Request.

  2. 
      Enhancement Request:
         CQ22620 Link LED stays on 5714S/5715S devices.
      Cause:
         New feature request to power down the serdes on 5714S/5715S.
      Change:
         Modified driver unload/init code and suspend/resume code to
         power down the serdes when the device should be in low power
         state and reset the serdes when the device is on operational
         state.
      Impact:
         None

Version 9.15 January 23, 2006
----------------------------------------
  1.  Enhancement Request:
        CQ22881 Unable to enable ASF on 5787/5754.
      Cause:
        New nvram support for 5787/5754.
      Change:
        Added code to support 5787/5754 nvram types.
      Impact:
        Resolve CQ22881 Enhancement Request.

Version 9.14 January 21, 2006
----------------------------------------
  1.  Enhancement Request:
        CQ22477 The ndis driver does not reject illegal transmit packets.
      Cause:
        New enhancement request.
      Change:
        Added check to send routine to fail transmit requests that are
        smaller than 14 bytes.
      Impact:
        Resolve CQ22477 Enhancement Request.

  2.  Enhancement Request:
        CQ22696 Need to reduce the length of OEM friendly names
        for some devices.
      Cause:
        OEM Request to reduce name displayed.
      Change:
        Edited OEM device display names.
      Impact:
        Resolve CQ22696 Enhancement Request.

  3. 
      Problem:
         ECD13216 Implement ECD13216 for 5714S/5715S link detection problem.
      Cause:
         Hardware errata on 5714S/5715S
      Change:
         Modified init code to enable configuration bits to enable
         fix for ECD13216 in hardware.
         Modified link status code to read link status from tx status
         register.
      Impact:
         None

  4. 
      Problem:
         CQ22692, CQ22801 Unable to set ASF IP address on 5755.
      Cause:
         The ndis driver needed to be update to include support
         for new 5755 memory devices.
      Change:
         Modified the ndis driver to properly support memory
         devices.
      Impact:
         None


Version 9.13 January 05, 2006
----------------------------------------
  1.  Enhancement Request:
        CQ22182  Add 4 part PCI ID support for new OEM project.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ22182 Enhancement Request.

  2.  Enhancement Request:
        CQ22183  Add 4 part PCI ID support for new OEM projects.
      Cause:
        New OEM projects.
      Change:
        Added two new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ22183 Enhancement Request.

  3.  Enhancement Request:
        Add support for new 5755 NVRAM types.
      Cause:
      Change:
        Added code to recognize 264 byte NVRAM page sizes for unbuffered
        memory.
      Impact:
        All 5755 NVRAM types should be fully supported by the ndis driver.

  4.  Enhancement Request:
        CQ22159  Add 4 part PCI ID support for new OEM project.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ22159 Enhancement Request.

  5.  Enhancement Request:
        CQ22534  Add 4 part PCI ID support for new OEM project.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in NDIS INF files.
      Impact:
        Resolve CQ22534 Enhancement Request.

  6.  Enhancement Request:
        CQ14560 - Coalesce transmit packet headers for better bus
                  utilization.
      Cause:
        Enhancement Request.
      Change:
        Added code to coalesce transmit packet headers fragments into
        one buffer fragment.
      Impact:
        Resolve CQ14560 Enhancement Request.

   7. 
      Problem:
         CQ22181 UMP: Host traffics on port with UMP enabled in a SLB 
         team are lost
      Cause:
         The miniport is changing all 4 MAC entries when requested to 
         change the MAC address. IPMI and UMP use the second and third 
         entries.
      Change:
         Only modify the first MAC entry when the teaming software 
         requests a MAC address change.
      Impact:
         None

   8. 
      Problem:
         5754M/5787M/5755M Does not shut down the phy dll when the link
         is not present.
      Cause:
         The driver did not configure the phy dll properly on the affected
         parts.
      Change:
         Modified the driver to configure the phy dll on the affected parts
         to shutdown.
      Impact:
         None

   9. 
      Problem:
         5754M/5755M Does not use the slow core clock when linked at 10mb.
      Cause:
         The driver did not configure the controller properly when linked at
         10mb.
      Change:
         Modified the driver to slow the core clock when linked at 10mb.
      Impact:
         None


Version 9.12 November 21, 2005
----------------------------------------
  1.  Enhancement Request:
        CQ14588 Add new PCI ID support OEM mobile customer.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in OEM installation INF file.
      Impact:
        Resolve CQ14588 Enhancement Request.

  2.  Enhancement Request:
        Improve handling of statistic OIDs while device is 
        in Low Power Mode.
      Cause:
        New WHQL test case putting device into Low Power mode
        and then issue statistics query OIDs.
      Change:
        Added check and reject of statistic OIDs while device is
        in Low Power Mode.
      Impact:
        Resolve handling of statistic OIDs Enhancement Request.

  3.  Enhancement Request:
        Improve handling of driver unloading and shutdown paths
        so that link speed is properly maintained at speeds other
        than 1 gig bits per second. 
      Cause:
        If device WOL capability is set to None and device is disabled
        and system is shutdown; the 57xx device keeps link at 1 gig.
        If device WOL capability is set to None and system is put to
        Standby mode; the 57xx device keeps link at 1 gig.
      Change:
        Modified driver source to setup the PHY with proper WOL
        speed even if WOL capability is set to None.
      Impact:
        Resolve handling of proper WOL speed Enhancement Request.

  4.  Enhancement Request:
        CQ14633 Remove comment from Device support in INF for
        AMD64 OEM 4 PCI ID match.
      Cause:
        The prior driver release had OEM 4 part PCI ID support line
        commented in AMD64 install INF file.
      Change:
        Uncomment OEM 4 part PCI ID support in AMD64 INF file.
      Impact:
        Resolve C14633 Enhancement Request.

  5.  Problem:
        CQ14616 5787M unable to pass traffic when linked at 10mb.
      Cause:
        The read dma burst mode was not programmed correctly for 5787.
      Change:
        Modified the ndis driver to program the dma burst mode correctly.
      Impact:
        Resolve CQ14616

  6.  Enhancement Request:
        CQ14643 Add new PCI ID support for OEM customer.
      Cause:
        New OEM project.
      Change:
        Added new PCI ID support in OEM installation INF file.
      Impact:
        Resolve C14643 Enhancement Request.

  7.  Enhancement Request:
        CQ14658 Add 6 new PCI ID support for OEM customer.
      Cause:
        New OEM projects.
      Change:
        Added 6 new PCI ID support in OEM installation INF file.
      Impact:
        Resolve C14658 Enhancement Request.

  8.  Enhancement Request:
        Improve NDIS5.1 Driver Shutdown handler so that it
        does not access any PCI Configuration Registers 
        when a system Bug Check is in progress.
      Cause:
        New Microsoft Vista DDK requirement.
      Change:
        Modified driver to be aware of this requirement and 
        make proper final steps in the Shutdown handler.
      Impact:
        Resolve Driver Shutdown improvement request.

  9.  Problem:
        CQ14669 5755A1 unable to wake from S1/S3/S4 when linked at 10mb.
      Cause:
        The read dma burst mode was not programmed correctly for 5755 causing
        the dma engine to hang.
      Change:
        Modified the ndis driver to program the dma burst mode correctly.
      Impact:
        Resolve CQ14669.




Version 9.11 November 04, 2005
----------------------------------------
  1.  Problem:
        CQ14461/CQ14438 5755/5787 adapters does not pass traffic in
        10mb after reboot
      Cause:
        The ndis driver was not shutting down the controller properly
        when linked at 10mb, causing the dma engines to remain enabled.
      Change:
        Modified the ndis driver to correctly shutdown the dma engines
        when linked at 10mb.
      Impact:
        Resolve CQ14461/CQ14438


Version 9.10 November 01, 2005
----------------------------------------
  1.  Problem:
        CQ14366 Self boot adapters shows invalid mac address.
      Cause:
        The ndis driver was reading the mac address from nvram on
        self boot adapters when it should read the mac address from
        shared memory.
      Change:
        Modified the ndis driver to read the mac address from nvram
        on all 5787 and 5755 family adapters.
      Impact:
        Resolve CQ14366.

  2.  Problem:
        CQ14387 5714S reports no link after resuming from standby.
      Cause:
        The ndis driver was shutting down the serdes on 5714S during
        transition to standby.
      Change:
        Modified the ndis driver to not shutdown the serdes during transition
        to low power state.
      Impact:
        Resolve CQ14387.

  3.  Problem:
        CQ14461 5755/5787 adapters does not pass traffic in 10mb after reboot.
      Cause:
        The ndis driver was resetting the device at using a slow core clock.
      Change:
        Modified the ndis driver to reset the device using the regular core clock.
      Impact:
        Resolve CQ14461.
  
  4.  Problem:
        5755/5787 adapters does not wake from interesting packet when linked
        at 10mb.
      Cause:
        The ndis driver was programming the device for interesting packet wake
        on lan using the slow core clock.
      Change:
        Modified the ndis driver to use the regular core clock when programming
        the device for interesting packet wake on lan.
      Impact:
        Resolve 10mb interesting wake on lan issue on 5755/5787.

  5.  Problem:
        Add support for 5787, 5787M, 5787F, 5754, 5754M, 5755, 5755M, 5714S
        and 5715S. 
      Cause:
        Requirement for Release 9.0
      Change:
        Modified the ndis driver to recognize the affected devices.
        Modified the inf files to recognize the affected devices.
      Impact:
        Affected devices are now supported.

  6.  Enhancement Request:
        CQ14439 Add 4 ID device match for new OEM projects.
      Cause:
        New 4 ID device match support requests by OEM.
      Change:
        Added new 4 ID device matches for OEM project.
      Impact:
        Resolve CQ14439 Enhancement Request.  



Version 8.48D October 26, 2005 - INF Update only
----------------------------------------
  1.  Problem:
        CQ14446 - Remove Interesting Packet Wake On Lan support
        on 5714 and 5715 copper devices.
      Cause:
        An incorrect default value was being used in the inf file
        that was inadvertently enabling interesting packet Wake On
        Lan.
      Change:
        Modified inf file entries for the affected devices to 
        default to only support magic packet wakeup.
      Impact:
        Resolve CQ14446


Version 8.48C October 24, 2005 - INF Update only
----------------------------------------
  1.  Problem:
        CQ14446 - Remove Interesting Packet Wake On Lan support
        on 5714 and 5715 copper
        devices.
      Cause:
        Interesting packet Wake On Lan is not supported on 5714 copper
        and 5715 copper.
      Change:
        Modified inf file entries for the affected devices to only
        support magic packet wakeup.
      Impact:
        Resolve CQ14446

  2.  Problem:
        CQ14448 - Remove unsupported devices in b57amd64.inf and oemsetup.inf
      Cause:
        Earlier change to remove support for 5787, 5787M,
        5787F, 5754, 5754M, 5755, 5755M, 5714S, and 5715S were
        not implemented in b57amd64.inf and oemsetup.inf due to
        a build error.
      Change:
        Removed inf file entries for the affected devices.
        Updated the device driver to not recognize the affected
        devices.
      Impact:
        The mentioned devices are not supported in by the Ndis
        driver until release Project 9.0

Version 8.48B October 21, 2005 - INF Update only
----------------------------------------
  1.  Problem:
        CQ14446 - Remove Wake On Lan support on 5714 and 5715 copper
        devices.
      Cause:
        Wake On Lan is not supported on 5714 and 5715 copper.
      Change:
        Removed WOL inf file entries for the affected devices.
      Impact:
        Resolve CQ14446

  2.  Problem:
        CQ14447 - Remove unsupported devices in b57amd64.inf.
      Cause:
        Earlier change to remove support for 5787, 5787M,
        5787F, 5754, 5754M, 5755, 5755M, 5714S, and 5715S were
        not implemented in b57amd64.inf.
      Change:
        Removed inf file entries for the affected devices.
        Updated the device driver to not recognize the affected
        devices.
      Impact:
        The mentioned devices are not supported in by the Ndis
        driver until release Project 9.0


Version 8.48  October 17, 2005      
----------------------------------------
  1.  Problem:
        Remove support for the following unreleased controllers:
        5787, 5787M, 5787F, 5754, 5754M, 5755, 5755M, 5714S, 5715S
      Cause:
        The controllers are not supported in release Project 8.3
      Change:
        Removed inf file entries for the affected devices.
        Updated the device driver to not recognize the affected
        devices.
      Impact:
        The mentioned devices are not supported in the Ndis
        driver until release Project 9.0


Version 8.47  October 13, 2005      
----------------------------------------
  1.  Problem:
        CQ14269  5750 Shasta Traffic LED behavior is different
        from expected default when the Windows device driver
        is loaded.
      Cause:
        Windows NDIS Driver v8.46 and earlier did not set the 
        required LED controls during 5750 Shasta Device 
        initialization.         
      Change:
        Updated Windows NDIS Driver to set the proper LED
        control bits, so that the expected LED behavior is seen.
      Impact:
        Resolve CQ14269 issue.  

  2.  Problem:
        CQ13867  Firmware corruption when upgrading the firmware
        on 5714 with ST M45PE10 flash.
      Cause:
        The windows NDIS Driver was not programming the nvram
        config3 register properly.
      Change:
        Updated the NDIS Driver to change the write command
        byte from 0x02 to 0x0a as per ST M45PE10 datasheet.
      Impact:
        Resolve CQ13867.

  3.  Enhancement Request:
        CQ14334 Switch OEM 4 part PCI ID SubSystem Device ID to 0x2020 
      Cause:
        Change of SDID request by OEM for new project.
      Change:
        Modified  4 part PCI ID device match for OEM project.
      Impact:
        Resolve CQ14334 Enhancement Request.  

  4.  Enhancement Request:
        CQ14335 Please remove OEM recently added 4 part PCI ID. 
      Cause:
        Change request by OEM.
      Change:
        Removed requested 4 part PCI ID device match for OEM project.
      Impact:
        Resolve CQ14335 Enhancement Request.  



Version 8.46  October 04, 2005      
----------------------------------------
  1.  Enhancement Request:
        CQ14196 and CQ 14197 Add 4 ID device match for new OEM projects.
      Cause:
        New 4 ID device match support requests by OEM.
      Change:
        Added new 4 ID device matches for OEM project.
      Impact:
        Resolve CQ14196/14197 Enhancement Request.  

  2.  Problem:
        The driver could enable the interesting packet WoL bit 
        when the driver was disabled (halted) and ASF/IPMI was also
        disabled. On 5705 and later devices, when this bit is enabled,
        a portion of internal memory in the device (misc_bd region)
        is not accessible to the host driver or FW.  This in turn
        could lead to a faulty driver/FW handshake when the driver was
        re-enabled, and under very rare circumstances the faulty
        handshake could lead to GPHY register corruption, which in
        turn could lead to the GPHY being set for the wrong 
        speed/duplex, or the GPHY could be configured to be in a
        non-functioning state.
      Cause:
        The driver would set the interesting packet wake-up bit when
        the driver was halted (even though there is no need to do
        this), when ASF/IPMI PT was disabled.
      Change:
        Updated Windows Driver code to only enable the interesting
        packet WoL bit when the system is going into S1/S3/S4, and not
        when the driver is disabled.
      Impact:
        There should be no side-effects from this change.

  3.  Problem:
        CQ 14030 When IPMI PT is enabled, an extra link down/up message
        pair could be logged in the Event log when a driver loads.  On
        some systems (depending on timing on the platform in question), 
        the extra link up/down events during driver load could result
        in an auto login to a domain to fail when teaming was enabled.
      Cause:
        If IPMI PT is enabled, the device will by default auto-neg to 
        10/100 only in an OS absent (driver not loaded) environment. 
        This is per design to save power (Because IPMI does not need
        a 1Gb link).  When the driver loads, it needs to modify the GPHY
        config to advertise 10/100/1000 and restart auto-neg.  Although
        the driver was properly restarting auto-neg, it was not
        clearing the "pDevice->RestartAutoneg" in the init code before 
        indicating a link up.  Because of this, the driver was
        improperly restarting auto-neg again after a 1Gb link had been
        established with a 10/100/1000 switch  port.  This "double"
        restarting of auto-neg led to the link down/up messages in the
        event viewer, and could cause (depending on system timing) the
        netlogon failure.
      Change:
        Updated the driver code to clear the "pDevice->RestartAutoneg"
        flag in the LM_ForceAutoNegBcm540xPhy() subroutine when
        auto-neg is restarted the 1st time.
      Impact:
        There should be no side-effects from this change.

  4.  Problem:
        CQ 14031 NetLogon fails upon reboot when using a Team of 2 NICs
        when flow control is set to any value other "disabled" in the
        Windows network driver properties.  This problem is similar, 
        but not identical to CQ 14030.  As with CQ 14030, when this 
        problem occurs (when flow control is set to a value other than
        "disabled"), a link down/up message pair would be logged in the
        Event log when a driver loads because the driver is restarting 
        auto-neg (to modify the advertised flow control parameters)
        after it had previously indicated link up to the OS.  This
        issue will only occur if auto-negotiation is enabled.
      Cause:
        If flow control is not disabled, and if auto-neg is enabled,
        the driver will need to modify the registers in the GPHY to 
        advertise the proper flow control support, and then restart
        auto-neg.  However, the driver was doing this at the very end
        of the initialization code, after it had already indicated a 
        link-up to the OS.  Thus, from the OS perspective, the link 
        was up, and then it was dropped, and then it would go back up
        later.  This bouncing of the link could result in a netlogon
        failure if teaming was enabled because the OS was not designed
        to be tolerant of a link down/up indication during a domain
        login, and depending on the timing (which was exacerbated by
        teaming), failures with the login could occur.  Lastly, this
        problem was introduced by the fix for CQ 9033 and 9124.   
      Change:
        Updated the driver code to restart auto-neg earlier in the 
        initialization process if flow control is not disabled.  By
        doing this, the driver will not give the OS a link up
        indication until after auto-neg has completed with the new 
        GPHY Flow control advertisement settings.  By doing this, 
        the "bouncing" of link up/down/up indications to the OS is
        avoided.  
      Impact
        The fix for CQ 9033/9124 was re-done.  This new fix should
        not re-introduce CQ 9033/9124, but flow control should 
        definitely be re-tested with this new driver due to this change.

  5.  Problem:
        Intermittent BSOD when loading/unloading driver on 5755_A0.
      Cause:
        After accessing the nvram interface, other register reads
        may be corrupted causing the device driver to behave incorrectly.
        This is an errata on the 5755A0 device.        
        Earlier workaround implemented in v8.44 contained a corner case
        where the driver may clobber the Memory Arbitor register.
      Change:
        Corrected workaround implemented in v8.44 to wait for the bootcode
        to enable the Memory Arbitor.
        Corrected a corner case where the driver was sending a pause command
        to the firmware while the cpu was halted.
      Impact:
        Resolve BSOD issue on 5755_A0

                                                        
Version 8.45  September 27, 2005      
----------------------------------------
  1.  Enhancement Request:
        CQ14113 Add 4 ID device match for new OEM project.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM project.
      Impact:
        Resolve CQ14113 Enhancement Request.  

  2.  Enhancement Request:
        CQ14115 Add 4 ID device match for new OEM project.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM project.
      Impact:
        Resolve CQ14115 Enhancement Request.  

  3.  Problem:
        CQ14105 5787 Device Shows link when Wake up Capabilities
        are set to NONE and SUT is sent into sleep states S1, S3,
        and S4, and ASF is disabled.
      Cause:
        The function in the driver that put the device in a low power
        state and turn off the GPHY when WoL and ASF were disabled, was
        skipping the 5787 device for this operation.
      Change:
        Updated Windows Driver code to treat the 5787 device similar
        to other devices (such as the 5751) and correct this problem.
      Impact:
        Resolve CQ14105 issue.

 4.  Problem:
        CQ13907 BMC isn´t reachable via LAN after an invoked
        Blue Screen. System monitored would lose LAN connection
        when the OS was forced into a Blue Screen condition.
      Cause:
        Driver v8.40 Enhancement # 6 addition enabled a feature
        in the NDIS driver that was not necessary.  The feature
        involved the driver sending IPMI PT FW a "heartbeat" message,
        and the FW would reset the chip if it did not get the
        heartbeat because its watchdog timer would expire.  This
        feature was faulty in the NDIS driver because if the OS
        was extremely stressed, the driver would not be able to 
        update the heartbeat in a timely manner, and this could result
        in a false watchdog timeout assertion.  The falsely detected
        timeout would then lead to a reset, which would then cause
        multiple downstream problems including this issue.
      Change:
        Removed the NDIS Driver enabling of ASF IPMI Watch Dog
        Timer.  This feature was not needed in this driver. If a 
        BSOD were to occur, the driver's "Shutdown" routine would
        be called, and the driver would reset the HW. 
      Impact:
        Resolve CQ13907 issue.

 5.  Problem:
        CQ14121 5715-A2: Its Primary Port Becomes Non-Responsive, 
        when Four Interfaces Are Evaluated in Dell Precision 470 PAE
        based System
      Cause:
        Driver v8.40 Enhancement # 6 addition enabled a feature
        in the NDIS driver that was not necessary.  The feature
        involved the driver sending IPMI PT FW a "heartbeat" message,
        and the FW would reset the chip if it did not get the
        heartbeat because its watchdog timer would expire.  This
        feature was faulty in the NDIS driver because if the OS
        was extremely stressed, the driver would not be able to 
        update the heartbeat in a timely manner, and this could result
        in a false watchdog timeout assertion.  The falsely detected
        timeout would then lead to a reset, which would then cause
        multiple downstream problems including this issue.
      Change:
        Removed the NDIS Driver enabling of ASF IPMI Watch Dog
        Timer. 
      Impact:
        Resolve CQ14121 issue.


Version 8.44  September 20, 2005      
----------------------------------------
  1.  Enhancement Request:
        CQ14024 Add 4 ID device match for new OEM project.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM project.
      Impact:
        Resolve CQ14024 Enhancement Request.  

  2.  Enhancement Request:
        CQ14025 Add 4 ID device match for new OEM project.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM project.
      Impact:
        Resolve CQ14025 Enhancement Request.  

  3.  Problem:
        CQ13920 5714 A2 and 5715 A2 Maintains Link despite Driver
        being disabled in Windows.
      Cause:
        Revision A0 and A1 of 5714 and 5715 devices had limitations
        that prevented the NDIS Driver from powering off the GPHY in 
        one port while the other port was running and active. 
        Turning off the PHY is only applicable when ASF is Disabled
        and no WOL is expected from 5714 and 5715 devices and the
        device is being Disabled in Windows Device Manager.
      Change:
        Added 5714 and 5715 and 5780 revision aware driver code to
        properly manage PHY power when the device is being disabled
        or when system is powering down.
      Impact:
        Resolve CQ13920 issue.

  4.  Enhancement Request:
        CQ14035 Add 4 ID device match for new OEM project.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM project.
      Impact:
        Resolve CQ14035 Enhancement Request.  

  5.  Enhancement Request:
        CQ13818 Add 4 ID device match for new OEM projects.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM projects.
      Impact:
        Resolve CQ13818 Enhancement Request.  

  6.  Problem:
        CQ14056 Interesting packet wakeup does not work on 5755 and 5787.
      Cause:
        The interesting packet wakeup patterns on 5755 and 5787
        controllers are stored in a different memory location inside
        shared memory.
      Change:
        Changed the driver to store interesting packet wakeup patterns
        from offset 0x4000 to 0x8000 for 5755 and 5787.
      Impact:
        The interesting packet wakeup feature for 5755 and 5787 is working.

  7.  Problem:
        BSOD when loading/unloading the driver on 5755.
      Cause:
        After accessing the nvram interface, other register reads
        may be corrupted causing the device driver to behave incorrectly.
        This is an errata on the 5755A0 device.
      Change:
        A workaround for 5755A0 when accessing the nvram interface
        has been implemented to prevent the corruption of register reads.
      Impact:
        The workaround will cause the driver to require 2 additional
        seconds to load on 5755A0 devices.



Version 8.43  September 14, 2005      
----------------------------------------
  1.  Problem:
        CQ13948 LSO does not function on 5787/5755.
      Cause:
        A typo in the LSO code for 5787/5755 ported from the ndis6 driver.
      Change:
        Corrected typo.
      Impact:
        LSO on 5787 and 5755 is now functional.


Version 8.42  September 12, 2005      
----------------------------------------
  1.  Problem:
        CQ13941 5714s A2 (Fiber) Unable to establish Connectivity in
        Windows 32/64 bit.
      Cause:
        A Driver and Bootcode combined attempted fix for CQ13216
        did not work as expected. The change for CQ13216 was added
        to v8.40 driver and was also present in v8.41 driver.
      Change:
        Reverted NDIS Driver change for CQ13216 fix that involved 
        setting of Bit 4 in Register 0x6808 and now clear both Bits 4 and 5.
      Impact:
        Resolve CQ13941 issue.

  Enhancements:
  =============
  1. Request: 
        Add 2 part PCI ID Support for new Broadcom Device: 5903M
      Change:
        Added new PCI ID support to the XP64, XP32, AMD64, and NDIS4
        installation INF files.
      Impact:
        None.



Version 8.41  September 07, 2005      
----------------------------------------
  1.  Enhancement Request:
        CQ13816 Add 4 ID device match for new OEM project.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM project.
      Impact:
        Resolve CQ13816 Enhancement Request.  

  2.  Enhancement Request:
        CQ13817 and CQ13818 Add 4 ID device match for new OEM projects.
      Cause:
        New 4 ID device match support request by OEM.
      Change:
        Added new 4 ID device match for OEM projects.
      Impact:
        Resolve CQ13817 and CQ12818 Enhancement Requests.  

  3.  Problem:
        CQ10476 BCM5751 Shasta: Mismatched TX vs. RX Statistics counters
        during continuous file transfer operation. Fix in v8.40 did not resolve
        issue.
      Cause:
        The fix put in v8.40 relied on a general purpose timer in BCM57xx
        miniport driver that may get cancelled if network Link Up is not
        established within 3 seconds of start of initialization at boot up.
        As a result of this and getting Link Up at just over 3 seconds, the
        driver workaround of reading and refreshing the device Statistics
        periodically did not get executed at all. This resulted in v8.40 fix not
        resolving the issue of mismatched TX/RX counters after a long copy
        and compare session.
      Change:
        Modified driver to wait 6 seconds for the initial network Link Up and
        not cancel the general purpose timer used for this workaround until
        the 6 second time has expired.  
      Impact:
        Resolve CQ10476 issue.

  4.  Problem:
        CQ13764  Stress test in new Windows Vista Beta version 
        causes a watchdog timeout for b57xp32.sys driver 
        DPC (Deffered Procedure Call).   This problem is specific to
        unreleased Windows Vista Beta OS version and Beta WHQL
        HCT tests and therefore unrelated to current officially supported
        OS and WHQL Certification programs.
      Cause:
        The 57xx driver DPC code uses and invokes various NDIS
        procedure calls to get and send Transmit packets as well as
        notify the OS of arrived Receive packets. When system and NIC 
        stress conditions are produced during running of LAN Device tests;
        these calls to NDIS service routines take longer and longer to
        complete. The Windows Vista watchdog routine then flags the
        b57xp32 device driver as taking too long to finish its DPC function.
      Change:
        Added a new time limit code with default of 10 milliseconds to the
        b57xp32 device driver's DPC function, so that it returns control back
        to the OS and avoids the watchdog timer problem.
        The newly added code for DPC time limit is applicable only to NDIS 5.1
        and later versions.  The default of 10 milliseconds time limit for 
        b57xp32 DPC function can be adjusted by use of a documented
        Windows Registry parameter.
      Impact:
        Resolve CQ13764 issue.

  5.  Problem:
        CQ13873 5714/15-A2 NIC involve in BSOD for an illegal DMA operation, 
        when evaluating Jumbo Frame feature.
      Cause:
        A change for Netware driver in shared NDIS and NETWARE source file
        caused the NDIS driver to misallocate required memory for proper
        Jumbo frame operation.
        This problem was present in 57xx NDIS drivers: v8.33 thru 8.40 as 
        well as v8.39.1 and its B and C INF updates. 
      Change:
        Added a conditional compile switch in driver source file to let both NDIS
        and Netware coexist with different Jumbo frame initializations.
      Impact:
        Resolve CQ13873 issue.

  6.  Problem:
        Add support for Large Send Offload on 5755 and 5787.
      Cause:
        New hardware requirement specific to 5755 and 5787.
      Change:
        Added conditional code for 5755 and 5787 Large Send Offload
        transactions to include the Tcp/Ip Header length in the send
        buffer descriptors.
        Added a conditional compile switch in driver source file to let both NDIS
        and Netware coexist with different Jumbo frame initializations.
      Impact:
        Resolve LSO support issue on 5755 and 5787.





Version 8.40  August 25, 2005      
----------------------------------------
  1.  Problem:
        CQ10476 BCM5751 Shasta: Mismatched TX vs. RX Statistics count
        during continuous file transfer operation.
      Cause:
        Shasta Devices with PCI ID of 0x1677 have a 28 bit wide statistics
        Register limitation (as compared to 32 bits in other devices) . 
        This will lead to roll over of TX Packets sent counter after 12 hours
        of file copy and compare to a network drive that is using the
        BCM5751 device with link speed of 1 gig. 
        This roll over of TX packets sent versus RX packets received causes
        Windows show of Network Device statistics to be incorrect and the
        RX number will be much bigger. This is only a TX statistic issue and
        proper operation of the device or its driver is not compromised.
      Change:
        Added a driver workaround for BCM5751 Shasta devices that reads
        and updates all statistics before it gets rolled over.
      Impact:
        Resolve CQ10476 issue.

  2.  Enhancement Request:
        CQ13592 Add 4 ID match for new OEM project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ13592 Enhancement Request.  

  3.  Enhancement Request:
        CQ13678 5702FE should not be supported in the AMD64 INF.
      Cause:
        The 5702FE Device support in AMD64 INF installation file was a 
        left over from earlier time.
      Change:
        Removed 5702FE Device support in AMD64 INF installation file.
      Impact:
        Resolve CQ13678 Enhancement Request.  

  4.  Enhancement Request:
        CQ13693 Add 4 ID match for new OEM project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ13693 Enhancement Request.  

  5.  Enhancement Request:
        CQ13715 Mirror OEM desktop customers PCI ID's into the Broadcom 
        INF installation files.
      Cause:
        OEM request to have device support in Broadcom generic INF files.
      Change:
        Copied 4 ID device supports from OEM INF files to Broadcom INF files.
      Impact:
        Resolve CQ13715 Enhancement Request.  

  6.  Enhancement Request:
        Add support for new ASF driver keep alive message.
      Cause:
        New design requirement.
      Change:
        Added keep alive message to ASF firmware to the driver's timer
        tick routine.
      Impact:
        None.

  7.  Enhancement Request:
        CQ13720 Add multiple 4 ID matches for new OEM mobile projects.
      Cause:
        New 4 ID match support requests by OEM.
      Change:
        Added new 4 ID matches for OEM mobile projects.
      Impact:
        Resolve CQ13720 Enhancement Request.  

  8.  Enhancement Request:
        CQ13779 Program DMA Read Write Control Register on 5714/5715
      Cause:
        Errata on device.
      Change:
        Set bit 15 and clear bit 14 of dma read write control register.
      Impact:
        Resolve CQ13779 issue.

  9.  Problem:
        CQ12862. The core clock could be slowed on 5751M Ax-step devices.
      Cause:
        The driver was slowing the core clock when a 5751M family Ax-step part is
        linked at 10mb.  This could cause a performance issue with TPM if TPM were
        enabled.  This problem could only occur on mobile ("M") devices. The driver
        should only slow the core clock at 10mb with 5751 Bx-step devices.
      Change:
        Leave the core clock at regular speed when 5751M Ax device is linked
        at 10mb.
      Impact:
        Resolve CQ12862 issue.



Version 8.39  July 20, 2005      
----------------------------------------
  1.  Problem:
        It could take a 5703/4 device, or the LAN core in a 5714/5715 device 
        10ms to respond to a PCI read transaction to register 0x468 when
        WOL was disabled and the system was shutdown. This issue is related to 
        CQ 13332 issue.
      Cause:
        When WOL is disabled, and ASF/IPMI are disabled, the driver will 
        power-down the GPHY.  This turns off the clock to register 0x468 on these
        devices. This could introduce a 10ms delay if the driver later accesses    
        this register. In most cases, this delay is benign.  However, if the 
        5703/4 device is behind a upstream PCIE-PCIX bridge, the upstream device
        could have a completion timer timeout enabled.  If the upstream device
        did have such a timer, a failure could be seen that would be similar to
        CQ 12100 (which was related to the 5751 family and was already worked
        around in SW).
      Change:
        Updated driver to only write to register 0x468 in the shutdown code path if
        WOL is enabled via NVRAM setting.
      Impact:
        Works around part of CQ 13332 issue. There should be no side-effects.
 
  2.  Problem:
        When the core clock is slowed on a 5704 device, or when the core 
        clock is slowed on 5714/5715 LAN core, it could take the device up to
        10ms to respond to a PCI target read transaction. This issue is 
        related to CQ 13332.
      Cause:
        5703/4 and 5714/5715 devices have a known HW errata related to
        target read accesses that occur after the core clock has been slowed.
        The workaround of the known errata was to either read registers twice, 
        or to re-order code so such that read data would be relied upon
        after slowing the core clock.  However, this older workaround could
        still result in a 10ms delay to respond to a target read, and if the 
        5704 device is behind a upstream PCIE-PCIX bridge, the upstream device
        could have a completion timer timeout enabled.  If the upstream device
        did have such a timer, a failure could be seen.
      Change:
        Updated driver to not issue memory-mapped read requests after slowing
        the core clock on certain devices (e.g. 5703, 5704, 5714, 5715).
      Impact:
        Works around part of CQ 13332. There should be no side-effects.

  3.  Problem:
        CQ13135 5702 does not pass WHQL 2m_WOLPattern test.
      Cause:
        Driver change done for CQ12875 in release v8.33 is causing the 5702
        to not recognize the first interesting wakeup packet received.
      Change:
        Backed out change for CQ12875 for this release so this release can
        continue. CQ12875 will be characterized further.
      Impact:
        Resolve CQ13135 issue, CQ12875 remains unresolved.
 


Version 8.38  July 20, 2005      
----------------------------------------
  1.  Problem:
        CQ13477 OID_GEN_XMIT_OK and OID_GEN_RCV_OK do not return correct
        values for null buffer queries during Windows HCT 1c_64BitOIDs test.
      Cause:
        Driver change done for CQ13358 in release v8.37 caused this issue;
        such that zero length buffer queries were accepted by the v8.37
        driver and returned 4 bytes of data.
      Change:
        Updated driver code for Windows DDK MiniportQueryInformation function
        so that it does not return any data for zero length buffer sizes and
        reports Buffer was too short.
      Impact:
        Resolve CQ13477 issue.
 


Version 8.37  July 18, 2005      
----------------------------------------
  1.  Problem:
        CQ13358 Broadcom MIB statistic field shows zero for MIB SNMP Query 
        Statistics OID operations.
        Driver versions 8.14 to 8.36 (and 7.99 to 7.108 sustaining) returned 
        zero to MIB SNMP Query Statistics OID operations.
      Cause:
        The combination of driver code path in versions listed above for 
        handling of  Windows DDK MiniportQueryInformation function, coupled 
        with the fact that upper layer SW was making a SNMP based query using
        a query with a buffer size of 7 bytes data size for the Statistic OIDs; 
        resulted in driver returning a buffer size indication of 7 bytes,
        which was interpreted by upper layer SW as having a final value of
        zero, because the size of the buffer returned should have been 4 bytes
        or 8 bytes depending on the OID in question.
      Change:
        Modified Driver implementation for Windows DDK MiniportQueryInformation
        function Statistics OIDs; so that it returns 4 bytes of data if Query
        data size was 1 to 7 bytes or 8 bytes if the Query data size was 8 
        bytes or larger. This is per Windows DDK MiniportQueryInformation 
        function specification.
      Impact:
        Resolve CQ13358 issue.

  2.  Enhancement Request:
        Add force link configuration for 5714S/5715S serdes/fiber based devices.
      Cause:
        5714S/5715S serdes/fiber based devices may not get link if 
        auto-negotiation option is disabled by the switch.
      Change:
         For 5714S/5715S serdes/fiber based devices, driver will force to
         1000Gbps full duplex mode if the link can't be established but link
         energy has been detected and no configuration words were received from
         the switch. 
      Impact:
         Resolve CQ13005, 13122 issues.
         This change only affects 5714S/5715S serdes/fiber based devices. It 
         has no impact if auto-negotiation is enabled by the switch. It does
         not affect GPHY based devices.
         
  3.  Problem:
        CQ12910   5714S A1 fails 2c_OffloadCheckSum NDIS test intermittently.
      Cause:
        5714S and  5715S Fiber devices require different sequencing of PHY
        register settings, and modifications to reset handling.
      Change:
        Reordered setting of PHY registers such that the advertisement register
        is written first and then Auto Negotiation is initiated.   Also
        modified the OS initiated reset routine to change how OS initiated
        resets are handled on 5714S and 5715S devices.
      Impact:
        Resolve CQ12910 issue.
 
  4.  Problem:
         CQ13463 Invalid Data in OEM Driver INF file for XP32
      Cause:
         OEM specific installation file for XP32 had errors in details of 
         driver name to be installed. The Broadcom b57win32.inf file did not
         have this issue.
      Change:
         Updated OEM specific installation file with correct driver name to 
         be installed for OEM devices with 4 part PCI ID matching.
      Impact:
         Resolve CQ13463 issue.



Version 8.36  July 11, 2005      
----------------------------------------

  1.  Problem:
        CQ13290, CQ13155 Diagnostic memory tests fail randomly.
      Cause:
         A change introduced into 8.32 to reduce OID stack usage inadvertently
         allocated only one temporary memory buffer for all loaded devices as
         opposed to allocating one temporary memory buffer for each loaded
         device.
      Change:
         Moved OID temporary buffer allocation from being statically declared
         to the device instance data structure.
      Impact:
         Resolve CQ13290, CQ13155 issues.

  2.  Enhancement Request:
        CQ13286 Add hidden registry key to disable advertisement of 1000mb.
      Change:
         Added hidden registry key "DisableGig". When this key is set
         to a non-zero value, the device driver will program the device
         to not advertise 1000mb.
      Impact:
         Resolve CQ13286 issue.

  3.  Enhancement Request:
        CQ13345 Add 4 ID match for new OEM project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ13345 Enhancement Request.  


Version 8.35  June 29, 2005      
----------------------------------------
  1.  Enhancement Request:
        CQ13094 Add 4 ID match for new OEM project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ13094 issue.  

  2.  Enhancement Request:
        CQ13163 Add five new 4 ID match device support for OEM projects.
      Cause:
        Request for new 4 ID match support  by OEM.
      Change:
        Added five new 4 ID match device support for OEM project.
      Impact:
        Resolve CQ13163 issue.  

  3.  Enhancement Request:
        CQ13188 Add 4 ID match for new OEM project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ13188 issue.  

  4.  Problem:
        CQ13145 NDIS 5.1 Driver v8.34 Installation INF file had internally
        identified a 5789 device as a 5788 device.
        This resulted in 5789 device getting the same installation parameters
        as a 5788 device.
      Cause:
         Device identification error in v8.34 AMD64 INF installation file.
      Change:
         Corrected device identification error in prior AMD64 INF installation
         file.
      Impact:
         Resolve CQ13145 issue.

  5.  Problem:
        CQ12894  Need to disable LSO for 5789 device in AMD64 INF file.
        Need to add Registry Delete of old LSO option for 5789 devices in
        AMD64 platform that had 8.30 driver installed. 
      Cause:
        LSO option in Registry stays during a driver upgrade, unless it is 
        specifically removed.  To avoid uninstall and reinstall of device
        driver to update Registry, driver version 8.35 should delete LSO 
        option from prior installation.
      Change:
        Removed LSO option for 5789 in INF install file and added Registry 
        delete of unintentional LSO option from prior release of driver.
      Impact:
        Resolve CQ12894 issue.

  6. Request: 
        CQ9270 Enable LSO Advanced Option for 5788 devices in AMD64
      Change:
        Enabled LSO Advanced Option for 5788 devices in AMD64 Install INF file.
      Impact:
        Resolve CQ9270 issue.

  7.  Problem:
        CQ13203  5752A1 Fails WHQL ACPI Stress Test for HCT12.1
      Cause:
        A change introduced in v8.31 to power off the phy on 5752 family
        parts when wol is disabled and asf is disabled caused the failure.
      Change:
        Commented out code for 5752 family parts that powers off the phy and
        revert back to the autophy power down power saving scheme.
      Impact:
        Resolve CQ13203 issue.




Version 8.34  June 07, 2005      
----------------------------------------
  1.  Problem:
        CQ12733 Incorrect MAC address on WinPE boot via PXE
    Cause:
        When the device driver is loaded with PXE active, the driver
        would reset the controller with the controller's memory arbiter
        disabled.
    Change:
        Modified the driver to not disable the controller's memory arbiter
        when issuing a device reset.
      Impact:
        Resolve CQ12733 issue.

  2.  Problem:
        CQ13072 Don't switch to VAUX power on 5714 and 5715 NICs
    Cause:
        Too much VAUX power is drawn from the system, when driver  
        switches NIC from Main PCI-E power to VAUX PCI-E power. 
        This is problem is specific and limited to 5714 and 5715 NICs
    Change:
        Modified the driver so that it does not switch 5714/5715 NIC
        power from Main to VAUX and only uses Main PCI-E power.
      Impact:
        Resolve CQ13072 issue.



Version 8.33  June 02, 2005      
----------------------------------------
  1.  Problem:
        CQ13032 Incorrect friendly name for 5714s and 5715s on NT 4.0 
    Cause:
        New device support addition in 8.32 needed distinction for copper
        and fiber interfaces.
    Change:
        Modified NT4 NDIS4 Installation INF file to correctly install copper
        and fiber versions of 5714 and 5715 Adapters.
      Impact:
        Resolve CQ13032 issue.

  2.  Problem:
        CQ12899 WinPE locks up when driver is loaded via RIS
    Cause:
        The device driver was initializing the device incorrectly when cleaning
        up after PXE by issuing commands to the ASF firmware when ASF is not
        loaded.
    Change:
        Removed commands to ASF during PXE cleanup.
      Impact:
        Resolve CQ12899 issue.

  3.  Enhancement Request:
        CQ13062 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ13062 issue.  

  4.  Problem:
        CQ12929 5714S A1 cannot establish link when connected to Dell 
        PowerConnect 5224 switch 
    Cause:
        The switch does not advertise full duplex. By default, the 
        chip/firware/driver only advertized full duplex, leading to a failure
        to connect.
    Change:
        Changed the driver to advertise half duplex also.
      Impact:
        None.

  5.  Problem:
        CQ12970 LE 5780S  A4 and Connection to Switch Causes Increased CPU 
        Utilization
    Cause:
        The device ID was not recognized by the driver, so the driver was 
        incorrectly treating the device as a copper device, not a fiber device.
    Change:
        Added the new ID to the check list in the driver, to allow the driver
        to program the device correctly.
      Impact:
        None.

  6.  Problem:        
        CQ12875 - The controller would link at 10mb when the driver is
        disabled in windows and WOL speed in the control panel is set
        10mb. The expected behavior is for the controller to link at
        the speed specified in nvram when the driver is disabled.
      Cause:
        The driver was not correctly configuring the WOL speed when
        the driver's halt routine was called when the driver is disabled.
      Change:
        Modified driver to correctly configure the WOL speed based on
        nvram setting when the driver's halt routine was called.
      Impact:
        There is no known negative impact of this change.


Version 8.32  May 26, 2005      
----------------------------------------
  1.  Problem:
        CQ12622 5704-B0 with Jumbo Frame: One port stops responding 
        within 2 hrs when passing Chariot traffic to both ports concurrently.
      Cause:
        This problem only occurs when both jumbo frames
        and LSO are both enabled and in use.  This problem also only occurs
        on 5704, and not on 5703, 5705, or other 57xx controller.      
        There is race condition in the LSO firmware that can cause a 
        dead-lock where firmware waits forever for state machine to 
        become IDLE before moving on.  
        This causes firmware to hang up and back pressure all other
        state machines which in turn prevents the device to further 
        transmit and receive traffic.
    Change:
        Modified 5704 LSO firmware to prevent the dead-lock condition.
      Impact:
        Resolve CQ12622 issue. There should be no side-effects of the fix.

  2.  Problem:
        CQ12894  Need to disable LSO for 5789 device in AMD64 INF file.
        Need to add Registry Delete of old LSO option for 5789 devices in
        AMD64 platform that had 8.30 driver installed. 
      Cause:
        LSO option in Registry stays during a driver upgrade, unless it is 
        specifically removed.  To avoid uninstall and reinstall of device driver
        to update Registry, driver version 8.32 should delete LSO option from
        prior installation.
      Change:
        Removed LSO option for 5789 in INF install file and added Registry
        delete of unintentional LSO option from prior release of driver.
      Impact:
        Resolve CQ12894 issue.

  3.  Problem:
        CQ12983 Not able to complete installation of 5714c on NT 4 system.
      Cause:
        New devices: 5714c, 5714s, 5715c, 5715s were not supported until tested.
      Change:
        Added new device 5714c, 5714s, 5715c, 5715c support.
      Impact:
        Resolve CQ12983 issue.

  4.  Problem:
        CQ12910 5714S A1 fails 2c_OffloadCheckSum NDIS test.
      Cause:
        New 5714s, 5715s Fiber device support not fully implemented.
      Change:
        Added new 5714s , 5715s Fiber device support.
      Impact:
        Resolve CQ12910 issue.

  5.  Enhancement Request:
        NdisQueryBufferSafe was being called while holding a spinlock in
        the send packet routine.
      Change:
        Reordered routine the routine that was calling NdisQueryBufferSafe
        to not hold a spinlock. This change was made to confirm to Microsoft
        DDK specifications.
      Impact:
        There are no known issues with this change.


Version 8.31  May 17, 2005      
----------------------------------------
  1.  Problem:
        CQ12857  Flow control is not functional on 5714/5715s Fiber Adapter.
        When 5714/5715s Fiber is interfacing  to a slow 10 Mbs client; it 
        would not observe Transmit Pause from the slow client and keep
        sending packets. This would result in a very low interface speed
        between the 1 Gbps fiber 5714/5715s device and the 10 Mbps client.
      Cause:
        Driver support for 5714/5715s Fiber was not using proper register 
        selection to read and set Flow Control propreties.
      Change:
        Updated driver to use latest register data to read and set 5714/5715s
        Fiber Flow Control properties.
      Impact:
        Resolve CQ12857 issue.

  2.  Problem:
        CQ12894  Need to disable LSO for 5789 device in AMD64 INF file.
      Cause:
        LSO option was made available for 5789 by error in INF install file.
      Change:
        Removed LSO option for 5789 in INF install file.
      Impact:
        Resolve CQ12894 issue.

  3.  Enhancement Request:
        CQ12862  Add power management support for Shasta BX and CX.
      Change:
        Enable DLL power-down on Shasta BX and CX Parts.
        Select 6.25Mhz core clock on 5751M BX and CX parts when ASF is disabled
        and linked at 10mb.
        Allow Wake-on-Link on Shasta CX parts for required OEMs.
      Impact:
        Resolve CQ12862 issue.

  4.  Enhancement Request:
        CQ12863  Add power management support for 5752M.
      Change:
        Enable DLL power-down on 5752M if ASF is disabled.
        Select 6.25Mhz core clock on 5752M when ASF is disabled and linked
        at 10mb.
      Impact:
        Resolve CQ12863 issue.

  5.  Enhancement Request:
        CQ12392  Format and organize the AMD64 INF similar to the XP32 INF.
      Change:
        Formatted and organize the XP32 INF similar to the AMD64 INF 
        install file.
      Impact:
        Resolve CQ12392 issue.

  6.  Problem:        
        5714/5715 family  NICs (not LOMs) could be configured to
        draw from Vaux power if the drivers for both ports were loaded, then
        then disabled, and then one of the ports was re-enabled. In this 
        specific scenario, the NIC could be configured to draw Vaux power
        even though PCI (main) power was present, and this could potentially
        lead to a case where the NIC drew excessive current (> 600mA) from
        the slot which could exceed the amount of power that some systems
        provide to slots.  This problem is the same as CQ 9992 which was
        resolved for 5704 NICs about a year ago (v7.75).
      Cause:
        Driver did not force GPIO2 HIGH on 5714 NIC designs at initialization
        time.
      Change:
        Modified driver to apply the same fix for CQ 9992 to 5714/5715 as 
        was previously applied to 5704 NIC devices in v7.75.  This fix
        involves having the driver force GPIO2 to be HIGH during the 
        driver's early initialization code.
      Impact:
        There is no known negative impact of this change.

  7.  Problem:        
        Register reads to the 5714/5715 family of devices could return 
        incorrect data if the core clock was slowed to 12.5Mhz or 6.25Mhz.
      Cause:
        5714/5715 was designed to only support memory-mapped register reads
        when the PCI clock (133Mhz) was never more than 10X the speed of 
        the core clock.  Previous drivers could make a few memory-mapped
        register reads to the 5714/5714 family of devices when the core 
        clock was slowed.
      Change:
        Modified driver to not rely on any values read from registers after
        the core clock was slowed to 12.5Mhz.  This involved re-ordering some
        code fragments.
      Impact:
        There is no known negative impact of this change.  It may correct
        a few previous cases where WoL functionality could have failed.

  8.  Problem:        
        Register reads to the 5780 family of devices could return incorrect
        data if the core clock was slowed.
      Cause:
        5780 device (like 5714/5715) was designed to only support memory-mapped
        register reads when the PCI clock (133Mhz) was never more than 10X
        the speed of the core clock.  Previous drivers could make a few
        memory-mapped register reads to the 5714/5715 family of devices when
        the core clock was slowed to 12.5Mhz.
      Change:
        Modified driver to never slow the core clock on 5780 devices.  
        Slowing the core clock was not a requirement for 5780 devices,
        because power consumption was not a major concern for this chipset.
      Impact:
        Power consumption will be higher because the LAN core clock is not
        slowed on 5780 platforms.  However, this change may correct
        a few previous cases where WoL functionality could have failed.

  9.  Problem:        
        Minor hand-shaking problem between the driver and management
        (ASF or IPMI PT) firmware on 5714/5715 and 5780 class of products.
      Cause:
        The driver was not leaving the "NICDRV_STATE_INIT_DONE" flag in 
        shared memory on 5714/5715/5780 products when the driver shutdown
        or went into a low power state.  This could potentially cause
        failures related to management FW after the driver shutdown or the 
        system went into a low power state.
      Change:
        Modified driver to deposit the "NICDRV_STATE_INIT_DONE" flag in
        shared memory when shutting down or going into a low power state.
      Impact:
        There is no known negative impact of this change.

  10. Problem:        
        CQ12862 - Improve power management for Shasta CX step parts.
      Change:
        Allow gphy dll to be powered down when link is not present
        and asf is disabled.
        Select 6.25mhz core clock when linked at 10mb and asf is disabled.
        Allow wake on link feature for required OEM platforms.
      Impact:
        There is no known negative impact of this change.

  11. Problem:        
        CQ12863 - Add support for power management mode in 5752M.
      Change:
        Allow gphy dll to be powered down when link is not present
        and asf is disabled.
        Select 6.25mhz core clock when linked at 10mb and asf is disabled.
      Impact:
        There is no known negative impact of this change.



Version 8.30  May 09, 2005      
----------------------------------------
  1.  Problem:
        CQ11937 5714c , 5714s, 5715c, 5715s, and 5780 Clock Slowing when
        Windows is Shutting down.
      Cause:
        A device limitation in 5714, 5715, 5780 prevents enabling of very slow
        clocks (6.25 Mhz) as compared to other 57xx devices.
      Change:
        All 57xx Driver code paths were reviewed and changed to avoid setting
        the affected devices' clocks to very slow clock.
      Impact:
        Resolve CQ11937 issue.  

  2.  Problem:
        CQ12830   5714s and 5715s Fiber adapters do not pass Jumbo frame traffic.
      Cause:
        The driver had not enabled 5714s and 5715s Fiber adapter Jumbo frames
        pending hardware compatibility testing completion.      
      Change:
        Enabled 5714s and 5715s Fiber adapter Jumbo frames support.
      Impact:
        Resolve CQ12830 issue.  

  3.  Enhancement Request:
        CQ12728 Support 64 entries in multicast table.
      Change:
        Expanded the multicast table from 34 to 64 entries.
      Impact:
        The ndis driver now supports 64 entries across all windows platforms.
        Resolve CQ12728 issue. 

  4.  Problem:
        CQ12871  IA64 Driver v.8.29 showing v8.28 Under File Properties.
      Cause:
        The 8.29 build for XP64 IA64 Release was not done properly, 
        as a result of build problem.
      Change:
        Releases 8.30 will have the proper driver file version.
      Impact:
        Resolve CQ12871 issue.  


Version 8.29  April 22, 2005      
----------------------------------------
  1.  Problem:
        CQ12597 5714, 5715, 5780: LSO and Jumbo Frame Advanced Options 
        are co-existent in NDIS5.1 v8.25 driver version.
      Cause:
        A device limitation in 5714, 5715, 5780 prevents enabling of both LSO
        and Jumbo options at the same time, and driver version 8.25 allowed
        both to get enabled leading to LSO not working when Jumbo option
        was selected. 
      Change:
        Modified installation INF files for NDIS5.1 drivers to show and only 
        allow LSO or Jumbo to be enabled separately.
      Impact:
        Resolve CQ12597 issue.  

  2.  Problem:
        CQ9887 5752, 5714 and 5715 have higher than expected BER rates under
        the following conditions:
          a) When the cable is longer than 70 meters; AND
          b) A device is operating at slow corner conditions (low voltage or
             high temp).
        This problem was not observed during normal system level testing.
      Change:
        Programmed the phy on affected devices to adjust the bias current of 
        the ADC on the phy.
      Impact:
        Fix BER issue.

  3.  Problem:
        CQ12656 UM_GenTimerFunction not getting cancelled when driver is
        initialized with cable unplugged. This was causing the CPU to stay
        in C3 state for 200ms max, which is not as long as desired.
      Cause:
        Corner case in code that cancels UM_GenTimerFunction when driver is
        initialized with cable unplugged.
      Change:
        Added code to UM_GenTimerFunction to cancel the timer if it is called
        with the cable disconnected.
      Impact:
        Fix CQ12656.

  4.  Problem:
        CQ12660 Specific OEM PCI ID 4 part matched device does not show
        special WOL Link Change option.
      Cause:
        Original OEM device support addition request did not have this option
        specified.
      Change:
        Modified all INF installation support for PCI ID part ID match of 
        specific OEM devices to get the special WOL Link Change option.
      Impact:
        Fix CQ12660 issue.

  5.  Problem:
        CQ12666 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12666 issue.  

  6.  Problem:
        CQ12682 Driver does not honor the WOL_LIMIT_10MB bit in nvram when
        the operating system is not present.
      Cause:
        The code in the driver shutdown path was not checking this bit in
        the nvram.
      Change:
        Added code to the driver shutdown path to check the WOL_LIMIT_10MB
        bit in the nvram.
      Impact:
        Resolve CQ12682 issue.   

  7.  Documentation Update Request:
        CQ12731 Document "PreserveVlanInfoInRxPacket" in Registry.Doc
      Cause:
        Advanced user option to tell driver to preserve VLAN tag information.
      Change:
        Added note to Registry.doc for PreserveVlanInfoInRxPacket driver option.
      Impact:
        Resolve CQ12731 documentation update request.   



Version 8.28  April 05, 2005      
----------------------------------------
  1.  Problem:
        CQ12609 5702a2 has assertion errors running HCT12.1 XP32-SP2 
        driver verifier using checked built driver.
        This problem can cause Windows HCT Certification failures with
        checked build driver.  This miniport driver's function UM_Reset which
        can be called by Windows NDIS driver or HCT Certification tests; would
        have to be called in order to show this problem.
        Driver versions that had this problem were 8.24, 8.25, 8.26 and 8.27.
      Cause:
        Modification of 5714 device reset handling in a previous
        driver introduced a bug in the driver where a HW reset 
        would not be issued to older 5700, 5701, 5702, and 5703 
        devices.
      Change:
        Corrected driver support and Reset for all device types.
      Impact:
        Resolve CQ12609 issue.  

  2.  Problem:
        Add support for 5714, 5715, 5780 controllers.
      Cause:
        The specified controllers are available.
      Change:
        Added support for the devices in the inf files.
      Impact:
        None.




Version 8.27  April 01, 2005      
----------------------------------------
  1.  Problem:
        Remove commented support for 5714, 5715, 5780 controllers.
      Cause:
        The specified controllers are not available.
      Change:
        Removed prior commented support for the devices in the inf files.
        Changed device driver to not load on the affected parts.
      Impact:
        None.


Version 8.26  April 01, 2005      
----------------------------------------
  1.  Problem:
        CQ12557 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12557 issue.  

  2.  Problem:
        CQ12480 Remove Server 5721 IDs from OEM Desktop INFs.
      Cause:
        Original request specified general support.
      Change:
        Removed 5721 ID 0x1659 match for OEM Desktop project INF files.
      Impact:
        Resolve CQ12480 issue.  

  3.  Problem:
        CQ12561 Need to update Netmap.inf to support 5752 in 
        NT4 to Windows 2000 upgrade process.
      Cause:
        New device upgrade support request.
      Change:
        Added New device upgrade support to Netmap.inf file.
      Impact:
        Resolve CQ12561 issue.  

   Enhancements:
   =============
  1.  Request: 
        Under certain circumstances (usually in peer-to-peer configurations),
        the dynamic interrupt coalescing algorithm could occasionally set
        the interrupt coalescing thresholds to values that were sub-optimal.
        This change was related to observations made while investigating
        CQ 7735 and CQ 11231. Due to the fact that network traffic is 
        bursty, it is not practical to always be able to set the "perfect"
        interrupt coalescing threshold values at any given time for any 
        given workload.  However, this change should help some in some
        conditions.  Even without this change, performance was still
        "good" in the vast majority of cases.
      Change:
        Modified the dynamic interrupt coalescing algorithm.  Used SW packet
        counters rather than HW packet counters.  Added code to wait slightly
        longer for performance to stabilize after interrupt threshold
        parameter changes, and slightly modified the threshold values.
        This change was originally prototyped in the v7.90z driver.
      Impact:
        Performance characteristics could change slightly, especially in
        peer-to-peer configurations.

  4.  Problem:
        CQ12587 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12587 issue.  

  5.  Problem:
        Remove support for 5714, 5715, 5780 controllers.
      Cause:
        The specified controllers are not available.
      Change:
        Removed support for the devices in the inf files.
        Changed device driver to not load on the affected parts.
      Impact:
        None.



Version 8.25  March 26, 2005      
----------------------------------------
  1.  Problem:
        CQ12524  Checksum failed when ASF writes to NVRAM from windows.
        This problem only occurs on Baxter Device IDs 0x1600 and 0x1601 that 
        introduce NVRAM Address Lockout feature for protection of TPM firmware
        and its environment.
      Cause:
        Prior drivers supporting Baxter IDs 0x1600 and 0x1601 did not check
        for new NVRAM hardware address lockout status and tried to access
        NVRAM unconditionally. This resulted in TPM firmware to stop running
        when a configuration change was performed in ASF or TPM configuration
        by use of the Windows Driver NVRAM access functions.
      Change:
        Modified Windows Driver to first check for NVRAM address lockout and 
        follow new access arbitration procedure.
        Updated driver for support of all NVRAM devices following a does not 
        verify status report on one NVRAM vendor device.
      Impact:
        Resolve CQ12524 issue which caused ASF capable NIC or LOM to disappear
        from ASFConfig.exe display screen when a configuration option was changed
        earlier with the same utility.  The configuration update is stored in NVRAM and
        when NVRAM has a checksum failure; it does not get listed anymore in 
        ASFConfig.exe utility.
         


Version 8.24  March 24, 2005      
----------------------------------------
  1.  Problem:
        CQ12389 Remove PCI 4 part ID match support for OEM.
      Cause:
        Change in OEM project device usage.
      Change:
        Removed PCI 4 part ID match for OEM.
      Impact:
        Resolve CQ12389 issue.  

  2.  Problem:
        CQ12499 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12499 issue.  

  3.  Problem:
        CQ12454 Use memory coherent macros for proper 
        AMD64 platform Register Read and Write accesses.
        This issue is only applicable to AMD64 systems and 
        is a direct result of updated Windows Device Driver Kit (DDK)
        supporting AMD64 driver builds.
      Cause:
        Original DDK and driver implementation did not have
        these macros defined and used. 
      Change:
        Added newly defined KeMemoryBarrier() AMD64 DDK 
        function call to Broadcom Driver Register memory mapped
        Read and Write accesses.
      Impact:
        Resolve CQ12454 issue and conform to the new AMD64 DDK
        Windows Driver specifications.

  4.  Problem:
        CQ12462 System hang or blue screen when ReverseNway is enabled.
        System hang or blue screen when running loopback test on single
        processor systems with multi-processor kernel.
      Cause:
        Fix for CQ12264 did not properly handle spinlock usage on
        single processor systems vs. multi-processor systems.
        Fix for CQ12264 did not properly handle spinlock dependencies
        when the ReverseNway feature was enabled.
      Change:
        Corrected spinlock code in the loopback test to properly qualify
        the releasing and acquiring of PHY_LOCK with the MpTuning variable
        in the MM_IndicateStatus routine.
        Removed references to releasing and acquiring of MAIN_LOCK in the
        MM_IndicateStatus routine.
      Impact:
        Resolve CQ12462.

  5.  Problem:
        CQ12517 OEM Device does not show all applicable advanced options. 
      Cause:
        The install file only allowed OEM mobile options.
      Change:
        Modified OEM device support to show all applicable advanced options. 
      Impact:
        Resolve CQ12517 issue.  

  6.  Problem:
        CQ12524  Checksum failed when ASF writes to NVRAM from windows.
        This problem only occurs on Baxter Device IDs 0x1600 and 0x1601 that 
        introduce NVRAM Address Lockout feature for protection of TPM firmware
        and its environment.
      Cause:
        Prior drivers supporting Baxter IDs 0x1600 and 0x1601 did not check
        for new NVRAM hardware address lockout status and tried to access
        NVRAM unconditionally. This resulted in TPM firmware to stop running
        when a configuration change was performed in ASF or TPM configuration
        by use of the Windows Driver NVRAM access functions.
      Change:
        Modified Windows Driver to first check for NVRAM address lockout and 
        follow new access arbitration procedure.
      Impact:
        Resolve CQ12524 issue which caused ASF capable NIC or LOM to disappear
        from ASFConfig.exe display screen when a configuration option was changed
        earlier with the same utility.  The configuration update is stored in NVRAM and
        when NVRAM has a checksum failure; it does not get listed anymore in 
        ASFConfig.exe utility.

  7.  Problem:
        CQ12519 Driver to Bootcode handshake during Windows Shutdown
        requires update so that normal and fast boot versions of Bootcode
        can initialize properly in conjunction with Windows Driver loading and 
        unloading.
      Cause:
        Original driver implementation in all prior releases.
      Change:
        Modified Windows Driver with updated driver to bootcode handshake
        procedure. 
      Impact:
        Resolve CQ12519 issue.  

  8.   Driver modification to add peer to peer communication for 5714 dual 
        ported device when ever a chip Reset is performed.
      Cause:
        Addition of 5714 device support.
      Change:
        Added peer to peer messages between the two driver instances 
        running on dual ported 5714 devices. 
      Impact:
        Support of 5714 devices.  




Version 8.23  March 16, 2005   
----------------------------------------
  1.  Problem:
        Add support back for PCI IDs 0x1600, 0x1601, 0x1668, 0x1669, 
        0x166A, 0x166B which will install the following Broadcom models:
        BCM5714C, BCM5714S, BCM5780C, BC5780S, BC5752, BCM5752M. 
      Change:
        Added the above PCI IDs to all NDIS  INF  installation support files. 

  2.  Problem:
        CQ12457 Few Transmit CRC (Cyclic Redundancy Check) errors seen
        at the Switch counters when Jumbo Frames are enabled and used
        extensively on 57xx Adapters and LOMs.
        These Transmit CRC errors are only applicable when Jumbo Packets
        advanced option is enabled and used. These Transmit CRC errors
        will not be seen by the other system which is receiving the Jumbo 
        Packets since the Switch retransmits all frames in between the two
        connected ports.  Cable length and quality are also important factors
        in CRC Transmit errors that are observed by the Switch.
      Change:
        Added setting of PHY Control Register FIFO Elasticity Enable option;
        when Jumbo Packets are enabled on all 57xx NIC and LOM devices.
        This is a minor improvement to reduce and eliminate Transmit CRC
        errors observed at the Switch port connected to the 57xx Device. 
      Cause:
        Original Driver implementation did not enable this PHY option.
      Impact:
        Resolve CQ12457  issue. 




Version 8.22 D  March 11, 2005      *** INF Installation File Update Only ***
----------------------------------------
  1.  Problem:
        CQ12410 and CQ12408: NT4 and Win98Me Release folders had INF
        installation files that included 0x1600, and 0x1668 Device IDs which
        were not fully tested.
      Change:
        Removed NT4 and Win98Me INF entries that supported  0x1600, 
        0x1668 Device IDs.
      Cause:
        Prior released driver.
      Impact:
        Resolve CQ12410 and CQ12408  issues.  


Version 8.22 C  March 11, 2005      *** INF Installation File Update Only ***
----------------------------------------
  1.  Problem:
        AMD64 Release folder had INF installation files that included 
        0x1600 Device IDs which were not fully tested.
      Change:
        Removed AMD64 INF entries that supported 0x1600 Device IDs.


Version 8.22 B  March 10, 2005      *** INF Installation File Update Only ***
----------------------------------------
  1.  Problem:
        CQ12357 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12357 issue.  



Version 8.22  March 08, 2005
----------------------------------------
  1.  Problem:
        CQ12264 Blue screen when running Driver Verifier and control suite
        diags.
      Cause:
        The driver was improperly holding a spinlock during the
        loopback test.
      Change:
        Corrected the driver to release spinlocks during the loopback
        test.
      Impact:
        Resolve CQ12264 issue.

  2.  Problem:
        CQ12026 A TPM NVRAM access could fail if driver reset the 575x device
        during the attempted TPM NVRAM access
      Cause:
        The NDIS driver would acquire the NVRAM lock before doing a reset and then
        halt the internal CPU to prevent NVRAM contention between driver and 
        bootcode.  However, the driver would then release the NVRAM lock right 
        before doing the chip reset.  This left a tiny window of vulnerability
        for the TPM to initiate an NVRAM access right after the driver released
        the NVRAM lock and right before the driver issued a reset to the 
        device.  If the driver were to issue a reset while the TPM was trying to 
        make an NVRAM access, the reset would cause the TPM NVRAM access to fail, 
        which could cause a higher level TPM command to fail.  This problem has
        never been reported by a customer in the field, but was seen doing 
        exhaustive low-level testing at Broadcom.
      Change:
        Changed the device driver to acquire nvram lock during device resets for
        5751 and 5752 family of devices (the only devices that support TPM).
      Impact:
        Resolves CQ 12026.  There should be no side effects from this change.


Version 8.21  March 03, 2005
----------------------------------------
  1.  Problem:
        CQ12082 Driver Verifier Enable/Disable Test for HCT 12.0 fails for
        7.104 NDIS 5.1 Driver.
      Cause:
        Some RX packets were not processed back into the driver, and driver
        returned successfully from its Halt function.
      Change:
        Added driver wait to get RX packets back from NDIS, prior to returning
        successfully from the driver Halt function.
      Impact:
        Resolve CQ12082 issue.

  2.  Problem:
        Remove support for 5752, 5753, 5714, 5715 controllers.
      Cause:
        The specified controllers are not available.
      Change:
        Removed support for the devices in the inf files.
        Changed device driver to not load on the affected parts.
      Impact:
        None.

  3.  Problem:
        Serdes connection of BCM5704s is still present after a system is
        shutdown.
      Cause:
        The Serdes link is still active.
      Change:
        Changed UM_Shutdown() routine to power down Tx/Rx SerDes for BCM5704s.
      Impact:
        None.


Version 8.20  February 25, 2005
----------------------------------------
  1.  Problem:
        CQ12175, CQ12192 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12175, CQ12192 issue. 
        
  2.  Problem:
        64bit addressing capability is not being advertised for PCI-E devices.
      Cause:
        The driver was not advertising correct addressing capabilities for
        PCI-E devices.
      Change:
        Changed 64bit addressing advertising code for PCI-E devices.
      Impact:
        None. 

  3.  Problem:
        CQ12207, CQ12211, 5714S does not display correct friendly name and
        advanced properties in the control panel.
      Cause:
        The inf file was treating 5714S as a copper device.
      Change:
        Corrected inf files.
      Impact:
        Resolve CQ12207, CQ12211.

  4.  Problem:
        CQ12275 5714 was initialized with incorrect dma watermarks when
        configured for non-jumbo packets.
      Cause:
        The dma watermarks was not being initialized correctly.
      Change:
        Corrected dma watermark initialization code for 5714.
      Impact:
        Resolve CQ12275.

  5.  Problem:
        CQ12149 Network tray icon shows no link after remove CPM and then
        insert DLink ESM.
      Cause:
        The device driver did not turn off hardware autoneg before checking
        if the device is receiving Rx Config word.
      Change:
        Changed the device driver to turn off H/W autoneg before reading
        the MAC status register.
      Impact:
        Resolve CQ12149.


Version 8.19  February 16, 2005
----------------------------------------
  1.  Problem:
        CQ11136 Preserve the state of GPIO3 on 5752 controllers.
      Cause:
        New requirement for 5752 controllers.
      Change:
        Added code to do read modify write to GPIO3 control bits.
      Impact:
        Resolve CQ11136 issue. 

  2.  Problem:
        CQ12038 Add registry key to support disabling OID_MAC_OPTION_NO_LOOPBACK
        option.
      Cause:
        New requirement.
      Change:
        Added registry key and code to optionally disable OID_MAC_OPTION_NO_LOOPBACK
        bit.
      Impact:
        If OID_MAC_OPTION_NO_LOOPBACK bit is not set then an intermediate layer
        module must perform packet loopbacks on behalf of the driver.

  3.  Problem:
        CQ12142 Add 4 ID match support for OEM new project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM project.
      Impact:
        Resolve CQ12142 issue.  

  4.  Problem:
        CQ12100 Bluescreen on 5750/5751 BX when driver is unloaded with
        ASF/IPMI disabled and WoL is disabled in NVRAM.
      Cause:
        Change for CQ11226 was causing the driver to unload with the
        phy dll powered off.
      Change:
        Corrected phy dll code to turn on the phy dll during driver
        unload.
      Impact:
        Resolve CQ12100.

  5.  Problem:
        5714s Fiber Device not able to ping to Server system.
      Cause:
        New 5714s Fiber support not yet added.
      Change:
        Added 5714s Fiber support in driver.
      Impact:
        Resolve 5714s Fiber ping issue.

  6.  Problem:
        CQ12157 Validate support for capacitive coupling and pre-emphasis.
      Cause:
        New support in the driver for capacitive coupling and pre-emphasis
        was not working correctly when loaded on boards with old bootcode.
      Change:
        Added check for bootcode shared memory version number before
        checking for capacitive coupling and pre-emphasis configuration
        information.
      Impact:
        Resolve CQ12157



Version 8.18  February 07, 2005
----------------------------------------
  1.  Problem:
        CQ 11971  Add new device 4 part ID support for mobile OEM customer. 
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM to all NDIS versions.
      Impact:
        Resolve CQ11971 issue.  

  2.  Problem:
        CQ 12052  5714 NIC stops responding on sending Jumbo frames. 
      Cause:
        New 5714 Device DMA High and Low Water Marks needed update.
      Change:
        Updated 5714 Device DMA High and Low Water Marks in driver.
      Impact:
        Resolve CQ12052 issue.  


Version 8.17  February 02, 2005
----------------------------------------
  1.  Problem:
        CQ 11764, Burned in address shows up as Multicast or wrong address on NICs with 
        IPMI.
      Cause:
        The HaltCpu() routine incorrectly releases the Rx/Tx CPU NVRAM grant if it halts 
        a CPU currently asserting its NVRAM arbitration request. This is incorrect because 
        the driver has no way to know which CPU (Tx or Rx) is currently the NVRAM grant owner, 
        and therefore should not issue a dummy read and should not release the grant (see HaltCpu()).
        Also, the driver at various places was issuing a dummy read w/o waiting for the result.
        The above errors break the NVRAM access protocol.
      Change:
         For the 5704 and 5703 chips, _both_ CPUs are halted. All NVRAM reads now wait for
         the result. 
      Impact:
        None.

  2.  Problem:
        CQ 11977, Bugcheck 0x7f when using .Net Framework 1.1
      Cause:
        The operating system ran out of stack space during a transmit request.
      Change:
        Modified send routine to reduce stack space usage by 1024 bytes.
      Impact:
        None.

  3.  Problem:
        CQ11969 In OEM System, when CPM cat 5 cable is disconnected 
        from secondary switch; CPU utilization jump to 40+%
      Cause:
        The driver was using a blocking wait Windows kernel call to wait for completion of 
        5704 Serdes Fiber port Soft Reset operation.
      Change:
        Modified driver to no longer use blocking Windows kernel call for waiting and wait
        without holding other threads.
      Impact:
        Resolve CQ11969 issue.



Version 8.16  January 28, 2005
----------------------------------------
  1.  Problem:
        CQ11875 5705A3 Cannot start upon loading NDIS5.1 v8.14 driver
      Cause:
        Addition of new device support and revisions in Windows driver caused
        certain adapter models (5705) to be rejected during update of driver.
      Change:
        Modified the device driver to support all required adapter models.
      Impact:
        Resolve CQ11875 issue.  


Version 8.15  January 26, 2005
----------------------------------------
  1.  Problem:
        CQ11139, CQ11143 - PCI Config Offset 0x30 (ROM base address)
        is writable.
      Cause:
        The windows device driver enabled making ROM base address register
        writable when only PXE should enable this register to be writable.
      Change:
        Modified the device driver to not make the ROM base address request
        writable.
      Impact:
        Resolve CQ11139 issue.  

  2.  Problem:
        CQ11833 Add 4 ID match support for NDIS 5.1 OEM new Server project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for NDIS 5.1 OEM project.
      Impact:
        Resolve CQ11833 issue.  

  3.  Problem:
        CQ11834 Add 4 ID match support for all NDIS versions for
        OEM new Desktop project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM to all NDIS versions.
      Impact:
        Resolve CQ11834 issue.  

  4.  Problem:
        CQ11835 Add 4 ID match support for all NDIS versions for
        OEM new Desktop project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM to all NDIS versions.
      Impact:
        Resolve CQ11835 issue.  

  5.  Problem:
        CQ11836 Add 4 ID match support for all NDIS versions for
        OEM new Desktop project.
      Cause:
        New 4 ID match support request by OEM.
      Change:
        Added new 4 ID match for OEM to all NDIS versions.
      Impact:
        Resolve CQ11836 issue.  

  6.  Problem:
        CQ11866 Registry Parameters on B57amd64.inf Shows 
        Duplicate Info for 5705A2
      Cause:
        There was a duplicate entry in Registry parameters, but it
        would not cause any installation problems.
      Change:
        Removed duplicate entry in 5705A2 Registry Parameters section.
      Impact:
        Resolve CQ11866 issue.  

  7.  Problem:
        CQ11859 OEM Laptop with 5705M Hang in transition to S1 , S3 
        when using battery and Windows WOL option turned off for 5705M.
      Cause:
        The PHY module was being turned Off by OEM Software monitor when
        running on battery, and driver applying change of clocks and Reset to 
        RX and TX state machines during transition to low power.
      Change:
        Added check of PHY power in driver prior to application of the clock change
        and Reset during transition to low power.
      Impact:
        Resolve CQ11859 issue.  

  8.  Problem:
        CQ11850  Add  OEM Laptop new 5705M  4 ID match support. 
      Cause:
        New OEM device ID request.
      Change:
        Added new OEM Device ID support.
      Impact:
        Resolve CQ11850 issue.  

  9.  Problem:
        CQ11967  Add new device IDs for OEM Desktop project. 
      Cause:
        New OEM device ID request.
      Change:
        Added new OEM Device ID support.
      Impact:
        Resolve CQ11967 issue.  

 10.  Problem:
        CQ11935  Add new device ID for OEM project. 
      Cause:
        New OEM device ID request.
      Change:
        Added new OEM Device ID support.
      Impact:
        Resolve CQ11935 issue.  

 11.  Problem:
        CQ11978  Add new device ID for OEM project. 
      Cause:
        New OEM device ID request.
      Change:
        Added new OEM Device ID support.
      Impact:
        Resolve CQ11978 issue.  

 12.  Problem:
        Redundant writes to the Power Management Control Register to place
        the controller into D3 state.
      Cause:
        The device driver and Windows was programming the controller to D3.
      Change:
        Removed redundant write to D3 in device driver.
      Impact:
        None.


Version 8.14  January 11, 2005
----------------------------------------
  1. Problem:
        CQ11553 - FCS errors and low netperf performance
        throughput at forced 100F and 10F on 5714A0.
      Cause:
        New device support for 5714 PHY was required.
      Change:
        Added required device support for 5714 PHY.
      Impact:
        Resolve CQ11553 issue.  
      Special Note:
        This problem was fixed in driver v8.13 with CQ11558 issue.

  2. Problem:
        CQ11634 - IA64: Undo OEM requested change done in 7.86d
        so that when they upgrade a driver, the TXSUM setting does
        not change.
      Cause:
        OEM requested above change.
      Change:
        Modified OEM specific INF install option for their IA64 platforms.
      Impact:
        Resolve CQ11634 issue.  

  3. Problem:
        CQ11672 - Enable "USE_KLOCKS" in NDIS 5.1 driver
      Cause:
        Performance improvement.
      Change:
        Added this option define to XP32 NDIS 5.1 Driver compiler sources file.
      Impact:
        Resolve CQ11672 issue.  

  4. Problem:
        CQ11723 - Internal file name in properties for b57amd64.sys of v7.97
        had extra characters and displayed b57netamd64.sys
      Cause:
        The compile file specifier had b57netamd64 as OS name.
      Change:
        Changed the compile file specifier to b57amd64 for OS name.
      Impact:
        Resolve CQ11723 issue.  This was only a cosmetics issue and had
        no effect on operation of the AMD64 driver.

  5. Problem:
        CQ11760 - Uninstall driver or Disable 5714-A0 LOM  hangs the system.
        CQ11763 - Disable of one 5714-A0 LOM caused both 5714-A0 LOMs to be 
        disabled on the system.
      Cause:
        The driver HaltCPU function for 5714 was being invoked multiple times.
      Change:
        Modified the driver not to invoke HaltCPU function for 5714 multiple times.
      Impact:
        Resolve CQ11760 and CQ11763 issues.  

  6. Problem:
        CQ11762 - Same MAC address for 5714 LOMs in Windows 2000 with NDIS v8.13.
        CQ11696 - Intermittent system freeze followed by continuous BSOD at bootup
        when installing v8.13 on 5714.
      Cause:
        The driver support for identification of different chip family and revision needed
        update for new device support recently introduced.
      Change:
        Modified the driver for correct identification of chip family and revision.
      Impact:
        Resolve CQ11762 and CQ11696 issues.  

  7. Problem:
        CQ11824 - Windows CHKINF failure in 8.13 XP32 installation INF file.
      Cause:
        The new device entry had incomplete XP install section name.
      Change:
        Added the new device entry XP install section name.
      Impact:
        Resolve CQ11824 issue.  

  8. Problem:
        CQ11819 - Driver returns 0 for statistics when calling OIDs using a 32 bit buffer
      Cause:
        The driver attempt to adjust data for 32 application put the result in wrong location.
      Change:
        Modified the driver to adjust data for 32 application to put the result in proper location.
      Impact:
        Resolve CQ11819 issue.  

  9. Problem:
        CQ11803 - 5714 Speed & duplex settings show only AUTO in driver property
      Cause:
        The driver had limited speed support for new 5714 device.
      Change:
        Expanded driver speed support for new 5714 device.
      Impact:
        Resolve CQ11803 issue.  

  10. Problem:
        CQ11780 - MAC address corruption issue after cold or warm boot
        CQ11764 - Burned in address shows up as Multicast or wrong address on NICs with IPMI
      Cause:
        Recovery time needed between Rx CPU halt and first NVRam read (5704).
      Change:
        Modified the driver to not release the Rx CPU NVRam request if the Rx CPU was halted while 
        its NVRam request is pending. The request is removed the next time NVRam access is needed.
      Impact:
        Longer init time may occur for 5704 devices (up to .5 seconds).  





Version 8.13  December 16, 2004
----------------------------------------
  1. Problem:
        CQ11558 - AUT Forced speed does not negotiate properly with switch
        set to auto-negotiate.
      Cause:
        New device support for 5714 PHY was required.
      Change:
        Added required device support for 5714 PHY.
      Impact:
        Resolve CQ11558 issue.

  2. Problem:
        CQ11580 - Flow control does not get enabled on 5714.
      Cause:
        New device support for 5714 PHY was required.
      Change:
        Added required device support for 5714 PHY.
      Impact:
        Resolve CQ11580 issue.

  3. Problem:
        CQ11144 - Ndis driver does not reload nvram wol settings when winfwupg
        utility is used.
      Cause:
        The ndis driver was did not reload the nvram wol settings on driver
        resume from winfwupg.
      Change:
        Added code to reload nvram wol settings when the driver resumes from
        winfwupg.
      Impact:
        Resolve CQ11144 issue.

  4. Problem:
        CQ11670 - Windows Server 2003 OS takes a long time to boot when 5714
        is installed.   
      Cause:
        New driver support for 5714 was not yet complete in driver version 8.12
      Change:
        Added driver support for 5714 device.
      Impact:
        Resolve CQ11670 issue.

  5. Problem:
        CQ11641 - Add support for 5752.
      Cause:
        New driver support for 5752.
      Change:
        Added driver support for 5752 device.
      Impact:
        Resolve CQ11641 issue.     

Version 8.12  December 10, 2004
----------------------------------------
  1. Problem:
        CQ11601 - Incorrect MAC address is displayed in Windows with 5714.
      Cause:
        New device support for 5714 NVRAM access method was required.
      Change:
        Added required NVRAM access method for 5714; as well as read of
        PCI configuration register to distinguish function zero or one driver loading.
      Impact:
        Resolve CQ 11601 issue.

  2. Problem:
        CQ11543 - Windows 2000 Blue Screen after creating a BASP team
        on 5714 LOM system.
      Cause:
        New device support for 5714 NVRAM access method was required.
      Change:
        Added required NVRAM access method for 5714; as well as read of
        PCI configuration register to distinguish function zero or one driver loading.
      Impact:
        Resolve CQ 11543 issue.


Version 8.11  December 09, 2004
----------------------------------------
  1. Problem:
        CQ11147 - Performance lower than expected in a few rare test scenarios
        with 5751 family of devices. When this occurred, throughput would 
        periodically drop to zero for short periods of time which would lower
        the average throughput. This problem was only seen when running
        high throughput peer-to-peer performance tests with a single Linux
        client.  The issue would not be seen in tests involving multiple 
        remote stations, or tests involving Windows clients
      Cause:
        Algorithm to coalesce send producer index updates on 5705 devices
        was also used on 5751 devices.  This is unnecessary on with 5751.
      Change:
        Do not coalesce send producer index updates on 5751 family devices
      Impact:
        Resolve CQ 11147.  There are no side-effects of this change.

  2. Problem:
        CQ11408 Add support for OEM 5704S NIC adapter.
      Cause:
        New device support request.
      Change:
        Added OEM INF Install support.
      Impact:
        Resolve CQ11408 issue.

  3. Problem:
        CQ11151 - NDIS driver does not properly support Dot3Stats OIDs
      Cause:
        Driver was returning wrong data size of 8 bytes instead of 4 bytes.
      Change:
        Modified driver to return 4 bytes data for all Dot3Stats OIDs.
      Impact:
        Resolve CQ11151 issue.

   4. Problem
       CQ11472 Unstable PLL output can lead to the chip lock-up when
       transitioning to D3 Cold.
       Extremely rare HW lock-up on 5751 devices when going into S3/S4
       that causes the 5751 to intermittently not be visible to the system
       after resuming from S3/S4.
      Cause:
        The lock-up occurs due to an unstable PLL output ,due to internal
        clock switching when PERST# is asserted when entering S3/S4.
      Change:
        Set hardware control register to values that prevent 
        Phase Lock Loop to power down & do Core clock switching.
      Impact:
         Higher power consumption in S3/S4 on the 5751 family of devices

  5. Problem:
        CQ11466 Add generic 5753 support to OEM desktop windows .inf files.
      Cause:
        New ID support request.
      Change:
        Added new ID support.
      Impact:
        Resolve CQ11466.

  6. Problem:
        CQ11453, CQ 11454 - BACS not working correctly under NT 4.
      Cause:
        A change in v7.92 of the driver to address CQ 9949 introduced a new
        problem that occurred only under NT 4 (not on W2K, XP, or W2K3).  The 
        new problem was that certain IOCTL calls down to the driver issued
        by BMAPI (on behalf of BACS) would fail, because the driver was no
        longer advertising support for private OIDs due to the change for 
        CQ 9949.  NT4 appears to block IOCTL calls for OIDs that are not 
        explicitly advertised.
      Change:
        Modified driver advertise all private OIDs in NDIS 4 and NDIS 3.1
        versions of the driver.  
      Impact:
        Resolve CQ11453 and 11454.  This will not break CQ 9949 because that
        issue was specific to newer operating systems (later than NT 4).

  7. Problem:
        CQ11487 - AMD64 inf is missing Checksum Offload, LargeSend, and Wirespeed options
      Cause:
        Advanced Option List was incomplete for AMD64 installation.
      Change:
        Added Advanced Option missing entries for AMD64 installation.
      Impact:
        Resolve CQ11487 issue.

  8. Problem:
        CQ11532 - Need to remove 5753F support.
      Cause:
        Unsupported device at this time.
      Change:
        Removed 5753F support from all install INF files.
      Impact:
        Resolve CQ11532 issue.

  9. Problem:
        CQ11521 - Configuring ASF in Windows XP32 using ASFConfig
        Corrupts Firmware on 5721 B1 (Flash  ST M45PE10)
      Cause:
        Driver device support for ST M45PE10 had incomplete command 
        sequence for Write of NVRAM Flash device.
      Change:
        Corrected Driver device support for ST M45PE10.
      Impact:
        Resolve CQ11521 issue.

 10. Problem:
        CQ11536 - Ports Status Activity on 5714 systems is not working.
      Cause:
        Driver device support for 5714 statistics was not updating correctly.
      Change:
        Corrected Driver device support for 5714 statistics.
      Impact:
        Resolve CQ11536 issue.







Version 8.10  November 23, 2004
----------------------------------------
  1. Problem:
        Add support for 5714, 5715, 5780 devices.
      Cause:
        New device support request 5714, 5715, 5780 devices.
      Change:
        Added driver and INF support for .
      Impact:
        None.



Version 7.92  November xx, 2004
----------------------------------------
  1. Problem:
        CQ11323 INF entry for one of OEM ID is incorrect.
      Cause:
        New ID support request entry had an error.
      Change:
        Corrected new OEM ID support.
      Impact:
        Resolve CQ11323.

  2. Problem:
        CQ11316 Change default value of LargeSendMinNumSeg to 2 for 5705 family.
      Cause:
        Better performance improvement.
      Change:
                Changed default value of LargeSendMinNumSeg to 2 for 5705 family.
      Impact:
        Resolve CQ11316.

  3. Problem:
        CQ11224 5753A1 12x12 with 256k flash (SA25F020) is not detected by AsfConfig.
                CQ11268 BACS does not show firmware version 
                CQ11269 System hangs on firmware upgrade
      Cause:
        New flash device was not yet supported by driver.
      Change:
        Added new flash device support.
      Impact:
        Resolve CQ11224, CQ11268, CQ11269.

  4. Problem:
        CQ11308 Cable Length Diagnostics reports cable length of zero.
      Cause:
        The change for CQ11226 was interfering with the diagnostics accesses of
        paged phy registers.
      Change:
        Changed the fix for CQ11226 to use diagnostic state information in
        order to not interfere with the cable length diagnostics.
      Impact:
        Resolve CQ11308.

  5. Problem:
        CQ9949 Blue Screen when 1cPrivateDevIOctl optional WHQL test script is run.
      Cause:
        The 1cPrivateDevIOctl test script was calling our private vendor specific
        OIDs with invalid information causing the driver to perform invalid hardware
        accesses.
      Change:
        Removed private OIDs from the structure returned by OID_GEN_SUPPORTED_LIST.
      Impact:
        Resolve CQ9949.

Version 7.91  November 05, 2004
----------------------------------------
  1. Problem:
        CQ11183 Adding support for two new OEM Mobile platforms.
      Cause:
        New ID support request.
      Change:
        Added new ID support.
      Impact:
        Resolve CQ11183.

  2. Problem:
        CQ11165 Add 5788 device ID's to support new OEM mobile project.
      Cause:
        New ID support request.
      Change:
        Added new ID support.
      Impact:
        Resolve CQ11165.

  3. Problem:
        CQ11132 OEM would like to default ChkSum Offload to TX
        ONLY on their 5701 products.
      Cause:
        New OEM customization support request.
      Change:
        Modified requested installation options for OEM products.
      Impact:
        Resolve CQ11132.

  4. Problem:
        CQ11209  and  CQ11210  OEM would like to new IDs for
        5703 and 5704 products; and wants them to default 
        ChkSum Offload to TX ONLY.
      Cause:
        New OEM device and customization support request.
      Change:
        Modified requested installation options for OEM products.
      Impact:
        Resolve CQ11209 and CQ11210.

  5. Problem:
        CQ11216 Wake On Link Option is not available in the
        Advanced Tab of Network Properties on some 5751M
        OEM laptop models.
      Cause:
        New feature request by OEM.
      Change:
        Enabled Wake On Link on 5751M OEM devices.
      Impact:
        Resolve CQ11216.

  6. Problem:
        CQ11226 Intermittent blue screen during BACS MII test on 5751.
      Cause:
        The gphy dll was not powered on during MII accesses from BACS.
      Change:
        Added gphy dll power up / power down code to MII access code
        used by BACS.
      Impact:
        Resolve CQ11226.
 


   Enhancement Request:
   ====================
  1. Request:
        CQ11104 Gpio2 pin should always be configured as an input pin for Shasta
        12x12 implementations.
      Change:
        Modified gpio control code to not change the state of gpio2 pin on
        Shasta 12x12 implementations.
      Impact:
        None.



Version 7.90  October 19, 2004
----------------------------------------
  1. Problem:
        CQ11088  Remove the ability to set speed and duplex on the
        OEM specific model embedded adapter.
      Cause:
        This OEM LOM device is hardwired for 1 gig speed only and speed options
        only cause problems for customers who tried to modify them.
      Change:
        Used 4 ID matched PCI IDs to give custom non modifiable speed option,
        only for this OEM LOM device installations.
      Impact:
        Resolve CQ11088.


  2. Problem:
        CQ10714 b57xp64.inf file needs to include 64-bit Windows 2003
        in the header for applicable OS
      Cause:
        Need to add Windows 2003-64 bit support comment in the install inf file.
      Change:
        Added Windows 2003-64 bit support comment in the install inf file.
      Impact:
        Resolve CQ10714 issue.

  3. Problem:
        Poor performance on 5751 BX parts.
      Cause:
        Excessive register accesses to the gphy power down code over MII interface
        was slowing down processing of interrupts.
      Change:
        Added additional state information in the gphy power down algorithm to
        further minimize MII interface accesses.
      Impact:
        Performance on 5751 BX parts should be comparable to driver revisions
        prior to 7.87.

   Enhancement Request:
   ====================
   1. Request:
        Certain gpio pins should not be modified by the device driver on
        LOM implementations.
      Change:
        Added code to preserve the state of the gpio pins in LOM implementations.
      Impact:
        None.


Version 7.89  October 11, 2004
----------------------------------------
  1. Problem:
        Poor performance on 5751 BX parts.
      Cause:
        Excessive register accesses to the gphy power down code over MII interface
        was slowing down processing of interrupts.
      Change:
        Modified gphy power down algorithm to minimize MII interface accesses.
      Impact:
        Performance on 5751 BX parts should be comparable to driver revisions
        prior to 7.87.

   Enhancements:
   =============
   1. Request: 
            Add PCI ID Support for new Broadcom Devices: 5753, 5753M, 5753F, and 5781
      Change:
            Added new PCI ID support to the XP64, XP32, AMD64, and NDIS4
            installation INF files.
      Impact:
            None.





Version 7.88  October 08, 2004
----------------------------------------
  1. Problem:
        CQ10965 Excessive power consumption on 5751 BX parts when cable is disconnected.
      Cause:
        A typo in the source code was causing the gphy power down code to execute in
        the system standby states but not in D0.
      Change:
        Corrected typo in source code.
      Impact:
        Resolve CQ10965 issue.

Version 7.87  October 07, 2004
----------------------------------------

 1. Problem:
        CQ10758 TPM - 5751 A4 LOM in OEM system with ASF Enabled fails S1 
        Waker/Dozer Test.
      Cause:
        This is due to the driver "resuming" from a sleep state and reading PHY registers 
        while the ASF FW could be simultaneously reading those registers. 
      Change:
        The fix to this problem is to gracefully stop the internal CPU before making any 
        PHY accesses in the "resume" code (the OID_SET_POWER handler).
      Impact:
        None.

 2. Problem:
        CQ10863 GEN_OID_RCV_ERROR is not incrementing when an error packet is received. 
      Cause:
        Original driver implementation did not increment this count when Oversized,  Undersized, 
        and Jabber packets were received.
      Change:
         Added count of Oversized,  Undersized, and Jabber packets to GEN_OID_RCV_ERROR
         inquiry code in the driver.
      Impact:
        Resolve CQ10863 issue.

 3. Problem:
        CQ10862 OEM would like to add 4 Vendor Specific OIDs for Receive Error counters. 
      Cause:
        New OEM support request.
      Change:
         Added four new OEM custom OIDs for inquiry of Receive error statistics.
      Impact:
        Resolve CQ10862 issue.

  4. Problem:
        CQ10991 Change the default minimum number of segments that can be offloaded
        by the hardware value from 8 to 2 on 575x Devices. 
      Cause:
        Performance testing shows that Large Send Offload operations can be improved on
        575x devices, by changing the value of this parameter from 8 to 2.
      Change:
        Modified driver to set recommended value to this parameter for 575x devices.
      Impact:
        Resolve CQ10991 issue.

  5. Problem:
        CQ10985 System cannot wake with Magic Packet using LAA MAC Network Address
        set with Advanced Options when ASF is also enabled.
      Cause:
        The driver shutdown handler did not update the WOL MAC Network Address with 
        custom LAA values in the case of ASF enabled condition.
      Change:
        Modified driver to set custom LAA values accordingly when Windows is doing shutdown.
      Impact:
        Resolve CQ10985 issue.

  6. Problem:
        CQ10965 Excessive power consumption on 5751 BX parts when cable is disconnected.
      Cause:
        The driver was not powering down the GPHY DLL when it is not needed.
      Change:
        Modified driver to power down the GPHY DLL when it is not needed.
      Impact:
        Resolve CQ10965 issue.

  7. Problem:
        CQ10350  5750 ASF heartbeat PET stopped when system in S4 state, or after
        wake from same S4 state.
      Cause:
        The driver to ASF handshake and control register sharing needed update for
        proper ASF operation in Standby mode or after wake from Standby.
      Change:
        Updated the driver to do proper ASF handshake and control register sharing
        for resume of ASF PET operation.
      Impact:
        Resolve CQ10350 issue.





Version 7.86 August 23, 2004
---------------------------------

 1. Problem:
        CQ10816  CHKINF fails in HCT12 for XP-SP2 installation.
      Cause:
        An install section was missing in the b57win32.inf v7.85 INF file.
      Change:
        Added the missing install section.
      Impact:
        Correct CQ10816 issue.



Version 7.85 August 19, 2004
---------------------------------

 1. Problem:
        CQ10748 The "LargeSendOffload" registry key was being mistakenly added to
        the Windows 2000 registry. This key should not be added to the W2K registry
        because of serious problems with LSO feature in the original release of W2K
        (before the release of the W2K service packs). 
        This issue is applicable to the unified install inf file b57win32.inf and only one 
        specific OEM with PCI SubSystem ID of 0x1028.
        Prior released versions of b57win32.inf that had this installation issue for OEM 
        with SubSystem ID of 0x1028 were 7.76 to 7.84.
      Cause:
        This key was originally present only in the Windows XP INF. However, when
        the Windows 2000 and Windows XP INF files were merged into a single INF,
        the INF was not modified so that this key would only be added on Windows XP
        and not added for Windows 2000. 
      Change:
        The unified Windows 2000 and Windows XP INF was modified to not add
        LargeSendOffload key to the registry when the driver is installed on 
        Windows 2000.
      Impact:
        No side effects.

2. Problem:
        CQ10781:  OEM System with 57xx PCI-E Device does NMI (blue screen) after
        PXE boot from Venturcom BXP PXE server.
 Cause:
        The root cause of the problem is that the Venturcom BXP PXE Server does not
        shutdown the UNDI driver after PXE boot has completed.
        This problem does not occur with PXE server products from other vendors.
        The 7.84 driver detects during initialization that the LAN device has not been
        shutdown properly by the PXE/UNDI software, and it attempts to gracefully
        workaround this by resetting the device.
        During this attempt to reset the 57xx PCI-E device, the PCI-E link flaps
        (link down/up) which causes an "unexpected link change" on the chipset side.
        Depending on the chipset configuration, this can lead to an NMI.
        This problem only occurs on PCI-E devices, and does not occur on standard PCI devices.
      Change:
        Modified the device driver to gracefully reset 57xx PCI-E devices without causing the
        PCI-E link to go down/up,  in the case that the PXE UNDI driver had not been halted
        at the time of  Windows initialization of the device driver.
      Impact:
        None



Version 7.84 August 05, 2004
---------------------------------

 1. Problem:
        CQ10705  A NMI was observed when a Windows "shutdown" occurred on a  OEM 
        5751M LOM based platform running 10mb, with WOL disabled, no ASF enabled.  The
        problem could only occur if WOL was disabled, and the system was running at 10mb.
      Cause:
        The original driver Shutdown sequence (with no WOL and no ASF) powered off the GPHY
        prior to disabling device TX and RX blocks.  The GPHY was powered-down to save 
        power. Since the GPHY was disabled, the clock to certain MAC registers was intended
        to be switched to a slower clock derived from the core clock.  However, a bug was 
        recently discovered in this logic which could lead to those registers having a very slow
        clock (or no clock) in this situation.  This in turn, could lead to scenarios where read transactions 
        to those registers was not completed in a timely manner.  This could cause the chipset to 
        assert an NMI after 10ms if the read was not yet completed.  In the failing case, it was 
        observed that the read did complete, but it took up to 21ms to complete..
      Change:
        Modified driver to first disable the device RX and TX blocks and then power off the PHY
        if no WOL and ASF were enabled.
      Impact:
        No side effects.


Version 7.83 August 05, 2004
---------------------------------

   1. Problem:
        CQ10672  LAN driver yellow bang, or TPM failure, during focused LAN driver 
         halt/re-initialize testing.
      Cause:
        The driver could write to a new NVRAM control register in 5751 HW without
        holding the NVRAM lock.  This coud cause a problem if the TPM function and 
        the LAN driver both simultaneously tried to access NVRAM.  This problem is
        highly timing dependent.  Under normal circumstances, the only time that the 
        driver acceses NVRAM is when loading the driver.
      Change:
        Re-ordered some code fragments to ensure that Nvram control register
        in question is only accessed while the driver is holding the NVRAM lock.  
      Impact:
        This driver is compatible with TPM.


   2. Problem:
        CQ10532  Sychronize AMD 64 device support with XP 32.
      Cause:
            The AMD 64 install inf file did not have OEM PCI ID match for supported device.
      Change:
        Added OEM PCI ID device support to AMD 64 inf install file. 
      Impact:
        Fix CQ10532 issue.



Version 7.82 July 28, 2004
---------------------------------
   1. Problem:
        CQ10529  B57dtect.dll  had wrong File Version 1.0.0.0 instead of 1.12.0.0
      Cause:
            The DLL resource file for build had wrong string defined for File Version. 
      Change:
        Corrected  the DLL resource file string definition for File Version.  
      Impact:
         Fix CQ10529 issue.

   2. Problem:
        CQ10532  Synchronize b57amd64.inf with b57win32.inf installation files.
      Cause:
            Original limited support of AMD 64 platform. 
      Change:
        Increased Windows AMD 64 device support to the same level as Windows XP 32.  
      Impact:
         Fix CQ10532 issue.

   3. Problem:
        CQ10543  OEM LOM shows "Fiber" in adapter properties.
      Cause:
            Original name requested by OEM; which has now requested to remove Fiber word. 
      Change:
        Change network adapter device name to string supplied by OEM.  
      Impact:
         Fix CQ10543 issue.

   4. Problem:
        CQ10576  Broadcom Server CD v7.6.3\b57dtect.dll displays wrong copyright date.
      Cause:
            The DLL released in this CD and v7.81 driver was the same binary as 7.80 which had old copyright dates.
      Change:
        Released new DLL with proper copyright date.  
      Impact:
         Fix CQ10576 issue.

   5. Problem:
        CQ10575 Broadcom Server CD v7.6.3\b57dtect.dll - wrong DLL file version.
      Cause:
            The DLL released in this CD and v7.81 driver was the same binary as 7.80 which had old file version.
      Change:
        Released new DLL with proper DLL version.  
      Impact:
         Fix CQ10575 issue.

   6. Problem:
        CQ10578  Broadcom 7.81 AMD64 INF has .CAT file section commented out.
      Cause:
            Original version of AMD 64 release.
      Change:
        Uncommented .CAT file reference.  
      Impact:
         Fix CQ10578 issue.

   7. Problem:
        CQ10597  Add OEM new projects P1 & P1_C PCI 4 ID match.
      Cause:
            New OEM device support.
      Change:
        Added new support.  
      Impact:
         Fix CQ10597 issue.

   8. Problem:
        CQ10539  Broadcom 5788 Device Performance decreased with latest driver compared to previous driver.
      Cause:
        Driver 5788 special dummy register reads at the start of ISR, these were only needed for 5788 A0 chip.
      Change:
        Removed 5788 A0 support, support can be restored by defining POSTED_READ_PATCH in sources.  
      Impact:
        Fix CQ10539 issue.

   9. Problem:
        CQ10671  OEM LOM Design Wake On Link Change option does not work; while WOL by IP Ping & MP works OK.
        This problem does not occur on Broadcom evaluation NICs.
      Cause:
        Driver did not set Wake On Link Change option to hardware on one of code paths.
      Change:
        Verified driver now sets Wake On Link Change option whenever the advanced property has selected it.  
      Impact:
         Fix CQ10671 issue.

   10. Problem:
        CQ10681  OEM request to change default Flow Control setting to disable.
      Cause:
        New request.
      Change:
        Change OEM default advanced option setting.  
      Impact:
         Fix CQ10681 issue.

   11. Problem:
        CQ10691 Running Chariot with 1Byte buffer size causes the interface to hang.
        This problem only occurs when an application attempts to transmit a packet 
        that contains a huge number (e.g. hundreds) of very small buffer fragments
        and that it would be highly unusual for a real application to do this. 
        This problem was found when using an artificial test scenario that intentionally
        forced this condition.
      Cause:
        The fix for CQ9262 related to highly fragmented transmit packet buffers
        was implemented in the multi-processors code path but was not implemented 
        in the single processor code path.
      Change:
        Implemented fix for CQ9262 in the single processor code path.
      Impact:
        Fix CQ10691 issue.



Version 7.81 July 1, 2004
---------------------------------
   1. Problem:
        CQ10473   b57xp32.cat was referenced in the v7.80 b57win.inf file.
      Cause:
            Unified inf had uncorrected reference to b57xp32.cat instead of b57win32.cat file. 
      Change:
        Corrected digital signature file reference to b57win32.cat file.  
      Impact:
         Fix CQ10473 issue.

   2. Problem:
        CQ10474 Add new support for OEM product.
      Cause:
            New support request. 
      Change:
        Added new device support.  
      Impact:
         Fix CQ10474 issue.

   3. Problem:
        CQ10475 Add new support for OEM AMD-64 products.
      Cause:
            New AMD-64 support request. 
      Change:
        Added new OEM AMD-64 device support.  
      Impact:
         Fix CQ10475 issue.

   4. Problem:
        CQ10486 Incorrect comments in OEM  inf  header.
      Cause:
            Missing Windows2000 Support indication. 
      Change:
        Added Windows2000 Support indication.  
      Impact:
         Fix CQ10486 issue.

   5. Problem:
        CQ10489  b57xp64.inf needs current year in copyright date (2001 - 2004)
      Cause:
            Original release date. 
      Change:
        Modified copyright dates.  
      Impact:
         Fix CQ10489 issue.

   6. Problem:
        CQ10491 OEM Server unified INF does not have proper OEM copyright notice.
      Cause:
            Original release version. 
      Change:
        Modified copyright notice.  
      Impact:
         Fix CQ10491 issue.

   7. Problem:
        CQ10502 Windows reports stop error 0x0000007f when using .Net
        Framework 1.1
      Cause:
        The kernel double faulted in driver's send routine due to kernel stack
        space being exhausted.
      Change:
        Modified send routine to use less stack space.
      Impact:
         Driver uses 2k less stack space when processing packet sends vs.
         previous versions of the driver.




                

Version 7.80 June 19, 2004
---------------------------------
   1. Problem:
        CQ10421 5751-B0 NIC not functioning in under Chariot stress condition
      Cause:
            Failure under stress that could occur on multi-proc systems, was introduced 
        with change made in v7.76 to the driver interrupt handler code. 
        The change in v7.76 resulted in a race condition where under rare circumstances
        on a multi-proc system, interrupts could be left disabled when exiting the
        interrupt handler
      Change:
        Fixed a race condition in the interrupt handler by changing the order of two operations.  
      Impact:
         Fix CQ10421 issue.

   2. Problem:
        CQ10427   Unified INF has incorrect BaseDriverFilerVersion number.
      Cause:
            BaseDriverFileVersion parameter was not updated when release was made.
      Change:
        Updated BaseDriverFileVersion with correct number.
      Impact:
         Fix CQ10427 issue.


Version 7.79 June 17, 2004
---------------------------------
   1. Problem:
            CQ10318 5750 based adapters consume more power when configured for
            10mb WakeOnLan vs. 100mb WakeOnLan.
      Cause:
            The clock control register was not programmed correctly when the
            device is configured for 10mb WakeOnLan during system shutdown.
      Change:
            Corrected programming of the clock control register for 5750
            based adapters for 10mb WakeOnLan during system shutdown.
      Impact:
            Lower power consumption for 5750 devices configured for 10mb WakeOnLan.

   2. Problem:
            CQ10167 OEM Request for specific device name with PCI 4 ID match.
      Cause:
            New OEM request.
      Change:
            Added new support for OEM request.
      Impact:
            Resolve CQ10167.

   3. Problem:
            CQ10369 OEM Request to add support for four new devices with 
            PCI 4 ID match.
      Cause:
            New OEM request.
      Change:
            Added new support for OEM request.
      Impact:
            Resolve CQ10369.

   4. Problem:
            CQ10391 Ndis drivers does not pass WHQL WakeOnLan tests on 5702 adapters.
      Cause:
            Fix for CQ10032 which only applies to 5750 based controllers was
            being applied to non-5750 controllers.
      Change:
            Qualified fix for CQ10032 to apply to only 5750 based controllers.
      Impact:
            Resolve CQ10391.

   5. Problem:
            CQ10231 Put support for Junction NIC back into Windows drivers.
      Cause:
            The .inf need to be updated. This was not done for XP64 and AMD64.
      Change:
            Modified the XP64 and AMD64 .inf to support the new device.
      Impact:

   6. Problem:
            Add support for Capacitive Coupling
      Cause:
      Change:
            Implemented support for Capacitive Coupling.
      Impact:
            Support for this is required in the boot code and diagnostics.

Version 7.78 June 10, 2004
---------------------------------
   1. Problem:
            CQ10317 Using switch -hreset to perform reset adapter continuously overnight, 
            system would lock up
      Cause:
            There is an extra write to the T3_PCI_PM_STATUS_CTRL_REG in LM_SetPowerState(). 
            This problem was introduced while resolving CQ10032 in driver 7.77
      Change:
            Removed the extra write.
      Impact:
            None.

   2. Problem:
            CQ10336 System freezes when changing advanced driver properties on Intel PDK 
            PCI-E Slots
      Cause:
            There is an extra write to the T3_PCI_PM_STATUS_CTRL_REG in LM_SetPowerState(). 
            This problem was introduced while resolving CQ10032 in driver 7.77
      Change:
            Removed the extra write.
      Impact:
            None.

   3. Problem:
            CQ10318 5750 based adapters consume more power when configured for
            10mb WakeOnLan vs. 100mb WakeOnLan.
      Cause:
            The clock control register was not programmed correctly when the
            device is configured for 10mb WakeOnLan during system standby or
            hibernate.
      Change:
            Corrected programming of the clock control register for 5750
            based adapters for 10mb WakeOnLan.
      Impact:
            Lower power consumption for 5750 devices configured for 10mb WakeOnLan.


Version 7.77 June 8, 2004
---------------------------------

   1. Problem:
            CQ9033 Flow control does not work consistantly.
      Cause:
            When the phy is initially powered on, the default behavior
            is to not advertise flow control.
      Change:
            Restart autoneg when flow control is configured to notify
            the link partner that flow control is desired.
      Impact:
            None.


   2. Problem:
            CQ10280 5700 b2 and b3  fails to pass traffic.
      Cause:
            The DPC routine is broken.
      Change:
            Restored the old DPC routine, with the OEM suggested fix to resolve
            CQ10151 added.
      Impact:
            None.


   3. Problem:
            CQ10275 Large Send Offload and IPMI does not co-function on 5721.
      Cause:
            LSO is turned off when ASF is enabled. This was necessary for the 5705
            device which implemented LSO in f/w.
      Change:
            Since LSO is done in h/w, it is not necessary to disable LSO 
            when ASF is running on 575x and 572x devices.
      Impact:
            None.

   4. Problem:
      Cause:
            CQ10032 System wakes up immediately after entering standby.
            
      Change:
            Set bit 26 of Mac control mode register to prevent more PME events from 
            the device when the OS has already acknowledged the PME event.
      Impact:
            None.


Version 7.76 June 3, 2004
---------------------------------

   1. Change Request:
            CQ10231 Put support for Junction NIC back into Windows drivers.
      Cause:

      Change:
            Reinstated support for Junction NIC back into Windows drivers.
      Impact:

   2. Change Request:
            Merge the winXP and win2k inf.
      Cause:
            Requested by MSFT for logo certification.
      Change:
            There is now a single .inf for winXP and win2k. This .inf is called 
            b57win32.inf. This distribution still includes the old .inf, so to
            test, instruct windows to use the win32 inf during driver install.
      Impact:
            None.
   
   3. Problem:
            CQ10151 Server ASRs when running IXIA stress test. The machine appears locked up
            under heavy network load.
      Cause:
            The DPC routine can run for an extended period if the NIC interrupt rate 
            is high.
      Change:
            Cap the amount of time the DPC routine can run. The DPC routine was
            aso rewritten to improve clarity.
      Impact:
            None.

   4. Problem:
            CQ10034 Runt packets transmitted on 5700BX are not padded with zeros.
      Cause:
            Archaic workaround code for the 5700AX parts was incorrectly padding
            transmit packets for 5700BX with garbage.
      Change:
            Removed workaround code since 5700AX parts were never released into
            production.
      Impact:
            None.


Version 7.75 May 26, 2004
---------------------------------

   1. Problem:
            CQ10033   5700 B2 LOM with v1.3 Bootcode does not pass traffic
            when v7.73 driver is used.
      Cause:
            The older 5700 v1.3 Bootcode did not implement shared memory 
            driver-bootcode interface; so the driver would not recognize nor 
            initialize the PHY.
      Change:
            Added a fallback case to driver; so that in case of older bootcodes
            the driver would initialize the PHY for proper operation.
      Impact:
            Fix CQ10033 issue.

   2. Problem:
            CQ9992 5704 nic may draw VAUX during device initialization when
            only one port has been enabled.
      Cause:
            Incorrect programming of GPIO2 when only one port has been enabled.
      Change:
            Corrected programming of GPIO2.
      Impact:
            5704 nic will not draw from VAUX during device initialization.

   3. Problem:
            CQ10097 OID_GEN_RCV_NO_BUFFER or OID_GEN_RCV_ERROR
            statistics not incremented when packets are dropped.
      Cause:
            OID_GEN_RCV_NO_BUFFER was getting the count from 
            lower module's no more receive buffer descriptors.
      Change:
            Modified OID_GEN_RCV_NO_BUFFER to get count from 
            lower module's receive overrun counter.
      Impact:
            Fix CQ10097 issue.

   4. Problem:
            CQ10073  OEM requested to add 4 PCI ID match support for 5751F 
      Cause:
            New support for 5751F installations.
      Change:
            Added new support for 5751F installations. 
      Impact:
            Fix CQ10073 new support request.

   5. Change Request:
            CQ10165  OEM Request to add 4 ID support to IA64 driver.
      Cause:
            New support for OEM installations.
      Change:
            Added new support for OEM IA64 installations. 
      Impact:
            Fix CQ10165 new support request.

   6. Change Request:
            CQ10167  OEM Request to add 4 ID support to XP32 and NDIS5 Drivers.
      Cause:
            New support for OEM installations.
      Change:
            Added new support for XP32 and NDIS5 Drivers.
      Impact:
            Fix CQ10167 new support request.

   7. Change Request:
            CQ9791  Add support for WakeOnLink for requested OEMs.
      Cause:
            New support for OEM.
      Change:
            Added new support.
      Impact:
            Implemented CQ9791 change request.

   8. Change Request:
            CQ10193 Disable embedded cpu for 5750/5721 A3 revision parts.
      Cause:
            Hardware errata for 5750/5721 A3 revision parts.
      Change:
            Added cpu halt routine in device initialization for affected parts.
      Impact:
            Embedded cpu for affected parts will be halted.

   9. Problem:
          CQ9960  System will not go to standby properly when a 5705 is 
          linked at 10mb.
      Cause:
          When the 5705 is linked at 10mb, the core clock speed is slowed
          to reduce power consumption. When the device driver programs
          the 5705 for Wake On Lan, the 5705 is not programmed properly
          due to the reduced clock speed.
      Change:
          Changed the Wake On Lan configuration code to ensure that the
          core clock speed is set to normal before configuring the part
          for Wake On Lan.
      Impact:
          Fix CQ9960 issue.

   10. Problem:
            CQ10106  System running NT4 may report IERR when saving a speadsheet
            from a Win95/Win98 Client.
      Cause:
            The operating system was presenting zero length buffers to the
            ndis driver for transmission.
      Change:
            Added scan for zero length buffers and coalesce transmit buffers
            that contain zero length buffers.
      Impact:
            Fix CQ10106 new support request.

   11. Change Request:
            CQ8102  Log message to event log when Ethernet@Wirespeed is
            in use.
      Cause:
            New request from OEM.
      Change:
            Added check for Ethernet@Wirespeed status to event logger routine.
      Impact:
            Fix CQ8102 new support request.



Version 7.74 May 20, 2004
---------------------------------

   1. Problem:
            CQ9812   Fiber NIC 5701 has intermittent connectivity at startup.
      Cause:
            Unsuccessful negotiation at startup with fiber switch.
      Change:
            Increased loop attempts to negotiate with fiber switch from two to
            four times and also added initialize of negotiation state machine
            prior to actual negotiation attempt.
      Impact:
            Fix CQ9812 issue.

   2. Change Request:
            Re: CQ9955 Restore support for 5751M devices.
      Change:
            Removed commented inf support entries.
      Impact:
            Restored support for 5751M devices.



Version 7.73 April 29, 2004
---------------------------------
   1. Problem:
            CQ9997 ASF 2.0 enabled will not allow system to wake from standby.
      Cause:
            The driver to ASF handshaking does not work as expected when the device
            power state is changed. Specifically, the "last driver state" is not set
            to WoL when it should be. Also, in 7.72, it is possible for the firmware 
            to use the WoL pattern table before it is completely setup by the driver.
      Change:
            Fixed the handshaking.
      Impact:



Version 7.72 April 28, 2004
---------------------------------

   1. Problem:
            CQ9989 5751 LOM link is disconnected when changed speed.
      Cause:
            The driver change to correct CQ9124 and CQ9033 Flow Control 
            problem did not consider forced speed settings and caused the
            link to disconnect.  Backed out the change for CQ9124 and CQ9033
            until full regression testing has been done. Issues CQ9124 and CQ9033
            will be resolved on a later driver release.
      Change:
            Commented the change for fix of CQ9124 and CQ9033 issues.
      Impact:
            Fix CQ9989 issue.



Version 7.71 April 23, 2004
---------------------------------

   1. Problem:
            CQ9955 Need to remove support for 5751M devices in Release 7.5 on ALL drivers.
      Cause:
            The 5751M device has not yet been fully tested.
      Change:
            Commented inf support entries.
      Impact:
            Fix CQ9955 issue.

   2. Problem:
            CQ9872 Not able to install 57xx driver for NIC on Win-Me
      Cause:
            The Windows 2000 installation inf file used was bigger than 64K bytes.
            This is a Windows 98, 98SE, Windows Me install inf file limitation.
      Change:
            Created a new Win98Me file folder that contains new b57w9x.inf and driver
            files for use in Win98, Win98SE, WinMe Operating Systems.
      Impact:
            Fix CQ9872 issue.

   3. Problem:
            CQ9931 Network Properties for OEM Desk Top models should be limited.
      Cause:
            Original implementation.
      Change:
            Modified installation inf files to comply with new OEM request.
      Impact:
            Fix CQ9931 issue.

   4. Problem:
            CQ9936  OEM Friendly name is no longer displayed on the Event Viewer Logs.
      Cause:
            The requested friendly name string was too long and it caused Windows to use
            it's own internal name for event logs of 57xx device.
      Change:
            Reduced the OEM friendly name by removing  Controller.
      Impact:
            Fix CQ9936 issue.

   5. Problem:
            CQ9950 Release 7.70 NT4 driver did not support 5705M device.
      Cause:
            New device support.
      Change:
            Added 5705M install support for 7.71 NT 4 release.
      Impact:
            Fix CQ9950 issue.

   6. Problem:
            CQ9943 Connection to BMC does not resume after disabling adapter in OS.
      Cause:
            New driver to ASF firmware handshake needed to be implemented.
      Change:
            Added new driver to ASF firmware handshake implementation.
      Impact:
            Fix CQ9943 issue.



Version 7.70 April 19, 2004
---------------------------------

   1. Problem:
            CQ9124 Flow control is not working with 5750 A0 on NT4
            CQ9033   Flow control negotiation fails
      Cause:
            On initial driver load, the flow control capability was not advertised
            to switch link partner.
      Change:
            Added a PHY control write to during device initialization; to advertise
            flow control capability
      Impact:
            Fix CQ9124 and CQ9033 issues.

   Enhancements:
   =============
   1. Request: 
            CQ9835 Change behavior of CLKRUN# for 5705 so CLKRUN# is asserted when link
            is present and deasserted when link is not present.
      Change:
            Modified link detection code to manipulate the CLKRUN# signal with respect
            to the link status reported by the phy.
      Impact:
            Fix CQ9835

   2. Request: 
            CQ9306 Add ability to disable TCP/IP options task offload support.
      Change:
            Added new bit definitions to UserTaskOffloadCapDisable that can be used
            to disable TCP/IP options offload support.
      Impact:
            Fix CQ9306

   3. Request: 
            CQ9886 OEM request to add new PCI 4 ID checking support for Win2k and XP.
      Change:
            Added new requested PCI 4 ID support.
      Impact:
            Fix CQ9886

   4. Request: 
            CQ9887 5705 and 5750 have higher than expected BER rates.
      Change:
            Programmed the phy on affected devices to adjust the bias current of the
            ADC on the phy.
      Impact:
        Fix BER issue.


Version 7.69 April 14, 2004
---------------------------------

   1. Problem:
            CQ9613 Set power mode failed in TestApp.exe (Broadcom's internal test
            program needed to test Reverse Nway and Power Save Mode operations).
      Cause:
           A spin lock acquired by the driver when configuring the hardware for 
           power saving mode may not be released, causing the OS to lock up. This 
           lock up only occurred when the driver was configured for power saving mode
           and the EEPROM "Power Save Mode" option (secfg option 38) was disabled. 
      Change:
            The driver was modified to release the spin lock for all code paths in
            the T3_OID_SET_POWER_MODE OID handler.
            This same problem was also detected in the T3_OID_PHY_ON OID handler,
            and so the problem was fixed here also.
      Impact:
            Fix CQ9613 issue.

   2. Problem:
            CQ9573  5751 LOM stops send out ASF alerts after  40 seconds while in a S3 State.
            CQ9788  5704 Connection to BMC fails in Window sleep states and Shutdown.
      Cause:     
            The driver to ASF handshake needed update to resume ASF operation in Standby mode.
      Change:
            Updated the driver to do proper ASF handshake for resume of ASF operation.
      Impact:
            Fix CQ9573 and 9788 issues.

   3. Problem:
            CQ9726 OEM Enhancement request to make a few options preset to defaults
            and not able to change in XP.
      Cause:  
            Original installation implementation.
      Change:
            Updated XP installation inf file to handle OEM enhancement request.
      Impact:
            Fix CQ9726 issue.

   4. Problem:
            CQ9543 Driver version 7.68 had full Network Properties for OEM mobile customer;
                where it should be have been limited to 8021.p , Flow Control, Speed, WakeOnLan choices.
      Cause:  
            Original installation implementation.
      Change:
            Updated installation inf files to support OEM mobile customer request.
      Impact:
            Fix CQ9543 issue.

   5. Problem:
            CQ9809 Incorrect friendly name for OEM 575x adapters on NT 4.0
      Cause:  
            Original installation implementation.
      Change:
            Updated installation NT 4.0 inf file to display requested OEM friendly name.
      Impact:
            Fix CQ9809 issue.

   6. Problem:
            CQ9816 WHQL 2c_OffloadCheckSum test is failing.
      Cause:
            Fix for CQ9711 is causing the NIC to drop a packet after adapter restart.
      Change:
            Modified change for CQ9711 so restart of autoneg will only occur if
            Ethernet@Wirespeed is disabled but the current link was achieved using
            Ethernet@Wirespeed.
      Impact:
            Fix CQ9816 issue.

   7. Problem:
            CQ9342 High CPU load and sluggish system behavior with BASP and heavy traffic.
      Cause:
            Looping inside the DPC handler for performance reasons was causing excessive
    CPU utilization.
      Change:
            Reduced the number of loops in the DPC routine from 100 to 20.
      Impact:
            Fix CQ9342 issue.


Version 7.68 April 02, 2004
---------------------------------

   1. Problem:
            CQ9446  ASF stops responding after disabling/enabling ASF in Windows for 575x.
      Cause:  
            The driver to ASF handshake needed update to resume ASF operation.
      Change:
            Updated the driver to do proper ASF handshake for resume of ASF operation.
      Impact:
            Fix CQ9446 issue.

   2. Problem:
            CQ9706  5703 Fiber NIC intermittently loses connection with a Cisco6509 when
            system is rebooted or device is disabled and then enabled.
      Cause:  
            The driver link timer needed increase to 802.3z specification and attempted one time
            to autonegotiate.
      Change:
            Updated the driver link timer and increased driver autonegotiate attempt from one to 
            two times.
      Impact:
            Fix CQ9706 issue.

   3. Problem:
            CQ9748 Error in INF install section for PCI-Express NIC
      Cause:  
            Incomplete inf install section for OEM.
      Change:
            Added missing inf install section.
      Impact:
            Fix CQ9748 issue.

   4. Problem:
            CQ9294  Change string display for 5788 to "Broadcom NetLink (TM) Gigabit Ethernet"
      Cause:  
            Original inf information.
      Change:
            Change to new friendly name.
      Impact:
            Fix CQ9294 issue.

   5. Problem:
            CQ9698  57xx: Create OEM branded AMD64 driver.
      Cause:  
            New feature.
      Change:
            Added requested branded AMD64 driver for OEM.
      Impact:
            Fix CQ9698 issue.

   6. Problem:
            CQ9553  ASF 2.0 In Standby, Shutdown or Hibernate will stop sending PETS.
      Cause:  
            The Driver to ASF handshake needed to be updated with latest ASF implementation,
      Change:
            Updated Driver to ASF handshake.
      Impact:
            Fix CQ9553 issue.

   7. Problem:
            CQ9759  Add three new PCI subsys id's for OEM using 5751 silicon.
      Cause:  
            New Support for OEM.
      Change:
            Added three new PCI IDs for support of 5751 device installation.
      Impact:
            Fix CQ9759 issue.

   8. Problem:
            CQ9711  Unable to disable Ethernet@Wirespeed
      Cause:  
            Incorrect phy initialization sequence when Ethernet@Wirespeed is disabled.
      Change:
            Corrected phy initialization sequence.
      Impact:
            none.

   9. Problem:
            CQ9307  Single registry key for speed/duplex option for certain OEMs.
      Cause:  
            New Support for OEM.
      Change:
            Added support for new single key speed/duplex options.
      Impact:
            none.

   10. Problem:
            CQ9481, CQ9701  5751: Share traffic/link LED not working correctly in XP 
            (XP driver not changing LED mode)
       Cause:
            LED mode is not programmed properly
       Change:
            Programmed the LED as requested. The LED setup code now mimics the Linux 
            implementation.


Version 7.67 Mar 19, 2004
---------------------------------

   1. Problem:
            CQ9548 WinXP 5701A3 fails PCI Compliance test in HCT 12.0 Beta 2 Test Kit
      Cause:  
            The driver would always assume that OOB WOL was enabled and therefore would
            always set the PME# bit in pci config space.
      Change:
            Changed driver to read OOB WOL configuration directly from eeprom.
      Impact:
            Fix CQ9548 issue.

   2. Problem:
            CQ9579 Add two ID VID/DID PCI match for OEM.
      Cause:  
            Customer request.
      Change:
            Updated driver install inf file.
      Impact:
            Fix CQ9579 issue.

   3. Problem:
            CQ9627 %OEM2_DEV1% name will be displayed when generic system ID is installed.
      Cause:  
            Name string not initialized in installation inf file.
      Change:
            Updated driver install inf file.
      Impact:
            Fix CQ9627 issue.

   4. Problem:
            CQ9666 Release notes states we support Win95/OSR2
      Cause:  
            Original Release notes.
      Change:
            Updated this Release.txt file.
      Impact:
            Fix CQ9666 issue.

   Enhancements:
   =============
   1. Request: 
            Add registry key to optionally force CLKRUN# on mobile platforms.
      Change:
            Added registry key to support forcing CLKRUN# on mobile platforms.
      Impact:
            None.


Version 7.66 Mar 12, 2004
---------------------------------

   1. Problem:
            CQ9603 WinXP .inf missing line for OEM customer. 
      Cause:  
            Incomplete driver installation inf file.
      Change:
            Corrected driver install inf file.
      Impact:
            Fix CQ9603 issue.


Version 7.65 Mar 11, 2004
-----------------------------

   1. Problem:
            CQ9148 No link LED at Gig on 5751 LOM.
            CQ9481 5751: Share traffic/link LED not working correctly in XP.
            CQ9549 5751-A1: Driver overwrites LED settings from NVRAM.
      Cause:  
            The Windows driver was not keeping Firmware initialized LED settings.
      Change:
            Modified driver to honor the Firmware set LED controls.
      Impact:
            Fix CQ9148, CQ9481, and CQ9549 issues.

   2. Problem:
            CQ9435 Jumbo frames was not functioning in drivers v7.57 to v7.60
      Cause:  
            The driver was not keeping Advanced Option Jumbo Frame size as user specified.
      Change:
            Modified driver to honor the user input for Jumbo Frames.
      Impact:
            Fix CQ9435 issue.

   3. Problem:
            CQ9551 5751-A1:  Using "->CfgWr0" cycles rather then "->MWr32" for setting "D3 Hot" 
      Cause:  
            Driver performed Configuration Writes for all 57xx devices for this control operation.
      Change:
            Modified driver to use Memory Writes for 575x devices and Configuration Writes for all other devices.
      Impact:
            Fix CQ9551 issue.

   4. Problem:
            CQ9603 WinXP .inf missing line for OEM customer. 
      Cause:  
            Incomplete driver installation inf file.
      Change:
            Corrected driver install inf file.
      Impact:
            Fix CQ9603 issue.

   5. Problem:
            CQ9129 Adapter stops transmitting packets on ia64 and amd64 systems with more
            than 4gb of memory.
      Cause:  
            On 64-bit operating systems it is possible to get transmit buffers from
            the upper layers that span a 4gb boundary. The 57xx family of adapters are
            not able to dma buffers that span a 4gb boundary and therefore the read
            dma engine will hang.
      Change:
            Added code to double buffer transmit buffers that span a 4gb boundary
            for all 57xx adapters.
      Impact:
            Fix CQ9129 issue.



Version 7.64 Mar 5, 2004
-----------------------------
 
   1. Problem:
            CQ9571 Version 7.63 binaries contains incorrect file version information.
      Cause:  
            The 7.63 binaries were built incorrectly.
      Change:
            Recompiled with correct file version information.
      Impact:
            None.

   2. Problem:
            The ASF firmware is not able to access nic memory when WOL is enabled on
    575X adapters.
      Cause:  
            The driver did not properly configure the Mac Control Mode register when
            WOL is enabled on a 575X.
      Change:
            Corrected WOL code to properly configure Mac Control Mode register on
            575X.
      Impact:
            None.

   3. Problem:
            CQ9505 Add option in advance options to allow disable of warning and informational logs
            for a specific OEM customer's 4 part PCI ID set.
      Cause:  
            Original driver implementation.
      Change:
            Add new inf entry for OEM 4 part PCI ID and also modify driver to look for and
            handle new Warning/Information Advanced Options.
      Impact:
            Fix CQ9505




Version 7.63 Mar 1, 2004
-----------------------------
 
   1. Problem:
            Performance is not optimized for TCP/IP traffic. 
      Cause:  
            TCP/IP data throughput is decreased by 5% when receive frame TCP payload
            is not aligned on a 64-byte cache line boundary. This occurs on both x86
            and AMD platforms.            
      Change:
           Changed the internal offset in receive buffers to align the TCP payload on
           a 64-byte boundary. Except for 5701/PCI-X and 5700/PCI-X, the default internal
           receive buffer offset for all NIC's is now 10-bytes. Assuming 54-bytes are used for
           the MAC, IP and TCP headers, a 10-byte offset will put the TCP payload
           on a 64-byte boundary. The internal receive buffer offset for 5701/PCI-X and 5700/PCI-X
           NIC's will always be forced to 0 and cannot be overridden.

      Impact:
          Improved receive performance with TCP/IP frames. 
  


Version 7.62 Feb 25, 2004
-----------------------------

   1. Problem:
 
Missing support for Shasta A1 various device PCI IDs.

      Cause:  
         
Missing support for Shasta A1 various device PCI IDs.

      Change:

    Changed driver installation inf file to support added IDs.

      Impact:

None.


Version 7.61 Feb 25, 2004
-----------------------------

   1. Problem:
 
        Missing support for Shasta A1.

      Cause:  
         
      Change:

        Disabled all A0 specific workarounds on A1 chips.

        Changed driver for 5751 A1 by disabling PCIE reset during GRC reset.

        Changed driver for 5751 A1 by enabing PCIE data fifo bug fix in the chip.

      Impact:

        None.

Version 7.60 Feb 18, 2004
-----------------------------
   1. Problem: 
    CQ9390, Remove HP mobile PCI entries from Broadcom standard .inf files.
      Cause:  
         Installation inf file needed update.
      Change:
         Update installation inf file.
      Impact:
            None.

   2. Problem: 
    CQ9420, Friendly name displays "%BCM5750A1% instead of 
                      "Broadcom NetXtreme Gigabit Eithernet"
      Cause:  
         Installation inf file needed update.
      Change:
         Update installation inf file.
      Impact:
            None.


Version 7.59 Feb 12, 2004
-----------------------------
   1. Problem: 
            CQ9262, Database file transfer come to a stop, ARP show 0's MAC address.
      Cause:  
            There was a corner case in the descriptor count check in SendPacketsMP().

            This corner case in the NIC driver can occur only if the packet data received 
            from the upper layer is extremely fragmented. For example, one packet, which 
            triggered this corner case contained 563 bytes, but was fragmented across 511 
            4K pages, each containing one or two bytes. One of our OEM Java database 
            applications generated this type of packet. When the driver fails in this mode, 
            the NIC can still receive but will not transmit. The NIC will also increment the 
            NoSendBdLeft statistic counter for each packet transition attempt. Usually, 
            the NIC driver cannot be disabled and the Windows desktop freezes.

Version 7.58 Feb 11, 2004
-----------------------------
   Fixes:
   =======
   1. Problem: 
            Driver may not initialize properly when PXE is enabled.
      Cause:  
            If PXE is not shutdown properly, the hardware will be left
            in a state that is not compatible with the driver's initialization
            routine.
      Change:
            Added code the check to see if the hardware has been left in a
            active state during the driver's load routine and reset the adapter
            if needed.
      Impact:
            None.

   2. Problem: 
            CQ9129, 5700/5704 may hang on systems with more than 4gb of ram.
      Cause:  
            There were several corner cases in the 4gb workaround code related to
            extremely small or extremely large transmit buffers.
      Change:
            Removed corner cases.
      Impact:
            None.

   3. Problem: 
            CQ9262, Database file transfer come to a stop, ARP show 0's MAC address.
      Cause:  
            There was a corner case in the descriptor count check in SendPacketsMP().

            This corner case in the NIC driver can occur only if the packet data received 
            from the upper layer is extremely fragmented. For example, one packet, which 
            triggered this corner case contained 563 bytes, but was fragmented across 511 
            4K pages, each containing one or two bytes. One of our OEM Java database 
            applications generated this type of packet. When the driver fails in this mode, 
            the NIC can still receive but will not transmit. The NIC will also increment the 
            NoSendBdLeft statistic counter for each packet transition attempt. Usually, 
            the NIC driver cannot be disabled and the Windows desktop freezes.


   Enhancements:
   =============
   1. Request: 
            Add LSO statistics for BMAPI
      Change:
            Added code to count the number of LSO transactions offloaded by the
    hardware.
      Impact:
            None.

   2. Request: 
            CQ9270 Enable LSO for 5788
      Change:
            Enable LSO for 5788 devices.
      Impact:
            None.

   2. Request: 
            CQ9199 Update OEM Product names.
      Change:
            Updated OEM Product names.
      Impact:
            None.


Version 7.57 Jan 22, 2004
-----------------------------

   Fixes:
   =======
   1. Problem: 
            CQ9161, ASF 2.0 Secure session cause HIGH cpu util seen in 10mb.
      Cause:  
    The driver sets bits 22 of the Pci Clock Control Register.
      Change:
            Do not set bit 22 of the Pci Clock Control Register for 575x
      Impact:
            None.

   2. Problem: 
            CQ9184, No network connection in Windows Xp when ASF is enabled
      Cause:  
    The handshaking between the driver and the fw does not work.
      Change:
            Fixed the driver to f/w handshaking.
      Impact:
            None.

   3. Problem: 
            CQ9168, When In OS present mode at 100mb the secure session fails.
      Cause:  
    The driver sets bits 22 of the Pci Clock Control Register.
      Change:
            Do not set bit 22 of the Pci Clock Control Register for 575x
      Impact:
            None.

   4. Problem: 
            CIOBE parts with multiple split transactions enabled may cause the
    system to hang.
      Cause:  
    CIOBE has an errata related to the multiple split transaction feature.
      Change:
            Disable multiple split transaction feature in CIOBE parts.
      Impact:
            None.

Version 7.56 December 30, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
            Enforce a register read after each and every register write.
            This is a workaround for a bug in the ASIC which causes
            chip lockup @10MBS (all traffic stops).
      Cause:  
    Problem in the ASIC design.
      Change:
            Register writes are followed by register reads
      Impact:
            None.

   Enhancements:
   =============
   1. Request: 
            Changed the interrupt processing slightly for the 5705 and 5750.
      Change:
            Attempt to reduce the number of forced status updates in the ISR.
      Impact:
            This is only an optimization of the code.


Version 7.55 December 24, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
            CQ 8820 5705 A3 Add support for new IDs (14e4  165e  1028  0171)
            and (14e4  165e  1028  015a).
      Cause:  
        New IDs.
      Change:
            Added new IDs to the inf
      Impact:
             None.

   2. Problem: 
            BCM5750 show as "fast ethernet" in device manager.
      Cause:  
    .inf text is incorrect.
      Change:
            Fixed the .inf
      Impact:
             None.

   Enhancements:
   =============
   1. Request: 
            Report the PCI-E bus type to bmapi
      Change:
            Modified OID to report bus type to bmapi
      Impact:
            None.

   2. Request: 
            Serialize all accesses to the 575X registers. This is a temporary 
            workaround for a problem in the Asic (CQ8912 and CQ8978).
      Change:
            Changed the code as requested.
      Impact:
            There are significant changes in the register access code.
            The driver size is increased from prior releases. The size with revert
            to that of prior releases when the serialize all I/O patch is disabled.


Version 7.54 December 10, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
            Bit 15 of register 0xc4 is not set properly (hardware bug workaround)
      Change:
            Set bit 15 of register 0xc4 using memory cycle (not config cycles)
      Impact:
            None.

   Enhancements:
   2. Request: 
            Change some of the driver code to remove magic numbers and use existing
            macros to read and write registers.
      Change:
            Changed the code as requested.
      Impact:
            None.


Version 7.53 December 05, 2003
-----------------------------

   Enhancements:
   =======
   1. Request: 
            Add support for 5750 device and move driver version to 7.53
      Change:
            Added support for 5750 device.
      Impact:
            5750 device supported.

   2. Request: 
            Increase 5751 chip reset delay to 300 milliseconds.
      Change:
            Increased 5751 chip reset delay to 300 milliseconds.
      Impact:
            5751 device chip reset has 300 milliseconds delay.




Version 7.36 December 02, 2003
-----------------------------

   Enhancements:
   =======
   1. Request: 
            Need registry key to configure frame length consistancy check.
      Change:
            Added registry key to configure frame length consistancy check.
      Impact:
            None.

Version 7.35 November 21, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
            Incorrect BCM5705 send producer index register update. This problem
            has been reported by one of our OEMs.

      Cause:  
            Contention issue in the NDIS driver on multiproc systems.

      Change:
            Protected the BCM5705 register update routine with a spin lock

      Impact:
            None.

Version 7.34 November 17, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
            CQ8781 - No check for NULL from NdisQueryBufferSafe in Ndis 5.1 drivers
      Cause:  
    Bug in code that calls NdisQueryBufferSafe
      Change:
            Implemented a buffer prescan to insure that packet buffers are mapped before
            attempting to process a packet. If any buffers are not mapped, fail the request
            gracefully.
      Impact:
            None.

   2. Problem: 
            CQ8781 - Use NdisQueryBufferSafe instead of NdisQueryBuffer in Windows 2000
            Ndis 5.0 drivers in oem specific builds
      Cause:  
    Code was implemented to use NdisQueryBuffer
      Change:
            Implemented a buffer prescan to insure that packet buffers are mapped before
            attempting to process a packet. If any buffers are not mapped, fail the request
            gracefully.
      Impact:
            Oem specific builds of the Ndis 5.0 driver will not load on Windows98.

   3. Problem: 
            The nic will drop frames if the ethernet length field is inconsistent.
      Cause:  
    The nic was programmed to drop frames containing a inconsistent ethernet
            length field.
      Change:
            Disabled ethernet length field checking in the hardware.
      Impact:
            None.


Version 7.33 October 16, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
             CQ 8625 5705 A3 programmed with new ID (14e4 1654 103c 3100) is not recognized by 7.32
             OEM specific build.
      Cause:  
            Incorrect OEM specific NT4 inf.
      Change:
            Corrected the inf
      Impact:
             None.

   2. Problem: 
             Multiple Mac Address (MMA) feature is only accepting two MMA addresses when it should
             accept three.
      Cause:  
            Incorrect #define value in source file.
      Change:
            Corrected #define value
      Impact:
             None.


Version 7.32 October 15, 2003
-----------------------------

   Fixes:
   =======
   1. Problem: 
             CQ 8497, 5705 A3 programmed with new ID (14e4 1654 103c 3100) is not recognized by 7.31

      Cause:  
            Incorrect NT4 inf.

      Change:
            Fixed the inf
      Impact:
             None.

   Enhancements:
   =============
   1. Request:
             CQ7321, add registry key to control TCP/IP option checksum support.
      Change:
             Added keys to disable task offload (see word document attached to CQ for more
             details).
      Impact:
             None. 


Version 7.31 October 13, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
             CQ 8497, 3 of 24 NIC reported a high Transmit Queue Length 
             in 72 hours stress test.
      Cause:  
            The OID handler is using an incorrect structure (big endian) 
            which causes the wrong dword to be incremented to reflect the 
            Q len.
      Change:
            Switched to the correct stucture
      Impact:
             None.

   2. Problem:
             Fix CQ8545, OEM certification test fails with 7.15 driver but 
             passes with 6.67
      Cause: 
             Incorrect chip rev. identification in MM_GetConfig() prevented
             TxCoalesce buffers from being allocated for some 5704s
      Change:
             Fixed MM_GetConfig()
      Impact:
             None

   3. Problem:
             CQ7502, LargeSend Offload (LSO) capabilities differ in 5705
             from the rest.
      Cause:
             The driver was reporting inconsistant encapulation support for
             LargeSend Offload.
      Change:
            Modified driver source to have same encapsulation support
            for all devices.

Version 7.30 Sep 23, 2003
-------------------------
   Enhancements:
   =============
   1. Request:
             Do not set the PME_EN bit in PCI configuration space if OOB WOL
             is not enabled in the nvram when the driver is unloaded.
      Change:
             Added check in the unload routine to not set the PME_EN bit
             when the driver is unloaded.
      Impact:
             None. 

   2. Request:
             Add support for 5705F
      Change:
             Added support in the inf files and driver code for 5705F.
      Impact:
             None.

Version 7.16 Sep 12, 2003
-------------------------
   Enhancements:
   =============
   1. Request:
             Add one key to control both phy auto-negotiation enable/disable and
             desired link speed.
      Change:
             Defined new values for 'RequestedMediaType' that specifies both
             auto-negotiation enable/disable and desired link speed.
      Impact:
             None. 

   2. Request:
             Add support for multiple mac addresses on the same nic for the Ndis5.0
             driver.
      Change:
             Changed compile flags to compile multiple mac address support in the
             Ndis5.0 driver.
      Impact:
             None. 

Version 7.15 Aug 29, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
             The network icon may intermittently disappear when changing driver
             properties when PowerMon is loaded and QOS is enabled.
      Cause:  
             The driver was incorrectly restarting phy auto-negotiation excessively
             causing the driver to take too long to report link up to the operating
             system.
      Change:
             Added code to only restart phy auto-negotiation when there is a change
             in the state of ReverseNway.
      Impact:
             None.

   Enhancements:
   =============
   1. Request:
             Add "volatile" modifier to SendPass and DpcPass driver variables to
             prevent the compiler from optimizing references in ia64 and amd64
             environments.
      Change:
             Added "volatile" modifier to SendPass and DpcPass driver in ia64
             and amd64.
      Impact:
             None. 


Version 7.14 Aug 28, 2003
-------------------------
   Enhancements:
   =============
   1. Request:
             Add support for multiple mac addresses on the same nic.
      Change:
             Added registry keys and custom OIDs to allow third party software
             to configure the nic with multiple mac addresses.
      Impact:
             None. 


Version 7.13 Aug 25, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
             The crc error counter for 5700 and 5701 was not getting zeroed
             out when T3_OID_RESET_STATS_COUNTERS is called.
      Cause:  
             The crc error counter for 5700 and 5701 was not getting zeroed out
             when the OID call is made.
      Change:
             Added code to zero out the crc error counter for 5700 and 5701 when
             T3_OID_RESET_STATS_COUNTERS is called.
      Impact:
             None.

   2. Problem:
             The retail WinXp32, WinXp64, AMD64 drivers were being compiled with
             incorrect compiler flags.
      Cause:
             The build environment was not configured correctly.
      Change:
             Corrected the retail build environment of the affected operating
             systems to use the correct compiler flags.
      Impact:
             Executables will be slightly smaller.


Version 7.12 Aug 20, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
             Driver Verifier complains about a possible deadlock problem.
      Cause:  
             The driver was holding a spinlock during Ndis calls in the send
             path.
      Change:
             Removed spinlocks during Ndis calls in the send path.
      Impact:
             None.

   2. Problem:
            System fault under heavy network load (verifier C4_31)
      Cause:  
            The driver may incorrectly use spin locks at ISR level
      Change:
            Remove all calls to acquire spin locks from the ISR.

   3. Problem:
            Improper use of spin lock in shutdown handler
      Cause:  
            The driver is using a spin lock in the shutdown handler
      Change:
            Remove calls to acquire spin locks from shutdown handler

Version 7.11 Aug 15, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
             The OID_GEN_RCV_OK statistic incorrectly included receive
             overrun frames.
      Cause:  
             The driver needs to subtract the number of receive overrun
             frames from the values reported by hardware.
      Change:
             The driver subtracts the number of receive overrun frames from
             the value reported by hardware before reporting the statistic
             to Windows.
      Impact:
             None.

   Enhancements:
   =============
   1. Request:
             Improve bit error performance of 5703A0 and 5704A0 when used
             with long cable lengths.
      Change:
             Program the phy's ADC and Gamma registers to more optimum settings.
      Impact:
             None.

   2. Request:
             Improve serdes drive levels on 5704.
      Change:
             Programed the serdes config registers with the values recommended
             by the hardware design team.
      Impact:
             None. 


Version 6.82 Aug 5, 2003
-------------------------

   1. Problem:
             Incorrect operation after PHY loopback test. Reported against 
             Linux configuration. 
      Cause:  
             PHY register 0x18 is not programmed properly after running the external
             loopback test.
      Change:
             Changed the value written to PHY register 0x18 from 0x480 to
             the correct value 0x400 (after external loopback test).                                             
      Impact:
             None.

   2. Problem:
              Flow control does not function (CQ8181).
      Cause:  
              LM_SetupCopperPhy() does not always program the flow control
              when the link comes up.
      Change:
              Program the flow control in all code paths when the link comes up.
      Impact:
              None.

   3. Problem
              Idle cycle fix in 5704 B0 has side effects on certain HP/CPQ
              servers.
      Cause:

      Change:
              This hardware fix is not enabled in this version.

Version 6.80 July 29, 2003
-------------------------
   Enhancements:
   =============
   1. Request: 
               Add support for external loopback with loopback plug.

      Change:
               Added new requested media type values for external loopback.

      Impact:
               None.

   2. Request: 
               Enable hardware fixes in 5704_Bx parts for known erratas.

      Change:
               Added code to driver init routines to enable hardware fixes in
               5704 B0 silicon.  See 5704 errata for more details info about
               the changes/fixes in B0 silicon.


      Impact:
               None.

   Fixes:
   =======
   1. Problem:
              AMD Solo System intermittently blue screens when installing driver for 5704
              CQ8190.

      Cause:  
              The driver is executing pageable code at high IRQ level (UM_Initialize()).  

      Change:
              Isolated the code executing at high IRQ level to a non pageable routine.

      Impact:
              None.


Version 6.69 July 9, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
              In Windows Win98SE: System cannot go into sleep mode when "wake up frame" is set

      Cause:  
              Win98SE expects WakeOnLan capability of  MagicPacket  as well  as  WakeUpFrame
              during its query of  OID_PNP_CAPABILITIES; even if device Advanced Properties is set to
              WakeUpFrame only.  

      Change:
              Added setting of MagicPacket support during handling of OID_PNP_CAPABILITIES.

      Impact:
              This change does not affect actual WOL function as specified in the Advanced Properties
              of the device, and only allows Win98SE systems to go to Standby mode.

   2. Problem:
              5700BX will stop processing packets under heavy loads.

      Cause:  
              A CoalesceNow workaround for stale status block information on the 5705 was
              causing the 5700BX to hang.

      Change:
              Qualified the CoalesceNow workaround to be applied to only the 5705.

      Impact:
              None.


Version 6.68 June 19, 2003
-------------------------
   Fixes:
   =======
   1. Problem:
              The adapter doesn't drop link when WOL is disabled and the driver
              is disabled.
              If WOL is enabled and the adapter is linked at 1gb when the driver
              is put into low power state, the adapter does not re-acquire link
              at 1gb when the driver resumes.

      Cause:  
              A typo in v6.65 of the driver was causing the driver to assume that
              ASF is always enabled.
              A change in v6.65 of the driver was causing the driver to not restart
              link autonegociation on resume.

      Change:
              Corrected typo causing the driver to assume that ASF is always enabled.
              Changed the restart autonegociation routine to take into account the
              changes made in v6.65

      Impact:
              These changes affect all adapters in all versions of Windows.


Version 6.67 June 13, 2003
-------------------------

   Enhancements:
   =============
   1. Request: 
               Increment version number for revision control purposes.

      Change:
               Changed version number from 6.66 to 6.67

      Impact:
               None.


Version 6.66 June 02, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
              CQ7927: System locks up when driver is unloaded on 5700/5701 with ASF.

      Cause:  
              A workaround that is not applicable to the 5700 and 5701 related to
              nvram accesses was being executed which caused an access to a invalid
              register.

      Change:
              Qualified the asf and nvram access workaround to be executed on only
              non 5700 and 5701 parts.

      Impact:
              This change only affects 5700 and 5701.



Version 6.65 May 31, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
              CQ7874,7873: Cannot get link after disabling power saving mode
              with ReverseNway. Cannot get link after changing from 100mb switch
              to 10mb hub.

      Cause:  
              There was a corner case in the ReverseNway logic that was causing
              the phy not advertise correct capabilities when ReverseNway is
              disabled while the control suite has the driver suspended.
              There was a corner case in the ReverseNway logic that was causing
              the to not be reset properly when the phy lockup errata was executed.

      Change:
              Corrected corner cases so the phy advertises correct capabilities to
              it's link partner.

      Impact:
              These changes only affect those platforms that have ReverseNway enabled.

   2. Problem:
              CQ7914: 5700BX fails to pass traffic while running 2c_Simultaneous
              WHQL tests.

      Cause:  
              A change in the 6.60 driver to address an errata on the 5704 inadvertently
              broke an existing fix for the 5700_BX small fragment errata. The bug was
              causing the driver to run out of coalesce buffers when run on 5700_BX
              devices.

      Change:
              Corrected code so the driver will properly handle small fragment coalesce
              buffers on 5700_BX devices.

      Impact:
              This change only affects 5700_BX devices. Other devices will not see any
              change in behavior.


Version 6.64 May 20, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
              CQ785207: Device is Yellow Banged out after disable/enable of the
              driver.

      Cause:  
              There was a race condition in the halt cpu routine in which the
              halted cpu could still be holding the NVRAM arbitration bit.
              This was preventing the driver from reading the configuration
              information from the NVRAM and caused the driver to unload.

      Change:
              Added check in the halt cpu routine to see if the halted cpu is
              holding the NVRAM arbitration bit.

      Impact:
              None


Version 6.63 May 20, 2003
-------------------------

   1. Enhancements:

   Fixes:
   =======

   1. Problem:
              CQ7807: Loopback- - Mac test fails

      Cause:  
              The driver was not correctly configuring the 5705 for mac loopback
              if the device was linked at 10mb.

      Change:
              Changed code to correctly configure the device when linked at 10mb.

      Impact:
              None

   2. Problem:
              CQ7827: System will freeze on shutdown when linked at 10mb half.

      Cause:  
              The phy was getting powered down during reset.

      Change:
              Changed code to not power down the phy during reset.

      Impact:
              None

Version 6.62 May 15, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
              CQ7656: Driver get yellow bang on 5788.

      Cause:  
              A check for the device/bond id was detecting the 5788 as an
              unsupported device and therefore was causing the driver to unload.

      Change:
              Removed the check that was causing the driver to unload.

      Impact:
              None

   2. Problem:
              CQ7798, CQ7799: ChkInf found errors in the inf files.

      Cause:  
              Typos in the inf files.

      Change:
              Corrected the inf files.

      Impact:
              None

   3. Problem:
              The workaround for the phy lockup errata was not being applied to all
              versions of the 5703 and 5704.
      Cause:  
              There was a check for previous revisions of 5703 and 5704 that was
              incorrectly carried over from a previous errata.

      Change:
              Removed check for specific versions of the 5703 and 5704 for the phy
              lockup errata.

      Impact:
              None


   1. Enhancements:
              CQ7795, CQ7800: 1000 Full Duplex option in adapter advanced properties
              for all inf files.

      Change:
              This option is suppose to be present in only inf files for specific
              OEMs. Removed 1000 Full Duplex option from files that are not applicable.

      Impact:
              None


Version 6.61 May 14, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
         CQ7777: Some of the OID tests are failing in win98me

      Cause:  
              Added parameter checks in the OID processing are not
              valid in all cases. These were added in rev 6.54

      Change:
              Removed the checks, they do not work for all cases as implemented.

      Impact:
              None

   2. Problem:
         The driver did not restart autoneg on Fast Ethernet only parts when resuming
         from hibernate or standby.

      Cause:  
              This was originally intended behavior. However the driver needs to
              restart autoneg on resume due to phy lockup errata.

      Change:
              During resume check for Fast Ethernet only capable parts and 
              restart phy auto negotiation.

      Impact:
              None

   1. Enhancements:
              The following OEM device ID's are not in the inf files.
                PCI\VEN_14e4&DEV_16c7&SUBSYS_00ca0e11
                PCI\VEN_14e4&DEV_16c7&SUBSYS_00cb0e11

      Change:
              Added OEM device ID's

      Impact:
              None

Version 6.60 May 12, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
               Fixed problem with link getting dropped when shutting down Windows
               when using a 5703/2 with old versions of bootcode when OOB WOL is
               enabled.
      Cause:  
               The bootcode was not properly passing configuration information to
               the ndis driver.
      Change:
               Modified the ndis driver to read the configuration information directly
               from NVRAM.
      Impact:
               None

   2. Problem:
               System bluescreens with random bugcheck values on .Net with 5704.
      Cause:  
               A bug in the 4gb errata workaround with LSO enabled was causing buffer
               overruns which would corrupt system memory and cause random bugcheck values.
      Change:
               Allocated static double copy buffers for use with LSO and 4gb aligned
               buffers.
      Impact:
               None


Version 6.59 May 5, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
               CQ7664: New HP device IDs need to be added.
      Cause:  
               N/A
      Change:
               Added HP device IDs to NIC .inf
      Impact:
               None

   2. Problem:
               CQ7521: Mac loopback test is broken with fiber devices
      Cause:  
               UM_AutogRetryTimerFunction() calls LM_SetupPhy() during test
      Change:
               Added LM_REQUESTED_MEDIA_TYPE_LOOPBACK condition to call to 
               LM_SetupPhy()
      Impact:
               None

   3. Problem:
               The driver will intermittently load with a zero mac address.
      Cause:  
               The shared memory area that contains the mac address was not properly
               initialized when the nic is in certain low power modes.
      Change:
               Read the mac address from the NVRAM and not shared memory.
      Impact:
               None

Version 6.58 May 1, 2003
-------------------------

   Fixes:
   =======

   1. Problem:
               Laurel PING -t gets 20-30% 'request timed out' on both ports (CQ7586)

      Cause:  
               Fiber phy setup is being performed every half second because we are using
               the autoneg bit as a condition. This bit is not set when the fiber switch 
               is not doing autoneg.
      Change:
               Only look at the autoneg bit when autoneg was successfully completed.
      Impact:
               None

   2. Problem:
               Hardy having link status inconsistency (CQ7550)

      Cause:  
               Fiber Phy was not programmed properly.
      Change:
               Changed the NDIS code to behave like the Linux code.
      Impact:
               None



Version 6.57 April 29, 2003
-------------------------

   Fixes:
   ========
   1. Problem: 
               When the phy is poweredd down via BMAPI the network icon in the system
               tray does not always show link down.
      Cause:
               Race condition between the trying to indicate link down to the operating
               system and the phy reset routine trying to indicate link up to the operating
               system
      Change:
               Corrected logic error to remove race condition.
      Impact:
               None.
               
   2. Problem: 
               The OID OID_GEN_TRANSMIT_QUEUE_LENGTH does not support 64bit queries.
      Cause:
               The code did not support 64bit queries.
      Change:
               Corrected code to support 64bit queries.
      Impact:
               None.

   3. Problem: 
               Updated phy workarounds for potential intermittent link problems for 5704/5705.
      Cause:
               Not applicable.
      Change:
               Not applicable.
      Impact:
               None.


Version 6.56 April 18, 2003
-------------------------
 
   Fixes:
   ========
   1. Problem: 
               The phy workaround implemented in 6.55 was not properly qualified to
               be applied to only 5704.   
      Cause:
               An 'if' statement was missing when the code was checked in.
      Change:
               Added 'if' statement in routine with 5704 phy workaround to properly
               qualify the workaround.
      Impact:
               None.

Version 6.55 April 17, 2003
-------------------------

   Fixes:
   ========
   1. Problem: CQ #7454, CQ #7559, CQ #7352, CQ #7453, CQ #7500, CQ7469
               Incorrect and intermittent WakeOnLan behavior on 5788. System waking up when
               not configured to wake and system not waking up when configured to wake.
      Cause:
               Ndis driver was not allowing enough time for the bootcode to complete
               execution of it's second phase of boot before communicating WakeOnLan
               configuration information to the bootcode.
      Change:
               Extended max delay for the driver to wait for bootcode to complete execution
               by 60ms.
      Impact:
               Driver unloads will take 60ms longer to execute.
               
   2. Problem: 
               Ndis Driver takes too long to initialize
      Cause:
               The ndis driver had a lengthy delay routine are part of phy initialization
      Change:
               The wait loop was qualified so it only applies to 5700 and 5701. Those parts
               were observed to require this delay.
      Impact:
               Ndis driver initialization should be faster by more than 20ms.

   3. Problem: 
               5704 intermittently will not auto-neg link at 1gb.
      Cause:
               The phy has a errata that requires the driver to check if the dfe is
               locked up.
      Change:
               Added dfe lockup check routine as part of the phy reset routine.
      Impact:
               Slightly higher cpu utilization when the cable is first disconnected.

   Enhancements:
   =============
   1. Request: 
               Added support for dynamic 10/100 or 10/100/1000 phy auto-neg advertising
               for certain platforms.

      Change:
               Added a check for the state of GPIO2 during link change events and adjust
               auto-neg capability advertising accordingly.

      Impact:
               None.

Version     Release Date
=======     ============
6.54    a.  04/09/03
            CQ6302 Add OID to blink the activity LED
            CQ7127 Add OID to reset stats counters
            CQ7281 Add OID to implement OID_802_XMIT_LATE_COLLISIONS
            CQ7294 Fix OID OID_GEN_RCV_NO_BUFFER
            CQ7315 Fix various OID return codes
        b.  Added fix for 5704S to fall back to HW AN Off when NICs TX fiber cable
            is removed.
        c.  Added workaround for 4gb memory errata for 5704 running under ia64.
        d.  Added 5788 tx/rx checksumming options in inf files.

6.53        03/26/03
        a.  Implemented workaround for CQ7242: Unable to wake system from shutdown
            after running hibernate under Windows 2003.
        b.  Always enable OOB WakeOnLan for legacy 5701 bootcode.

6.52        03/14/03
        a.  Added support for 5788.
        b.  Fixed problem with link down being reported if link was acquired during
            driver initialization.

6.51        03/13/03
        a.  Extended wait for link up during resume from Standby/Hibernation to
            fix packet drop issue in WHQL Standby/Hibernate testing.

6.50        03/10/03
        a.  Added 5704S support back in.

6.36
            03/05/03
        a.  Fixed intermittent blue screen if there is a link status change during
            driver unload.

6.35        03/04/03
        a.  Fixed intermittent blue screen problem during driver init if the
            device is sharing an interrupt.
        b.  Added support for OID_GEN_TRANSMIT_QUEUE_LENGTH
        c.  Corrected support for legacy bootcode that doesn't support eeprom
            version information. This problem was causing WakeOnLan configuration
            problems.
        d.  Fixed problem where serdes adapters were being treated as copper.
        e.  Fixed WHQL failure due to not waiting for link long enough on
            5702/3-A3 parts.
        f.  Fixed ASF hanging when system is going to standby/hibernate.

6.34        02/17/03
        a.  Added code to wait for the 2nd phase of bootcode to complete on
            5702/3/4/5. This resolves a WoL related issue with older
            v2.21a 5703 bootcode, and is generally "safer".  This also
            resolves an unwanted case where WoL was accidentally enabled.
        b.  Removed code to stop the TX and RX processor clocks on 5704
            when going into standby/hibernate or shutdown.  This resolved a
            hang when coming out of S1 with a 5704.
        c.  Minor change to interrupt coalescing algorithm.

6.33        02/14/03
        a.  Removed 5704 Serdes Support.
        b.  Added support for 5705 A3 DMA Workarounds.
        c.  Optimized Interrupt Coalescing algorithms for 64/66 systems.
        d.  Fixed problem when forcing WakeOnLan speed to 10mb and then
            having the system stay at 10mb when the system is resumed.
        e.  Incorporated improved power management for 5704 when the
            system is being shutdown or put into standby.

6.32        02/12/03
        a.  Updated driver send packets for resolve of Appletalk issue.
        b.  Updated driver for 5704 Fiber Auto Negotiation.
        c.  Added ODI_GEN_PROTOCOL_OPTIONS back into NdisQueryInformation
            because the WHQL tester expects it.
        d.  Fixed problem with NdisQueryInformation returning failure status
            when it's not appropriate.
        e.  Corrected removing 5782 Ethernet@WireSpeed option for WinXp.
        f.  Changed driver to runt tx frames with zero instead of garbage.

6.31        02/10/03
        a.  Removed OID_GEN_PROTOCOL_OPTIONS from NdisQueryInformation
        b.  Removed Ethernet@WireSpeed option from 5705A2/A3 and 5782.
        c.  Added check for null pointers in NdisQueryInformation to prevent
            system blue screens.
        d.  Fixed CQ#5069: Added HotPlug PCI port number assignment.


6.30        02/07/03

        a.  Enabled 5704 Fiber Support for resolve of bugs:  
             CQ#6288: BCM5704SA40 Fails to Negotiate with HP Procurve 2524 Switch.
             CQ#6725: Port 1 on 5704s Fiber does not pass traffic.
             CQ#6746: Fiber fails to link w/ 5.27 NDIS driver.
        b.  Added check to allow only valid mac addresses when the user manually
            overrides the mac address.
        c.  Fixed problem with ClkRun signal always being forced to active.

6.14        01/30/03

        a.  Fixed CQ#6800: 5704C Copy/compare test failure in .NET.  The failure
            was a result of unintentionally including the CQ#6381 fix in the
            .NET driver.


6.13        01/30/03
        a.  Fixed CQ#6247:  Under a heavy traffic environment, the driver could
            miss a status block update causing the chip to stall.  This problem
            has been observed only in the 2c_performanceblast Ndistest.

        b.  Fix CQ#6796 Window Diag fails on Internal Memory test on 5700-LOM
             by using alternate method to access memory.


6.12        01/27/03
        a.  Improved LSO firmware load time by not acquiring NVRAM lock.
        b.  Fix CQ6796 Window Diag fails on Internal Memory test on 5700-LOM
             by using alternate method to access memory.
              

6.11        01/24/03
        a.  Fixed buffer overrun problem when jumbo frames is enabled.
        b.  Fixed interrupt storm if a spurious interrupt occurs after resume
            from standby/hibernate due to stale status block information.
        c.  Fixed 2m_strss test failure due to late status block update during
            heavy bus traffic.
        d.  Fixed WOL failure when cable is disconnected when the system is
            put to sleep.
        e.  Fixed CQ6710 Running window Diag on 5700 LOM causes server to hang
        f.  Fixed CQ6736 BACS Window diagnostic failed on the internal memory test
            by using alternate method to access memory.
        g.  Added PHY power down for 5704 devices when WakeOnLan is Disabled.

6.10        01/13/03
        a.  Fixed CQ#6620 -- Driver may corrupt the stack on Windows 2000 if
            the packet being sent is very fragmented.

5.32        01/10/03
        a.  Fixed CQ#6539 -- Driver may not able to send packets when it runs
            out of double copy buffers.
        b.  Fixed problem with ReverseNway getting disabled after resume from
            standby/hibernate.

5.31        01/09/03
        a.  Fixed problem with not being able to disable Ethernet@Wirespeed
            feature.
        b.  Fixed problem causing NMI errors on certain platforms during init.

5.30        01/07/03
        a.  Fixed cert test failure on 5705 when running at 10mb.
        b.  Fixed intermittent link failure when resuming from phy
            power down mode.
        c.  Improved system resume time when cable is disconnected.

5.29        01/03/03
        a.  Fixed CQ#6456 -- Crash during hibernation with BCM5700.
        b.  Updated copyright strings to 2003.
        c.  Added phy reset when powering up the phy from low power mode.
        d.  Fixed loopback test failure.

5.28        01/01/03
        a.  Added Phy Reset to link down events for 5705.
        b.  Removed 5704 support.

5.27        12/30/02
        a.  Removed DbgPrint statements from retail build of driver.

5.26        12/30/02

        a.  Fixed CQ#6481 -- MagicPacket capability was not properly reported
            to the operating system.  Access to PHY registers was not properly
            synchronized when the system comes out of standby.
        b.  Fixed CQ#6353 -- Access to PHY registers was not properly
            synchronized when the system comes out of standby resulting in
            NdisTest WOL test failures.
        c.  Improved driver load times when link pulses are not present.
            

5.25        12/20/02
        a.  Fixed Bug#6354 ASF CFG table gets corrupted when changing IP to static.
        b.  Fixed Bug#6026 Allow only management to station to wake sticks with WOL 
             advanced option set to Wake Up Frame.
        c.  CQ6381:  5704C fails copy/compare tests only on PAE machine while
               running Chariot.
            CQ6418:  5704 Fiber fails copy/compare on PAE machine while running
               Chariot on different cards.

5.24        12/17/02
        a.  Added 6.25 Mhz low power clock mode for 10mb link.
        b.  Added MpSpinlock check for 5705 coalescing timer tick routine.
        c.  Tristate GPIOs during driver init.
        d.  Enabled Phy DLL power down.
        e.  Removed check for NT4 SP4 in ndis4 oemsetup.inf

5.23        12/12/02
        a.  Fixed hang on shutdown during programming of PMCtrl register.
        b.  Updated INF files to reflect known PCI ID's as of this date.

5.22        12/11/02
        a.  Fixed various Wake On Lan issues related to PCI config cycles
            not getting written by the OS.
        b.  Fixed problem with 5705/5901 not completing pending transmits
            when the driver is unloaded under heavy traffic.
        c.  Mapped the following NDIS counters:
              OID_802_3_XMIT_UNDERRUN
              OID_802_3_RCV_OVERRUN
              OID_GEN_XMIT_ERROR
        d.  Changed Link Down events in the event log from "Error" to
            "Warning"

5.21        11/27/02
        a.  Fixed 5704 and 5704S Fiber Negotiation issues.
        b.  Fixed 7 second link down indication.
        c.  Added work around for 5701A1 LSO hang.

5.20        11/19/02
        a.  Don't unload driver if BAR's memory enable bit is not set.
        b.  Enable Rx Accelerate for 5705A1 running on 33Mhz system bus.
        c.  Don't arbitrate halting of on board CPUs on 5700 and 5701.
        d.  Don't advertise SNAP encapsulation LSO support for 5705.
        e.  Prevent duplicate link indications to the OS.

5.19        11/12/02
        a.  Added three new OIDs for PHY Turn Off, Turn On, and Query operation.
        b.  Fixed yellow bang problem with 5705.

5.18        11/08/02
        a.  Fixed problem with 5901 not negotiating 100mb when plugged into a gigabit
            capable switch.
        b.  Fixed Waker/Dozer link problems.
        c.  Added Auto phy power down for 5705/5901 A1.

5.17        11/01/02
        a.  Changed WOL default capabilities to 'Both'.
        b.  Changed call to NdisMInitializeScatterGatherDma to pass TRUE for
            64-bit DMA capable.
        c.  Fixed HCT cable disconnect failure on IA64.
        d.  Changed link down messages in the error log to 'Error' from 'Informational'.
        e.  Fixed 5700 hang when unloading and reloading the driver.

5.16        10/21/02
        a.  Changed default DpcLoopCnt to improve mouse response on HyperThreading
            enabled processors.
        b.  Removed manual install options from inf files.
        c.  Added Isolate mode to phy power down sequence.

5.15        10/08/02
        a.  Disabled 5705/5901 Auto phy power down.
        b.  Adjusted link up timer due to pass whql media connect/disconnect test.

5.14        10/03/02
        a.  Corrected 5705/5901 Low power state clocking.
        b.  Enabled 5705/5901 Auto phy power down.
        c.  Fixed problem with linking at 1000mb when system is
            going into standby or hibernate.

5.13        09/25/02
        a.  Removed Jumbo Frame option for 5705/5901 on NT4
        b.  Fixed blue screen problem with 5705/5901

5.12        09/24/02
        a.  Added 5705MFE Support.
        b.  Added 5704S Support.

5.11        09/23/02
        a.  Fixed Ethernet@Wirespeed not getting disabled after phy
            reset on 5705/5901.
        b.  Shortened 5705/5901 reset sequence.
        c.  Corrected Low Power mode clocking for 5705/5901.

5.10        09/18/02
        a.  Fixed blue screen problem with 5705/5901.
        b.  Fixed Ethernet@WireSpeed not getting disabled with 5705.

4.13        09/16/02
        a.  Corrected driver WakeOnLan and Default options in the
            installation  .inf  files.

4.12        09/13/02
        a.  Fixed problem when only 'magic pkt' or only 'wake up frame'
            is selected from advanced properties tab.

4.11        09/12/02
        a.  Fixed problem with Vaux switchover for 5704.
        b.  Changed WOL speed behavior for 5704.

4.10        09/04/02
        a.  Removed 5705/5901 support for version 4.xx. 5705/5901 support
            will be in version 5.xx
        b.  Fixed problem with system not waking up with Magic Packet
            from shutdown.

3.51        09/03/02
        a.  Fixed problem with system waking from magic pkt when "Allow
            this device..." checkbox was unchecked.

3.50        08/26/02
            Bumped revision number to 3.50 for revision control purposes.
            No functional changes.

3.30        08/20/02
        a.  Fixed 2m_addre certification failures.
        b.  Fixed ReverseNway problems after resume from hibernate.
        c.  Fixed link indication problems with 5705/5901
        d.  Fixed IA64 SGL LSO performance problem.

3.29        08/13/02
        a.  Added 5901 Support
        b.  Fixed Pattern Match WOL problem with 5705/5901
        c.  Added support for 5705/5901 ClkRun register bits for MiniPci
        d.  Performance tuning for 5705

3.28        08/08/02
        a.  Fixed shutdown hang on IA64 platforms
        b.  Fixed problem with interrupt vector greater than 255.
        c.  Fixed eeprom corruption when BMAPI writes only 4 bytes
        d.  Removed invalid tx cpu checks for 5705

3.27        08/01/02
        a.  5703S Magic Packet WOL support
        b.  Fixed 5705 Statistics

3.26        07/30/02
        a.  Added PLL Powerdown in low power mode back in.
        b.  Added support for 5705
        c.  Removed init delay loops for 5705

3.25        07/25/02
        a.  Fixed problem with system hangs when WOL speed is forced
            to 10mb.
        b.  Removed corner case when processing TCP large send offloads
            that was causing the firmware to hang.
        c.  Enforced WOL speed requirements on 5704 adapters to minimize
            VAux power consumption.

3.24        07/11/02
        a.  Fixed problem with system hangs during suspend/hibernate.
        b.  Fixed linkspeed problems w/ ASF.

3.23        07/10/02
        a.  Correct INF to reflex correct driver defaults for OEM1_DEV4 device.
        b.  Fixed problem with System Shutdown leaving link at 1gig under certain
            configurations.

3.22        07/03/02
        a.  Added routine to read PowerSaving state from bootcode. This feature
            requires bootcode dated after 07/03/02.
        b.  Added code to notify bootcode of OS Shutdown/Suspend.

3.21        07/01/02
    Fixed the following:
        a.  Cable disconnect cert failure for XP/.Net.
        b.  Network link intermittently getting dropped when ASF is enabled.

3.20        06/28/02
    Fixed the following:
        a.  Large Send Offload hang due to dma queue out of sequence
        b.  System hang during shutdown.

3.19        06/26/02
    Fixed the following:
        a.  System hang/reboot due to PME getting stuck.

3.18        06/25/02
    Fixed the following:
        a.  Gray out power management when WOL capabilities is set to none.
        b.  Fixed continuous messages in Event Viewer for NT4.
        c.  Fixed blue screen/system hang problem when unloading driver.
        d.  Added Link Speed power saving.

3.17        06/19/02
    Fixed the following:
        a.  Added workaround so Win2k doesn't gray out power management
            button when only Magic Packet is enabled.
        b.  Changed workaround for .Net32/.Net64 link detect problem.
        c.  Changed max send packet BD from 32 to 128.
        d.  Added Power Saving OID

3.16        06/04/02
    Changed service names for .net32/.net64 back.

3.15        06/04/02
    Fixed the following:
        a.  Added workaround for .Net32/.Net64 link detect problem.
        b.  Corrected service names for .Net32/.Net64

3.14        05/22/02
    Fixed the following:
        a.  Incorrect link polarity in phy loopback test
        b.  Incorrect mac address for function 1 when firmware is not running.
        c.  Nic hang when running WHQL large send offload test.
        d.  Added Mac Address override in INF file for Win2k, WinXP.
        e.  Added workaround when the going into suspend or hibernate but
            the OS doesn't tell the driver that the supported PM mode has changed.

3.13        05/13/02
    Fixed the following:
        a.  Added WOL workaround that doesn't require link status polling
        b.  Adjusted MBUF Watermarks to fix problem 10/100 rx discard problem.

3.12        05/01/02

    Fixed the following:
        a.  Corrected version number to 3.12


3.11        04/30/02

    Fixed the following:
        a.  On Windows XP and later, both NDIS_MAC_OPTION_8021Q_VLAN and
            NDIS_MAC_OPTION_8021P_PRIORITY options must be enabled when VLAN
            support is turned on.
        b.  Fixed PCIX hanging problem
        c.  Added fix for mysterious 0x70 clearing problem.


3.10        04/23/02

    Fixed the following:
        a.  Second function not being recognized by NT4
        b.  Official Alpha 5704 release


2.89        12/09/02

    Fixed the following:
        a.  The standard receive buffer could overflow by 1 or 2 bytes when
            jumbo frame is enabled.


2.88        12/03/02

    Fixed the following:
        a.  Corrected CQ6203 Long wait during Teaming configuration.


2.87        11/25/02

    Fixed the following:
        a.  Corrected issues of Shutdown and going to Standby in PCIX systems
            with ASF Enabled.


2.86        11/15/02

    Fixed the following:
        a.  Changed Link Down status to Error in Even Viewer.
        b.  Report 64bit DMA capable on 64bit adapters.
        c.  Fixed problem with losing link after running cable diags.

2.85        10/18/02

    Fixed the following:
        a.  Fixed mouse not moving smoothly problem on Hyper-threading enabled
            systems.
        b.  Fixed intermittent loopback failures on PCI-X systems.
        c.  Updated internal driver string names.

2.84        09/24/02

    Fixed the following:
        a.  Check for duplicate Wake Pattern during handling of
            OID_PNP_ADD_WAKE_UP_PATTERN and return success if pattern already
            stored.
        b.  No longer log or report Link Up and Link Down Status; when in
            Diagnostic Mode.


2.83        09/17/02

    Fixed the following:
        a.  Freeing non-empty Ndis packet/buffer pool when driver verifier
            is enabled.  This is a very rare condition.


2.82        08/09/02

    Fixed the following:
        a.  CQ4838,4862: Low performance when LargeSend is enabled on IA64
            systems.
        b.  Fixed problem with interrupt vector greater than 255.


2.81        07/31/02

    Fixed the following:
        a.  Freeing non-empty Ndis packet/buffer pool when driver verifier
            is enabled.


2.79        07/29/02

    Fixed the following:
        a.  Provide statistics counter for frames dropped due to no receive
            buffer left.
        b.  Qualified bond id check with chip number.  Add additional bond ids.
        c.  Driver could crash when sharing interrupt.
        d.  LargeSend may cause a transmit lock.


2.78        06/28/02

    Fixed the following:
        a.  Register access contention with ASF during driver initialization.


2.77        06/26/02

    Fixed the following:
        a.  Ensure there is no bus activity when there is no link.
        b.  CQ4376: Hot replace of a fiber adapter leaves it in inoperable 
            state.
        c.  CQ4542: CPU test failure on a BCM5701 adapter running in PCI-X mode.
        d.  CQ4577: Register test failure on a BCM5701 adapter running in PCI-X
            mode.


2.76        06/10/02

    Fixed the following:
        a.  Freeing non-empty Ndis packet/buffer pool when driver verifier
            is enabled.


2.75        05/07/02

    Fixed the following:
        a.  Register test failure on the fiber adapter.


2.74        05/06/02

    Fixed the following:
        a.  Bad CRC count reported after running diagnostic.


2.73        05/01/02

    Allow a user application to query the driver's current flow control
    setting.

    Fixed the following:
        a.  On Windows XP and later, both NDIS_MAC_OPTION_8021Q_VLAN and
            NDIS_MAC_OPTION_8021P_PRIORITY options must be enabled when VLAN
            support is turned on.
        b.  Intermittent memory test failure.
        c.  Removed speed and duplex settings from the driver's advanced
            property tab of a fiber adapter.


2.72        04/24/02

    Miscellaneous changes to the INF files.


2.71        04/23/02

    Fixed the following:
        a.  System crash due to GPIO register access.  Added a workaround.


2.68        03/29/02

    Fixed the following:
        a.  CQ3740:  Missing information in the NT4 help file pertaining to
            "1 Gb Full" duplex line setting for the fiber adapter.
        b.  High CPU utilization after a CPU test on BCM5703/02.


2.67        03/22/02

    EEPROM write was not working.


2.66        03/21/02

    Changed driver media description to "Broadcom NetXtreme Installation Media".

    Allow configurability of the LED control register.


2.65        03/14/02

    When the "Speed & Duplex" setting is set to "auto" on the fiber adapter,
    the driver will fall back to 1000Mb FD mode if the link partner is not
    attempting to auto negotiate.

    Fixed the following:
        a. CQ3636: Cannot pass traffic in 1000Mb FD mode after disconnecting
           the cable.


2.64        03/13/02

    Fixed the following:
        a. CQ3592: High CPU utilization on the fiber card when it is set to
           auto-negotiate with a switch that has auto-negotiate turned off.
        b. CQ3593: Program the link LED of the fiber card to reflect
           auto-negotiation result.


2.63        03/08/02

    Fixed the following:
        a. CQ3217: Cannot get link when connecting two fiber adapters
           back-to-back.


2.62        03/01/02

    Fixed the following:
        a. CRC errors on BCM5703S.


2.61        02/28/02

    Enable RX checksum and LargeSend offloading by default on WindowsXP.

    Added BCM5703/02 performance enhancements.

    Fixed the following:
        a. CQ3437: 1c_InitTime test failure.  Driver was taking too long
           to obtain link status.


2.59        02/25/02

    Fixed the following:
        a. CQ3386: Removed Ethernet@WireSpeed option form fiber adapters.
        b. CQ3396: Removing the driver on Windows9x, caused the system to
           lock-up.
        c. CQ3387: WOL parameter not removed when upgrading to a fiber adapter.
        d. Removed Ethernet@WireSpeed option from BCM5700 based adapters.


2.58        02/22/02

    Fixed the following:
        a. CQ3355: WOL at 100Mb mode was not working on BCM5700.
        b. Changed the default for Ethernet@WireSpeed to enable.
        c. Unable to pass traffic at 1Gb link when Ethernet@WireSpeed is
           enabled.


2.57        02/22/02

    Added support for BCM5703s.

    Added the new PCI device IDs for the BCM5703/02 based adapters.

    Added support for Ethernet@WireSpeed.

    Fixed the following:
        a. CQ3153: 2m_WOLPattern Ndis test failure on the new HCT10 QFE5.


2.56        02/11/02

    Added ASF WOL support.


2.55        02/06/02

    Fixed the following:
        a. CQ2892: CPU utilization goes up when only the receive cable of the 
           fiber adapter is connected to the switch.
        b. CQ3035: Changed the copyright year.
        c. CQ3083: System locks up when running the interrupt test.
        d. CQ3105: 2c_LoadUnload test failure.


2.54        01/25/02

    Removed support for BCM5703/02 A0.

    This version is based off v2.32 and v2.41 with the following fixes added.
        a. CQ2097,2879,2888:  Intermittent autonegotiation failure when loading
           the driver for the fiber adapter.
        b. CQ2548: Unable to "unfail" on NT4 via a Hot-Plug utility.
        c. CQ2544: Hot-Plug utility displays an incorrect link status on NT4.
        d. CQ2891,2865: PXE client unable to do remote installation.
        e. CQ2613: W2K crashes while running continuous loopback in a PCI-X
           system.


2.53        01/23/02

    Fixed the following:
        a. Unable to read the MAC address from SEEPROM on BCM5703/02.


2.52        01/22/02

    Fixed the following:
        a. CQ2873: Failed 2c_AddressChange when running NdisTester.
        b. CQ2893: Jumbo frame was not working on BCM5703/02A0.
        c. CQ2879,2888: Intermittently failing the 1c_gtime test on the fiber
           adapter.
        d. CQ2544,2548: NT4 Hot Plug PCI issues.


2.51        01/10/02

    Fixed the following:
        a.  BCM5703/02A0 cannot wake-up from hibernation and standby if the
            firmware is not active.


2.49        01/08/02

    Fixed the following:
        a.  Ensure MAX_PCI_RETRY is set to zero immediately after a reset.


2.48        01/02/02

    Added support for ASF.


2.47        12/28/01

    Fixed the following:
        a.  Lost of network connectivity when running Double-Take on
            Windows 2000.


2.46        12/27/01

    This is an NT4 release only.  This version is actually v2.43 with the
    fix listed below.

    Fixed the following:
        a.  Failed 2m_media.tst on NT4 when running in 10mb half duplex mode.


2.45        12/20/01

    Added a new BCM5703/02A0 firmware workaround for DMA write overrun.

    Fixed the following:
        a.  Taking extremely long time shutting down Windows 9x when the driver
            is running.


2.44        12/18/01

    Added support for BCM5703/02.

    Added PCI-X workaround for BCM5703/02A0.


2.43        12/11/01

    Added the new Ndis 5.1 VLAN extensions for Windows XP/.NET drivers.  To
    enable this feature, set the registry parameters for "VlanEnable" to 1 and
    "VlanId" to the desired VLAN ID.

    Added support for BCM5700 with BCM5411.


2.42        12/07/01

    Added support for BCM5703/02.

    Fixed the following issue:
        a.  Windows 2000 may crash when running the loopback test continuously
            on a multi-processor system.


2.41        11/15/01

    This is an NT4 release only.  This version is actually v2.32 with the
    fix listed below.

    Fixed the following issue:
        a.  NT4 shutdown causes the system to hang when WOL is enabled.


2.40        04/22/02

    This version is based off v2.32 with the following fixes added.
        a.  Lost of network connectivity during WHQL ServerTest on a PCIX-100
            system.


2.39        11/02/01

    Fixed the following issues:
        a.  "unfail" issue in OEM Hotplug utility.  Only affects NT4 driver.


2.38        11/01/01

    Fixed the following issues:
        a.  Intermittent problem reading PHY registers.


2.37        10/31/01
    
    Fixed the following issues:
        a.  NT4 HotPlug PCI state was not initialized.
        b.  1c_Reset, 2c_OffloadChecksum, and 2c_OffloadLargeSend was not fixed
            in v2.36.


2.36        10/28/01

    Fixed the following issues:
        a.  Second installation on NT4 does not update to a newer driver.
        b.  Fixed intermittent failures on 1c_Reset, 2c_OffloadChecksum,
            and 2c_OffloadLargeSend.


2.35        10/22/01

    Added support for BCM5700Cx LargeSend offload.

    Added support for BCM5702.

    Fixed the following issues:
        a.  PHY_LINK10 mode not working.
        b.  Failed file compare test with Netbui protocol.


2.34        10/03/01

    Fixed the following issues:
        a.  Not reporting link change status to the OS when the cable is being
            disconnected from a 10Mb link.  This problem only occurs on the
            BCM5700.
        b.  Encapsulation for Task Offload was not properly advertised.


2.33        09/19/01
    
    Fixed the following issues:
        a.  BCM5700 cable unplug problem at 1Gb on PCI-X system.  Also requires
            1.12, or 2.5 or newer EEPROM.
        b.  Refine the fix in v2.32.  Version 2.32 will crash if at the time
            of the unplug, the system was busy transmitting packets.


2.32        09/14/01

    Fixed the following issues:
        a.  BCM5700 cable unplug problem at 1Gb.  Also requires 1.12, or 2.5
            or newer EEPROM.


2.31        09/12/01

    Fixed the following issues:
        a.  There is a possibility of the BCM5700 not claiming its interrupt,
            which results in system lock-up.
        b.  XP blue screen when running 2c_simultaneous on BCM5700 with jumbo
            frame set to 9000.
        c.  Misreporting of CRC error statistics.
        d.  2C_OffloadChecksum failures with the fiber adapter.


2.29        08/25/01

    Fixed the follwing issues:
        a.  2m_standby Ndis test failures on OEM 8450 machine.
        b.  Driver fails to load when the adapter is behind an IBM PCI-X bridge.


2.28        08/23/01

    Fixed the following issues:
        a.  When receive checksum is enabled on BCM5700, the driver may
            crash upon receiving a fragmented UDP datagram that is less than
            60 bytes.


2.27        08/22/01

    Fixed the following issues:
        a.  Ndis WOL test failures in pattern matching.
        b.  Crash on Windows .NET sending a packet that was double buffered.


2.26        08/19/01

    Fixed the following issues:
        a.  Windows 2000 intermittently locks up when entering standby or
            hibernate mode.


2.25        08/17/01

    Allow a way to get the actual bus speed on a PCI-X system.

    Fixed the following issues:
        a.  NT4 driver installation will failed if the driver for an adapter
            that previously occupied the same slot was not removed.
        b.  Fixed TCP segmentation certification failures.


2.24        08/14/01

    Changed the description of the Broadcom fiber adapter to
    "Broadcom NetXtreme Gigabit Fiber".

    Added WOL support for the new A3 chip.

    Fixed the following issues:
        a.  B57w2k.sys driver locks up when running Storage Consolidation.
        b.  The fiber adapter intermittently fails autonegotiation after
            resetting HP2524 switch.


2.23        08/02/01

    NT4 driver installation now checks for the presence of Service Pack 4 or
    greater.

    Fixed the following issues:
        a.  WOL speed was not properly set when shutting the system down.
        b.  B57xp32/64.sys drivers were not using NdisQueryBufferSafe which
            resulted in 1 failure in the 1c_KernelCalls test.
        c.  Failures in 1c_OffloadLargeSend.


2.22        07/31/01

    Fixed the following issues:
        a.  Fiber card back-to-back connection did not work on a PCI-X system.
        b.  BCM5700 crash on XP when telnet to a switch.
        c.  Driver crash after running ping for 30 minutes on an Athlon MP.


2.21        07/22/01

     Added LargeSend offload support.

     Enabled MagicPacket wake-up when the system shuts down.

     Fixed the following issues:
        a.  System crash on XP when enabling several instances at once.


2.19        07/17/01

    Fixed the following issues:
        a.  802.3z autonegotiation was not working reliably.
        b.  PHY loopback test was broken.


2.18        07/13/01

    Added support for Windows 95 Retail edition.

    Fixed the following issues.
        a.  System crash when running 2m_PerformanceBlast on an IA64 system.
            Under heavy traffic condition, the driver could miss an interrupt.
        b.  1c_Reset causes a system crash on Windows NT 4.0.  During a reset,
            a pended transmit request may not be properly completed.


2.17        07/10/01

    Added SGL support for the BCM5700 code path.  B57w2k will default to
    use the map registers and B57xp32/64 defaults to use SGL.

    Added a user configurable parameter for WOL speed.

    Fixed the following issues.
        a.  Driver was preventing the system from generating a dump file on
            system crash.


2.16        07/01/01

    Fixed the following issues.
        a.  Ndis resetting the miniport driver on the BCM5701 based fiber
            adapter when the cable is not connect.


2.15        06/28/01

    Added support for BCM5701 based fiber board.

    Fixed the following issues.
        a.  Intermitten running the 1c_FaultHandling script on Whistler with
            checked Ndis and DriverVerifier enabled.


2.14        06/19/01

    Removed all references to "Broadcom" from all OEM inf files.

    Fixed the following issues.
        a.  Possible memory leak in Windows 98 Retail edition.
        b.  Not indicate the correct link status to BASP.
        c.  Intermitten system crash when initializing the driver with the
            cable being plugged.
        d.  802.1p priority tag insertion was not done properly.


2.13        06/12/01

    Fixed the following issues.
        a.  Not initializing the chip's internal statistics counters to zero
            after a reset.
        b.  Intermitten system lock-up when transitioning to low power mode.
        c.  When forcing line speed, NdisTest complained about link status 
            indication during the WOL tests.

    Removed support for SGL.

    Added support for Windows 98 Retail edition to the b57w2k.sys binary.


2.12        06/01/01

    Fixed the following issues.
        a.  System crash on 2m_pblst.tst NdisTest.
        b.  Installation problem on NT4 when installing various OEM adapters
            at the same time.
        c.  Intermitten link indications at the end of WOL NdisTest.
        d.  System lock-up when booting up without a valid link.
        e.  Indicating received packets before Ndis sets the packet filter.
        f.  The default internal watermarks were configured for jumbo frame.

    Enable WOL at 10/100Mb on the new BCM5701 A1 chip.

    
2.11        05/23/01

    Added "RxClearTicksOnBd" and "TxClearTicksOnBd" registry key for configuring
    the 5701 interrupt mode.  By default, if these keys are not present,
    "RxClearTicksOnBd" is disabled and "TxClearTicksOnBd" is enabled.

    Tuned the driver for better performance on an MP system.


1.39        05/16/01

    Fixed the following issues:
        a. Low throughput with certain netperf test configuration in 100Mb mode.
        b. 802.1p was broken.
        c. Driver was reseting the statistics whenever there was a link change.


1.38        05/07/01

    Fixed the following problems.
        a. Oemsetup.inf generated "Parse error" when upgrading NT4.0 driver.
        b. Oemsetup.inf created multiple device entries when an older driver is
           already installed.
        c. Oemsetup.inf did not display the correct adapter string.

    Enabled WOL feature on Windows 9x driver.


1.37        05/04/01

    Fixed a bug in which a map register may not be freed.  On a PAE system,
    this bug will cause the system to crash when running the HCT test with
    driver verifier enabled.

    Added support for Ndis scatter-gather-list.  This mode is enabled by setting
    "UseSgl" keyword to 1 and it only works on the 5701.


1.36        05/02/01

    Fixed excessive interrupts problem.

    Modified link change dampening algorithm.  Originally, link change
    indications were delayed 1-2 seconds.  Now, link down indication is
    immediate and link up indication is delayed 1.5 seconds.

    Changed the driver description in the resource file to "Broadcom NetXtreme
    Gigabit Ethernet".

    Added "DpcLoopCnt" configurable parameter for capping DPC looping.


1.35        04/25/01

    Enhance the configurability of determining link change interrupt.  Added
    the following configurable parameters:

        "PhyIntMode"
            0   Auto select link change interrupt (default).
            1   Link change is triggered by the PHY interrupt.
            2   Link change is determined from the link ready signal.
            3   Link change is determined by auto-polling.  (5701 only)

            The default mode for 5700 is "1" and 5701 is "2".

        "LinkChngMode"
            0   Auto select the mechanism for determining link change status.
            1   Look at the MAC status register to get link change status.
            2   Look at the status block for link change status.  (5701 only).

            The default mode for 5700 is "1" and 5701 is "2".

        "Bcm540xMode"
            0   Auto select 540x LED mode based on the device's subsystem IDs.
            1   540x LED mode is set to "Triple Speed".
            2   540x LED mode is set to "LINK10".

    On the 5701, the status block size is configured to 80, 64, or 32 bytes 
    long depending on the number of rings enabled.

    Modified code to adjust the start of a receive buffer so that the payload
    will align at a 4-byte boundary.

    Modified b57w2k.inf to allow for generic installation.  The driver will
    check for supported devices and will fail if an unknown device is detected.

    Fixed the following issues:
        a.  No link up event after a PHY loopback test.


1.34        04/16/01

    Fixed problem in which an Ndis timer may not be properly disabled when
    unloading the driver.


1.33        04/11/01

    The following issues are fixed:
        a.  10Mbps not working.
        b.  PHY loopback failure in BASCS.

    Added support for "tagged status block" interrupt mode.

    Added support for Ndis 64-bit statistics counters.


1.32        04/03/01

    Added the "Athlon fix".  Enabled by default.

    Added support for BCM5701.


1.31        03/12/01

    Added support for the Agilent and BCM8002 SERDES (fiber boards).

    Added support for Windows Me and 98.

    Changed the severity of link down event message log to "Information"
    instead of "Error".

    Modified the driver to not log "Informational" messages to the EventViewer
    during initialization.  On a Windows 9x system, this will cause an
    undesirable error message box to popup after the system boots up.  This
    version of the driver will not log "Driver initialized successfully"
    message and link information during initialization.

    Added support for the new Fiber board with the BCM8002 SERDES.

    Enable LLC_LENGTH check when VLAN is not enabled.

    Added the "Dribble Bit" workaround.

    Fixed problem with the outgoing traffic being fragmented at 8190 byte
    boundary even when the jumbo frame size was set to 9000.


1.29        01/29/01

    Disable PCI-X relaxed ordering bit in the PCI-X command register.

    Changed DMA and MBUF watermarks when jumbo frame is enabled.


1.28        01/26/01

    Added support for PCI-X.

    Fixed system crash caused by running cable diagnostic in heavy traffic.


1.27        01/22/01

    Fixed intermitten crash on Whistler when entering lower power mode.  This
    was cause by the driver copying network wake-up frame beyond the give
    buffer.

    Added a workaround for the problem with not being able to DMA buffers that
    end at 0xfffffff8-0xffffffff address region.

    Driver will not switch to the auxilliary power if the system does not have
    it.

    Disallowed receiving packets bigger than 1514 but less than 1536 when
    jumbo frame is not enabled.

    Maximum jumbo frame size was changed from 8000 to 9000 bytes in b57nt4.hlp.


1.26        01/02/01

    Changed the way DPC is being serialized.

    Increased the maximum jumbo frame size to 9k.

    Added code to reset the PHY and wait for link during initialization.

    Fixed 1c_ofld.tst failure when only the transmit checksum is enabled.

    Modified the default interrupt coalescing parameters in b57w2k.inf and
    oemsetup.inf.

    Restore PCI subsystem and subvendor IDs on a reset.

    
1.25        12/22/00

    Added support for the B1 silicon.

    Fixed no link up interrupt.

    Fixed intermitten W2k system hang on boot up when there is no cable
    connected with Netbuei and Nwlink protocol installed.

    Modified b57w2k.inf to enable WOL and TX checksum offloading capabilities.

    Improved driver performance.


1.24        12/16/00

    Fixed problem with link functuation when coming out of hibernation mode.

    Fixed possible memory leak due to transmit packet descriptor not being
    freed up when the driver unloads.

    Cosmetic changes to oemsetup.inf and b57w2k.inf.

    Added code to check for subsystem vendor Id.


1.23        12/11/00

    Fixed an intermitten system crash when unloading the driver on a busy
    network.


1.22        12/09/00

    Fixed 1c_gtime failure when forcing 10mb full duplex on an HP 2424M switch.


1.21        12/07/00

    Shorten "Link Selection" items in b57w2k.inf and oemsetup.inf.

    Added software workaround to recover from link mismatch settings.  For
    example, the link partner is forced to 100mb and the adapter is forced
    to 10mb.


1.19        12/04/00

    Replaced "Driver" with "Controller" in b57w2k.inf and oemsetup.inf.

    Fixed a very intermitten MAC and PHY loopback failure.


1.18        12/01/00

    Removed TxMtu configurable parameter.  Now the user only has to configure
    RxMtu to enable jumbo frame support.

    5401 B0 silicon was not being resetted when the 1gb link went down.  The
    reset is required as software workaround for the 5401 errata.

    Driver will now restore a couple of PCI configuration registers after
    a reset.


1.17        11/29/00

    Added the ability to configure jumbo frame parameter in the b57w2k.inf.

    Fixed driver reporting wrong link status after reboot when forcing
    link speed on both sides.

    Fixed failure in MAC loopback test.


1.16        11/28/00

    Updated the 5401 tap power-management script.

    Removed the busy polling for link when unplugging the cable.  The polling
    period was too long and it was causing BASP to drop some Chariot
    connections.

    Removed support for A0, A1 silicon to reduce code size.


1.15        11/26/00

    Fixed intermitten system lock-up on shutdown when WOL is enabled.

    Multicast table was never cleared which was causing the intermitten
    failure in 2c_rmult.

    5401 reset on link down should occur only when the current speed is 1gb.

    Reduced driver load/unload time which will eliminate the 1c_gtime warnings.
    However, these warnings may still occur when WOL is enabled.  This is due
    to the driver waiting for auto-negotiation to complete before completing
    initialization.


1.14        11/22/00

    Added a software workaround for the 5401 to prevent it from locking up
    when the cable is unplugged during transmission.

    All the LEDs now indicate their corresponding link speed.

    
1.13        11/21/00

    Fixed problem with TCP connections dropping when running Chariot in
    10/100mb mode.

    Fixed problem with the adapter being disabled after exiting from the
    standby mode in Windows 2000.

    Fixed problem with the adapter not entering into wake-up mode when
    "shutdown".

    Ignore TX checksum parameter for B0 silicon.


1.12        11/18/00

    Added WOL support for Windows 2000.

    Fixed intermitten lock-up in 10mb mode.  Shadowed several MAC registers.

    Fixed PHY register read problem.  Occasionally PHY register read returned
    an incorrect value.

    Default TaskOffload and FlowControl parameter to off.


0.9         11/10/00

    Added MagicPacket support.

    In v0.8, whenever the driver detects a link mismatch, it will recover
    by switching to auto-negotiation mode.  This version does not have this
    recovery mechanism.

    Write the link settings to the EventLog after the driver has initialized.

    Fixed 1c_gtime failure when forcing line speed.


0.8         11/03/00

    NdisPacket allocated by the driver did not have the protocol reserved
    area which could cause system crash.

    Added a better handshaking mechanism with the firmware.

    Fixed the 2m_addres test.

    Added Compaq Hot Plug PCI support in oemsetup.inf.

    The MAC was not properly setup to operate in half duplex mode.

    Modified the driver to receive maximum sized VLAN packet without using
    the Jumbo receive ring.


0.7         10/30/00

    Fixed problems with forcing line speed.  

    Added checksum offloading capability.

    Fixed several issues with the Ndis test.  The following test should
    pass now:  1c_ofldn, 2m_load, 2m_misc, 2m_addre.

    Added support for IBM hot plug.


0.6         10/22/00

    Fixed lock-up that occurs when running the Ndis stress test.

    Fixed system crash when stopping the driver on an A1 silicon.

    Minor changes in b57nt4.hlp.

    Fixed problems with PHY loopback.  Added support for MAC loopback.

    Added a vendor specific OID for changing the MAC address.
    
    Tested VLAN tagging and 802.1p priority packet.


0.5         10/17/00

    Added a timer routine to periodically program the hardware to update
    the status block and generate an interrupt.  This is necessary because
    with A0, A1, B0 silicon, under certain condition, the host will miss
    interrupts.

    Disable PCI NWI by default.

    The send producer index is written twice.  This is a bug in the A0, A1, B0
    silicon in which chip will miss the mailbox stimulus.

    Added tx/rx PAUSE frame negotiation with link partner.  Modified b57w2k.inf
    to allow the user to configure rx/tx PAUSE frame independently.

    Fixed VLAN bug.  The driver was retrieving VLAN tag from the wrong offset
    in the miniport reserved area.

    Added jumbo frame support.  The user must manually modify the registry
    parameter to enable this feature.  "RxJumboDescCnt" must be changed
    to some value greater than 20 but less than 256.  This value determine
    the numbe of receive buffers to allocate for jumbo frames.

    Modified oemsetup.inf and b57w2k.inf to default "DisableAutoNeg" to 1,
    which will disable auto-negotiation advertisement when selecting a
    particular line speed.

    Added a help file for b57nt4.sys driver.


0.04        10/02/00
    Added support for link change detection via PHY interrupt as oppose to
    having the MAC poll the PHY.  PHY interrupt processing can be enable
    via "UsePhyInterrupt" registry parameter.  Default is "auto-polling".

    Miscellaneous modifications oemsetup.inf and b57w2k.inf.  Also fixed
    driver update issues with oemsetup.inf.

    Added delay before the driver is unloaded to prevent W2K from detecting
    the card as a different device.

    Fixed the deserialized driver to queue outgoing packets when there is no
    more packet descriptors left.


0.03        09/21/00
    Modified reset and halt routines to handle shutdown more robustly.  Some 
    systems will not recognize the board after a warm boot.  This version
    of the driver should fix this.

    
0.02        09/09/00
    Initial release for the A1 silicon.

Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: web2, load: 0.67