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

       Broadcom Management Application Programming Interface
                          for  Linux

          Copyright (c) 2000 - 2009 Broadcom Corporation
                      All rights reserved.
                          Aug 31, 2009



Version 6.6.0 (Aug 31, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Added support to return PHY ID for NX1 NICs.
      Change:
               Added support to return PHY ID for NX1 NICs.
      Impact:
               All NX1 NICs.

   Fixes:
   =====
   1. Problem: CQ43330
               The application might crash when bmapilnx tried to
               detect the iSCSI Boot status.
      Cause:
               The pointer passed to the function to detect the iSCSI
               Boot status can be out of boundary and became invalid.
      Change:
               Make sure the pointer passed to the function is within
               the boundary and valid.
      Impact:
               All NX1 and NX2 NICs.


Version 6.5.7 (Jul 02, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ42407
               The FwUpg tool can not show the device name of
               BCM5785 with AC131 PHY.
      Cause:
               Bmapilnx did not support the BCM5785 Fast Ethernet
               NIC.
      Change:
               Bmapilnx supports the BCM5785 Fast Ethernet NIC now.
      Impact:
               BCM5785 Fast Ethernet NIC.


Version 6.5.6 (Jun 30, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ42352
               The bmapilnx crashed during initialization in the
               PPC64 system.
      Cause:
               Bmapilnx crashed when trying to find out the iSCSI
               boot status from the PPC64 system.
      Change:
               Bmapilnx does not need to find out the iSCSI boot
               status from the PPC64 system since the feature is
               not supported in the PPC64 system.
      Impact:
               All adapters.


Version 6.5.5 (Jun 26, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem:
               FwUpg tool failed to upgrade the external PHY firmware
               for some adapters with BCM8727 PHY.
      Cause:
               Bmapilnx did not handle the external PHY type correctly.
      Change:
               Bmapilnx handles the external PHY type correctly.
      Impact:
               Some adapters with BCM8727 PHY.


Version 6.5.4 (Jun 25, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Added support to BCM5785.
      Change:
               Added support to BCM5785.
      Impact:
               BCM5785 adapter.

   2. Request:
               Added support to external PHY firmware upgrade.
      Change:
               Added support to external PHY firmware upgrade.
      Impact:
               External PHY firmware upgrade.


Version 6.5.3 (Jun 05, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ39514
               The "write error: Broken pipe" error message was displayed
               when running diagnostic tests for bonding NICs.
      Cause:
               Bmapilnx treated the master bonding NIC as a physical NIC and
               tried to collect information from it and caused the error.
      Change:
               Bmapilnx will exclude any master bonding NIC when collecting
               information for all physical NICs.
      Impact:
               System with bonding adapters.


Version 6.5.2 (May 29, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ40879
               Some BCM5708 NICs were not detected by FwUpg tool in
               the ESX4.0 system.
      Cause:
               Bmapilnx did not interpret the bus information of these NICs
               correctly.
      Change:
               Bmapilnx interprets the bus information of these NICs
               correctly now.
      Impact:
               All adapters.


Version 6.5.1 (May 20, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ39974
               Added support to BCM5761S.
      Change:
               Added support to BCM5761S.
      Impact:
               BCM5761S adapter.

   Fixes:
   =====
   1. Problem: CQ40058
               Bmapilnx failed to return the correct result of
               MII Register Test.
      Cause:
               Bmapilnx did not handle the returned error by driver
               correctly.
      Change:
               Bmapilnx handles the returned error by driver correctly
               and return it to the application.
      Impact:
               All adapters.


Version 6.5.0 (Feb 27, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ38776
               Added support to BCM5716S.
      Change:
               Added support to BCM5716S.
      Impact:
               BCM5716S adapter.

   2. Request:
               Added support to BCM57760/57780/57790.
      Change:
               Added support to BCM57760/57780/57790.
      Impact:
               BCM57760/57780/57790 adapters.

   Fixes:
   =====
   1. Problem: CQ38701
               Bmapilnx failed in API BmapiGetFwInfo() for BCM57790.
      Cause:
               BCM57790 was not supported in Bmapilnx.
      Change:
               BCM57790 is now supported in Bmapilnx.
      Impact:
               BCM57790 adapter.


Version 6.4.10 (Nov 12, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ38109
               Some NICs were not detected by bmapilnx in VMware ESX
               4.0 system.
      Cause:
               These NICs were assigned bus number that were equal or
               larger than 10.  The Bus_Info string returned in Ethtool
               interface has the bus number, device number, and function
               number that are in decimal, instead of hex.  The hex
               format was used in RedHat, SuSE and VMware ESX 3.x system.
               With incorrect bus/device/function numbers, the
               bmapilnx could not detect these NICs.
      Change:
               The bmapilnx will retrieve the bus/device/function numbers
               returned in Bus_Info string based on the OS.  For VMware
               ESX4, the bus/device/function numbers are in deciaml.
      Impact:
               NICs that are assigned with bus number that were equal or
               larger than 10 in VMware ESX4 system.


Version 6.4.9 (Oct 28, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Make some internal functions to be invisible during
               linking time.
      Change:
               These internal functions are only visible within bmapilnx.
      Impact:
               None.


Version 6.4.8 (Oct 22, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ37770
               The LED test will continue forever with the tg3 driver,
               v3.90b and above.
      Cause:
               The new driver interpreted the default value passed by
               bmapilnx differently.  The value is used for the duration
               of the LED test.
      Change:
               The bmapilnx will pass a correct value for the duration
               of the LED test, instead of the default value.
      Impact:
               LED test.


Version 6.4.7 (Oct 07, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ36507
               Added support to device name that is not "eth*".
      Change:
               Added support to device name that is not "eth*".
      Impact:
               All adapters.


Version 6.4.6 (Sep 29, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ36439
               Added support for 57710/5709 NICs in PPC64 environment.
      Change:
               Added support for 57710/5709 NICs in PPC64 environment.
      Impact:
               NX2 adapters in PPC64 environment.

   2. Request: CQ36847
               Added FWUPG tool to support NX2 adapters for Linux on
               PPC64 system.
      Change:
               Added FWUPG tool to support NX2 adapters for Linux on
               PPC64 system.
      Impact:
               NX2 adapters in PPC64 environment.

   Fixes:
   =====
   1. Problem: CQ37501
               The FWUPG tool for NX2 NIC does not work on PPC64 system.
      Cause:
               The FWUPG tool does not support NX2 NICs on PPC64 system.
      Change:
               Added FWUPG tool to support NX2 adapters for Linux on
               PPC64 system.
      Impact:
               NX2 adapters in PPC64 environment.


Version 6.4.5 (Jul 17, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Added support for BCM5716 NIC.
      Change:
               Added support for BCM5716 NIC.
      Impact:
               BCM5716-based adapter.


Version 6.4.4 (Jun 25, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ35789
               The version stinrg for BootCode1 was not returned
               correctly in BmapiGet5706FwInfo() for BCM5709.
      Cause:
               The BMAPILNX did not locate the BootCode1 version
               string in the NVRAM correctly for some BCM5709 NICs
               due to the setting for the flash type.
      Change:
               The BMAPILNX should locate the BootCode1 version
               string without checking the flash type since the
               BCM5709 NIC does handle the address translation
               for different flash type internally.
      Impact:
               BCM5709 NIC.


Version 6.4.3 (Jun 23, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ35467
               To support BCM57711E NIC.
      Change:
               Added support to BCM57711E NIC.
      Impact:
               BCM57711E NIC.


Version 6.4.2 (May 30, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ34237
               After upgrading the firmware, the default route using
               the NIC would be lost.
      Cause:
               After upgrading the firmware, the application bring
               down and up the NIC by manipulating the interface flag.
               During this process, the default route using the interface
               was not recovered and lost.
      Change:
               The bmapilnx will use a different method to bring down
               and up the NIC if a default route is using the interface.
               The default route is recovered.
      Impact:
               All NetXtreme adapters.


Version 6.4.1 (May 23, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ35448
               The SERDES bootcode file can't be used to upgrade
               the BCM5708S NIC with a Remote PHY.
      Cause:
               The BCM5708S NIC with a Remote PHY was detected as
               BCM5708C because the TP (twisted pair) media interface
               in the Remote PHY and the SERDES bootcode file was not 
               allowed to upgrade to a BCM5708C NIC.
      Change:
               The BCM5708S NIC with a Remote PHY is now detected
               correctly and the SERDES bootcode file is allowed to
               upgrade to the NIC.
      Impact:
               NetXtreme adapters with Remote PHY.


Version 6.4.0 (Apr 16, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: 
                To support NCSI version string.
      Change:
                The NCSI version string was returned in
                BmapiGet5706FwInfo and BmapiGet57710FwInfo.
      Impact:
                All adapters.


Version 6.3.48 (Mar 28, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ33942
               Unknown device for BCM5723 adapter.
      Cause:
               The BCM5723 device ID was not recognized by bmapilnx.
      Change:
               The BCM5723 device ID was added to the adapter list.
      Impact:
               BCM5723 adapters.


Version 6.3.47 (Mar 07, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem:
               NVRAM access is slow for BCM5761 adapter.
      Cause:
               The NVRAM was detected as SEEPROM.
      Change:
               The NVRAM is now detected as Flash.
      Impact:
               BCM5761 adapters.


Version 6.3.46 (Jan 22, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem:
               The FWUPG "cfg -mac <mac address>" command does
               not work correctly for BCM5764M/BCM5784M adapter.
      Cause:
               The new MAC address was written to NVRAM, but it
               can't be retrieved from NVRAM because the BCM5764M/
               5784M adapters were not recognized as supported
               NICs by the bmapilnx.
      Change:
               The bmapilnx can now recognize the BCM5764M/5784M
               as valid NICs and the new MAC address can be
               retrieved correctly from NVRAM.
      Impact:
               BCM5764M/5784M-based adapters.


Version 6.3.45 (Jan 07, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support BCM5764M, BCM5784M and BCM5761 NICs.
      Change:
               Added support to BCM5764M, BCM5784M and BCM5761 NICs.
      Impact:
               BCM5764M, BCM5784M and BCM5761 NICs.
               The Linux tg3 driver v3.83 or above is required for
               this feature.


Version 6.3.44 (Nov 13, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:
               Adapter without cable connection was reported as a
               down interface.
      Cause:
               The "Running" flag of the interface was checked to
               determine if the interface is "Up".  The interface
               is not "Running" if the cable is not connected.
      Change:
               The "Up" flag of the interface was checked to determine
               if the interface is "Up".
      Impact:
               All adapters.


Version 6.3.43 (Nov 12, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:
               Memory leak occurred when BmapiRefreshData() function
               is used by application.
      Cause:
               Memory allocated previously for the internal data was
               not freed completely while new memory was allocated
               for the refresh data.
      Change:
               Make sure the memory allocated previously was freed
               completely.
      Impact:
               All applications that use BmapiRefreshData() function.


Version 6.3.42 (Nov 07, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ32211
               NMI/SMI occurred when one interface of BCM5709 was down.
      Cause:
               The register were accessed when the device was in D3-hot
               state.
      Change:
               Make sure the device's registers are not accessed when
               the device is in D3-hot state.
      Impact:
               All NetXtreme II adapters.


Version 6.3.41 (Nov 01, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:
               Some commands in FWUPG utility for NetXtreme I adapter
               do not work correctly.
      Cause:
               The nic_type of NetXtreme I adapter was corrupted due
               to a bug injected in v6.3.40 release.
      Change:
               The bug is fixed and the nic_type of NetXtreme I
               adapter is now correct.
      Impact:
               All NetXtreme I adapters.


Version 6.3.40 (Oct 22, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support BCM57710 NIC.
      Change:
               Added support to BCM57710 NIC.
      Impact:
               BCM57710 NIC.
               The Linux bnx2x driver v0.40.10 is required for this feature.


Version 6.3.39 (Sept 17, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:
               Report 5722 as C0 while it is A0.
      Cause:
               Not properly read out chip ID
      Change:
               Read out chip ID correctly.
      Impact:
               5722 chip revision

   2. Problem: CQ31440
               Segmentation fault for NX1 adapter on RH4U5-32.
      Cause:
               The PCI config data were not read correctly from
               the /sys/bus/pci/devices file system.
      Change:
               The PCI config data are retrieved correctly from
               the /sys/bus/pci/devices file system.
      Impact:
               All adapters.


Version 6.3.38 (Sept 14, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ28989
               BMAPILNX does not detect BRCM adapters correctly
               on the IBM Cell blade.
      Cause:
               The domain number of PCI device was not supported.
      Change:
               Each PCI device is uniquely identified by the
               domain:bus:device.function.  All the PCI config
               data are retrieved from /sys/bus/pci/devices
               directory if it is supported.  Otherwise, they
               are retrieved from /proc/bus/pci directory. 
      Impact:
               All adapters.


Version 6.3.37 (July 13, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support BCM5709 NIC.
      Change:
               Added support to BCM5709 NIC.
      Impact:
               BCM5709 NIC.
               The Linux bnx2 driver v1.6.3b is required for this feature.


Version 6.3.36 (May 03, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ29318
               BMAPILNX does not support VMAC.
      Cause:
               The VMAC was not stored correctly in the field
               that is used by all the applications.  Instead,
               The permanent MAC address was returned.
      Change:
               For Linux kernel 2.6.14 and above, the permanent
               MAC address is retrieved by the ETHTOOL_GPERMADDR
               ioctl which will return the correct VMAC/permanent MAC.
               If the driver does not support the ETHTOOL_GPERMADDR
               ioctl, the permanent MAC address is retrieved from
               NVRAM.  For Linux that is below 2.6.14, the 
               ETHTOOL_GPERMADDR is not supported and the
               permanent MAC address is retrieved from NVRAM.
      Impact:
               All adapters.


Version 6.3.35 (Mar 12, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:
               BMAPILNX can get into an infinite loop when an
               ETHTOOL_GLINK ioctl command failed.
      Cause:
               The error handling code jumped to a location that
               will try to issue the ETHTOOL_GLINK ioctl again.
      Change:
               The error handling code posted an error message
               and exited when the ETHTOOL_GLINK ioctl failed.
      Impact:
               All adapters.


Version 6.3.34 (Feb 28, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ28659 
               Device list in lnxfwupg is not displayed properly.
      Cause:
               The brcm_pci.ids in the bmapilnx RPM contains 'CR'
               and 'LF' at the end of each device name string.
      Change:
               Ran a script to eliminate the 'CR' at the end of each
               device name string in brcm_pci.ids before making the
               bmapilnx RPM.
      Impact:
               All adapters.

Version 6.3.33 (Jan 02, 2007)
---------------------------------

   Fixes:
   ======
   1. Problem:  
               Ethtool interface does not work in Xen Linux.
               See CQ#26795 for detail.
      Cause:
               The Xen package will virtualize network devices.
               The virtual nic driver supports limited Ethtool operations.
      Change:
               BMAPI will use either ethN or pethN to issue the Ethtool IOCTL
               to the driver.  Under Xen Linux, the physical device can be
               either ethN or pethN depending on if the network-bridge is
               started.
      Impact:
               Under single Xen Linux, the BMAPI can work correctly with Ethtool.
               System with multiple Xen Linux OSes is not tested.

Version 6.3.32 (November 30, 2006)
---------------------------------

   Fixes:
   ======
   1. Problem:  
               Adapter was incorrectly reported with bad bootstrap magic.
      Cause:
               Incorrect structure was used in the routine to retrieve 
               mac address for adapters loaded with tg3 driver.
      Change:
               Fix the routine to use the correct structure.
      Impact:
               MAC address for adapters loaded with tg3 driver.


   2. Problem:  
               Lib64 search path for ppc needs to be fixed.
      Cause:
               The linker specified in previous releases caused the 
               wrong loader path to be hard coded in the ELF file.
      Change:
               Rework ConTestApp/Makefile to use the system default 
               compilers and linker with proper CFLAGS and LFLAGS 
               options.
      Impact:
               The reported message "bad ELF interpreter" should not 
               be seen when running BMAPILNX/ConTestApp on any PPC 
               platform.


Version 6.3.31 (November 21, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support 5906 based chips.
      Change:
               Added support to handle the above chips.
      Impact:
               All releted APIs.

   2. Request: 
               CQ22475 - Need BMAPI support to enable/disable IPMI.
      Change:
               Enhance BmapiSetASFTable() to support enable/disable
               IPMI. Applicable changes were rolled over from Windows
               BMAPI v7.5.8.
      Impact:
               Note that applications can only enable/disable IPMI.
               No other configuration settings are allow to set.
               This limitation had been communicated to OEM and
               accepted.
               BmapiSetASFTable().


Version 6.3.30 (November 14, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               CQ26481 - Method for getting UMP version for 
               multifunction NICs.
      Change:
               Added new fields in BM_FW_INFO and BM_FW_INFO_5706 to 
               support new types of firmware.
      Impact:
               1. BM_FW_INFO and FW_FW_INFO_5706 in BMAPI.h.
               2. BmapiGet5706FwInfo() and BmapiGetFirmwareInfo().

   2. Request: 
               To handle bond ID properly for Stanford chips.
      Change:
               Use Stanford chips bond ID mask.
      Impact:
               All Stanford chips.

   Fixes:
   ======
   1. Problem: 
               1. CQ26991 
                  lnxfwupg will not upgrade bootcode or IPMI for 5704.
               2. CQ27119 
                  lnxfwupg cannot enable IPMI on both 5704c ports 
                  simultaneously
      Cause:
               The nvram was write protected making the write operation
               unsuccessful. 
      Change:
               Ensure write protect was properly handled upon
               programming the device.
      Impact:
               BmapiSetASFTable()
               BmapiWriteFirmware()
               BmapiWriteFirmwareInfo()

               Note:
               The changes only apply to dual-port LOM devices with
               SEEPROM in the 5704/5714/5715/5780 family.

   2. Problem: CQ27394: 
               PCI.IDS file left open after BMAPI close.
      Cause:
               Previous releases left pci.ids file open even after
               BmapiUninitialize().
      Change:
               Ensured to close pci.ids file as soon as the file is
               no longer needed.
      Impact:
               pci.ids should not be left open after BmapiUninitialize().

   3. Problem:
               CQ26833 - PXE version string displayed incorrect info.
      Cause:
               Previous releases used a 16-bit mask to get the PXE 
               version offset. When its offset exceeded 0x10000, the 
               retrieved version information was then incorrect.
      Change:
               Fixed the related routine to use 32-bit mask.
      Impact:
               BmapiGetFirmwareInfo()


Version 6.3.29 (November 1, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request:  
               To provide symbolic link between /usr/lib64 and /usr/lib
               for libbmapi_x64.
      Change:
               Modified the rpm installation for x86_64 to create 
               symbolic link between /usr/lib64 and /usr/lib for 
               libbmapi_x64, the 64-bit library for x86_64.
      Impact:
               The rpm for x86_64 should create symbolic link between
               /usr/lib64 and /usr/lib for libbmapi_x64.

   2. Request: 
               To update BM_FW_MEDIA_MANUFACT_REGION. 
      Change:
               Updated the required structures in BMAPI.h. 
      Impact:
               BMAPI.h

   Fixes:
   =============
   1. Problem: CQ27090       
               Linux Firmware Update utilities caused Seg Fault if PCI 
               IDs file not present.
      Cause:
               Previous BMAPILNX assumed that pci.ids would be always
               present. The segmentation fault was caused by an invalid
               access to a non-existent file in BMAPILNX.
      Change:
               Added code to handle the reported case when pci.ids is
               not found on the system..
      Impact:
               No segmentation fault should be observed at any time. 
               If the system has no pci.ids file, "Unknown device"
               will be reported in the device title.


Version 6.3.28 (Sept. 28, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ26383
               To provide better search path to locate brcm_pci.ids. 
      Change:
               Implemented the search path priority as requested in
               the following order.
                  Priority 1: The path set by $BMAPI_PCI_LOCATION.
                  Priority 2: The $PWD path for current directory. 
                  Priority 3: The /usr/share directory.
      Impact:
               brcm_pci.ids can be located from one of the above paths.
               readme.txt was updated to document this change.

   Fixes:
   =============
   1. Problem:         
               lnxfwupg failed to configure MAC address for the 2nd
               port on a 5704 device.
      Cause:
               The 2nd port information was retrieved from an incorrect 
               location. 
      Change:
               To retrieve the 2nd port information from the related
               device register.
      Impact:
               Dual port devices.


Version 6.3.27 (July 11, 2006)
---------------------------------

   Fixes:
   =============
   1. Problem: CQ25713       
               lnxfwupg reports MAC address swapped on dual port NICs.
      Cause:
               Previous version did not consider port swapped cases.
      Change:
               Corrected the code to cover port swapped cases.
      Impact:
               MAC address should always be reported correctly for
               all NICs.


Version 6.3.26 (June 30, 2006)
---------------------------------

   Fixes:
   =============
   1. Problem: CQ25237       
               BCM5786 was reported as "Unknown device".
      Cause:
               brcm_pci.ids was not updated to include new devices.
      Change:
               Updated brcm_pci.ids to include new devices. 
      Impact:
               No Broadcom device should be reported as "Unknown device".


Version 6.3.25 (June 8, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To update BM_ASF_CFG, BM_FW_FEATURE_CONFIG, 
               BM_NIC_SHARED_CONFIG, BM_FW_MEDIA_MANUFACT_REGION.
      Change:
               Updated the required structures in BMAPI.h. 
      Impact:
               BMAPI.h

   Fixes:
   =============
   1. Problem: CQ25237       
               BCM5786 was reported as "Unknown device".
      Cause:
               brcm_pci.ids was not updated to include new devices.
      Change:
               Updated brcm_pci.ids to include new devices. 
      Impact:
               No Broadcom device should be reported as "Unknown device".

   2. Problem:        
               To rebuild BMAPILNX with gcc v3.2.3 on Red Hat Enterprise 
               Linux 3.0.
      Cause:
               Previous versions were built with gcc v2.96 on Red Hat 
               7.3 release.  
      Change:
               Re-build BMAPILNX with gcc v3.2.3 on Red Hat Enterprise 
               Linux AS release 3 (Taroon Update 6).
      Impact:
               BMAPILNX is not built on gcc v3.2.3.


Version 6.3.24 (May 31, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To make all APIs available to support the firmware 
               upgrade utilities for ppc64 platform.
      Change:
               Modified BmapiWriteNicMem(), BmapiReadNicMem(), and 
               associated internal routines.
      Impact:
               BmapiWriteNicMem() 
               BmapiReadNicMem()

   Fixes:
   =============
   1. Problem:        
               Each port in a dual-port NIC should have its own
               permanent mac address.
      Cause:
               Previous version only retrieve the mac address for
               the 1st port.
      Change:
               Retrieved 2nd port permanent mac address from firmware. 
      Impact:
               BmapiGetBRCMNicInfoEx()
               BmapiGetPhyNic()

               In addition to the existing functionalities, the above
               two APIs will retrieve permanent mac address for all
               Broadcom supported dual-port NICs loaded with "tg3" or 
               "bnx2" driver.


Version 6.3.23 (May 19, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               Need to provide permanent mac address to support both 
               lnxfwnx2 and lnxfwupg firmware upgrade tools.
      Change:
               Added routines to retrieve permanent mac address from 
               firmware and modified all associated APIs.
      Impact:
               BmapiGetBRCMNicInfoEx() and its man page.
               BmapiGetPhyNic() and its man page.

               In addition to the existing functionalities, the above
               two APIs will retrieve permanent mac address for each
               Broadcom supported NIC loaded with "tg3" or "bnx2" driver.


Version 6.3.22 (May 5, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request:  
               To provide NVRAM size for 5706 devices.
      Change:
               Request NVRAM size from bnx2 driver and provide the 
               inforamtion to applications.
      Impact:
               BmapiGetBRCMNicInfoEx().

   2. Request: 
               To make all APIs needed to support the firmware upgrade 
               utilities available.
      Change:
               Modified BmapiWriteNicMem(), BmapiReadNicMem(), and 
               associated internal routines.
      Impact:
               BmapiWriteNicMem() 
               BmapiReadNicMem()

   Fixes:
   =============
   1. Problem:        
               Make sure only qualified drivers are allowed to access ASF
               table.
      Cause:
               Previous version should only restrict qualified NICs with
               supported driver names to access ASF table.
      Change:
               Added the additional checking in the related routine.
      Impact:
               Any non-supported driver should not be able to access ASF
               table.


Version 6.3.21 (March 28, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support x86_64 and ppc64 architectures on the 
               following platforms:
               -  RedHat Enterprise Linux 3.0 (please refer to
                  "Known Limitations" in readme.txt)
               -  RedHat Enterprise Linux 4.0 
               -  Suse Linux Enterprise Server 9.0
               -  Suse Linux Professional 10.0
      Change:
               1. For x86, bmapilnx RPM package remains the same 
                  to provide 32-bit library (libbmapi).
               2. For x86_64, bmapilnx RPM package is added to 
                  provide 32-bit library (libbmapi) and 64-bit 
                  library (libbmapi_x64).
               3. For ppc64, bmapilnx RPM package is added to
                  provide 64-bit library (libbmapi_ppc64).
      Impact:
               1. On x86 platforms, bmapilnx RPM package and 32-bit
                  library (libbmapi) remain intact.
               2. On x86_64 platforms, bmapilnx RPM package will
                  install 32-bit library (libbmapi) and 64-bit library 
                  (libbmapi_x64).
                  With this RPM installation, the 32-bit library 
                  (libbmapi) is available to serve 32-bit applications 
                  as usual. In addition, the 64-bit library (libbmapi_x64) 
                  can be linked to run with 64-bit applications.
               3. On ppc64 platforms, bmapilnx RPM package will install 
                  64-bit library (libbmapi_ppc64).
               4. Upon installation, each RPM package should be ensured 
                  and loaded only on the supported CPU platform.
               5. readme.txt and associated man3 pages.

   2. Request: 
               To add BmapiWriteFirmwareInfo() and its man page
               for Linux.
      Change:
               Added BmapiWriteFirmwareInfo().
      Impact:
               BmapiWriteFirmwareInfo() and associated man3 pages.


Version 6.3.20 (March 7, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ23682 
               To update readme.txt for a known problem
               in Linux kernel causing BMAPILNX to report
               error code 58 when running tg3.
      Change:
               Modified "Known Limitations" in readme.txt.
      Impact:
               readme.txt and RPM package.


Version 6.3.19 (March 3, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support 5754, 5755, and 5787 chips.
      Change:
               Added support to handle the above chips.
      Impact:
               All releted APIs.

   2. Request: 
               To support selfboot feature for 5787 chip.
      Change:
               Modified related APIs to support selfboot feature.
      Impact:
               1. BmapiGetFirmwareInfo() and BmapiWriteFirmwareInfo().
               2. BmapiGetASFTable() and BmapiSetASFTable().

   3. Request: 
               To add BmapiEnableDevice() and BmapiGet5706FwInfo() 
               for Linux.
      Change:
               Added BmapiEnableDevice() and BmapiGet5706FwInfo().
      Impact:
               BmapiEnableDevice() and BmapiGet5706FwInfo() and
               associated man3 pages.
   
   4. Request: 
               To support x86 for 32-bit and x86_64 for 64-bit
               architecture on the following platforms:
               -  RedHat Enterprise Linux 3.0 (x86 only, please 
                  refer to "Known Limitations" in readme.txt)
               -  RedHat Enterprise Linux 4.0 
               -  Suse Linux Enterprise Server 9.0
               -  Suse Linux Professional 10.0
      Change:
               Implemented all changes as required.
      Impact:
               1. Makefile, build environment, and readme.txt.
               2. 32-bit and 64-bit binaried are available for
                  the supported platforms.
 
   Fixes:
   =============
   1. Problem: CQ23451       
               Newly changed IP did not respond to RCMP pings before
               the NIC was brought down and up.
      Cause:
               The suspend and resume driver functions for tg3 
               were not handled properly.
      Change:
               Fixed the code to suspend and resume the device loaded 
               with tg3 driver.
      Impact:
               BmapiSuspendDriverEx()
               BmapiResumeDriverEx()

   2. Problem:        
               To roll over applicable fixes for CQ22654 and CQ22336
               submitted to Windows BMAPI.
      Cause:
               CQ22654, the register value was affected by the link status.
               CQ22336, HW/BIOS problem.
      Change:
               Rolled over the applicable fixes from Windows BMAPI 
               between v7.3.10 and v7.3.15.
      Impact:
               BmapiTestControlRegisters()
               BmapiTestControlRegistersEx()
               BmapiTestEEPROM() 
               BmapiTestEEPROMEx()


Version 6.3.18 (November 3, 2005)
---------------------------------

   Fixes:
   =============
   1. Problem:        
               To remove the unwanted output message from stdout.
      Cause:
               An informational printf() remained in the code.
      Change:
               Removed the extra printf() statement.
      Impact:
               The output message showing "PCI_IDS_FILE found at ..."
               is removed.


Version 6.3.17 (October 28, 2005)
---------------------------------

   Fixes:
   =============
   1. Problem:        
               BmapiSetASFTable() should not able to change
               configuration for IPMI and UMP.
      Cause:
               The API did not check for the type of management
               firmware in NVRAM.
      Change:
               Rolled over applicable fixes submitted to Windows 
               BMAPI between v7.2.16 and v7.3.9.
      Impact:
               BmapiSetASFTable()

   2. Problem:        
               Need to restore the memory value after memory test.
      Cause:
               The original algorithm did not restore the memory value
               upon completion of the memory test. 
      Change:
               Implemented memory test to read out the memory value, 
               do the test and then restore the memory value.
      Impact:
               BmapiTestInternalMemoryEx().


Version 6.3.16 (October 10, 2005)
-----------------------------------

   Fixes:
   =============
   1. Problem: Error returned from BmapiGetASFTable() while running
               ASFSCFG on a HTLE LOM with tg3 driver 3.41b.
      Cause:
               The internal algorithm missed to implement the 
               ethtool access for the 2-port devices.
      Change:
               Added the ethtool access for the 2-port devices.
      Impact:
               The ASF capabilities should be available to all tg3 
               based adapter with driver version >=3.37 on the Linux
               systems capable of accessing EEPROM via "ethtool -e". 

   2. Problem: CQ13653
               BmapiInitializeEx() seems very slow on a freshly loaded
               Linux system.
      Cause:
               The internal algorithm used the 'locate' command to 
               look up the pci.ids on the system.  Unfortunately,
               the 'locate' command is not immediately available on 
               some freshly loaded Linux systems, thus causes some 
               delay.
      Change:
               Modified the internal algorithm not to depend on the 
               'locate' command.
      Impact:
               The call to BmapiInitializeEx() should not cause any
               slowness even on a freshly loaded system.
                     

Version 6.3.15 (September 29, 2005)
-----------------------------------

   Enhancements:
   =============
   1. Request:
               Do not perform MAC loopback for HTLE devices.
      Change:
               Made MAC loopback test unavailable to HTLE devices.
      Impact:
               No MAC loopback test for HTLE devices.

   Fixes:
   =============
   1. Problem:       
               Should not report any Broadcom NICs as "Unknown device".
      Cause:
               The pci.ids file on the Linux system ws not updated with
               the latest version from http://pciids.sourceforge.net.
      Change:
               Include brcm_pci.ids in the bmapilnx rpm package and
               install the file at /usr/share upon 'rpm -i' for
               bmapilnx installation.
               For any Broadcom devices, bmapilnx will look up
               information from /usr/share/brcm_pci.ids; otherwise,
               it will go for the pci.ids on the system.
      Impact:
               No Broadcom devices should be reported as "Unknown".
                       

Version 6.3.14 (August 31, 2005)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To add diagnostics support for both tg3 and bnx2 
               based adapters.
      Change:
               Implemented the requested support in all related 
               functions.
               The following diagnostic tests were added for all 
               tg3 adapters (driver version >=3.37) and all bnx2
               based adapters (driver version >=1.3.25).
                   BRCM Control Registers
                   BRCM MII Registers
                   BRCM EEPROM
                   BRCM Internal Memory
                   BRCM Interrupt
                   BRCM MAC Loopback
                   BRCM PHY Loopback
                   BRCM LED
      Impact:
               All APIs to support the diagnostic functionalities.
               The above diagnostic tests are available to all tg3 
               adapters with driver version >=3.37 and all bnx2
               based adapters with driver version >=1.3.25.

   2. Request: 
               To add ASF support for tg3 based adapter.
      Change:
               Added the requested support in all related functions.
      Impact:
               All APIs to support the ASF functionalities.
               The ASF capabilities are available to all tg3 based 
               adapters with driver version >=3.37.

   3. Request: 
               To make statistics information and additional adapter
               information available to both tg3 and bnx2 based 
               adapters.
      Change:
               Added the requested support in all related functions.
      Impact:
               All APIs to support the requested functionalities.
               The statistics information and additional adapter
               information are available to all tg3 based adapters 
               with driver version >=3.37 and all bnx2 based adapters 
               with driver version >=1.3.25.


Version 6.3.13 (April 26, 2005)
---------------------------------

   Fixes:
   =============
   1. Problem:        
               Roll over CPU test fixes for CQ12698 from Windows BMAPI.
      Cause:
               When driver verifier is enabled on the system, the
               slower timing will intermittantly cause test firmware
               to fail to access NVRAM due to CPU reset and halt.
      Change:
               Merge with the CPU test fixes from Windows BMAPI 
               v7.2.15.
      Impact:
               BmapiTestCPU() and BmapiTestCPUEx() on all 570x chips.

   2. Problem:        
               Need to update BM_FW_MEDIA_MANUFACT_REGION.
      Cause:
               New fields were added to media_manufact_region_t in
               include/media_rgn.h.
      Change:
               Updated BM_FW_MEDIA_MANUFACT_REGION and related 
               functions accordingly.
      Impact:
               BmapiGetFirmwareInfo().


Version 6.3.12 (Mar. 09, 2005)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To remove 0x2018 from register test for 5750 chips.
      Change:
               Removed 0x2018 from the register list.
      Impact:
               Register Test.

              
Version 6.3.11 (Feb. 24, 2005)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To support 5714 and 5752 chips.
      Change:
               Added support to handle 5714 and 5752 chips.
      Impact:
               All.

              
Version 6.3.10 (Feb. 1, 2005)
---------------------------------

   Fixes:
   =============
   1. Problem: CQ11272
               BMAPILNX failed to access pci.ids file.
      Cause:
               Unlike other linux systems, some SuSE 9 systems do not 
               recognize the -n option in the "locate -n 1 pci.ids" 
               command, some do not even recognize the "locate" 
               command.
      Change:
               Change algorithm to locate the file through the faster
               command "locate -n 1 pci.ids" first. For systems not
               recognizing the -n option, "locate pci.ids" will be 
               used. At last, the slow "find" command available on all
               systems should be able to locate the file.
      Impact:
               BMAPILNX should be able to locate the pci.ids on all
               systems. 


Version 6.3.9 (Jan. 3, 2005)
---------------------------------

   Fixes:
   =============
   1. Problem: CQ11099
               OLD should not cause OMSA to crash when running with 
               tg3 driver.
      Cause:
               The BMAPILNX stack was corrupted immediately after
               the ETHTOOL_GLINK ioctl() call.  This problem was
               only seen on Redhat AS2.1 with tg3 driver, ver 0.97.
      Change:
               Avoid making the ETHTOOL_GLINK ioctl() call when the
               driver is tg3 version 0.97.
      Impact:
               If the driver is tg3, version 0.97, the link status 
               can only be reported as Unknown. The algorithm for 
               the other drivers remains intact.


Version 6.3.8 (Dec. 17, 2004)
---------------------------------

   Fixes:
   =============
   1. Problem: CQ10828
               Need to support new loopback tests for bcm5700.
      Cause:
               The MAC/PHY/EXT loopback tests were not implemented by 
               the bcm5700 driver.
      Change:
               Changed algorithm to support the new loopback tests for
               the bcm5700 driver v7.4.12 and later versions. 
      Impact:
               The bcm5700 driver v7.4.12 and later versions should be
               able to exercise the MAC, PHY, and External loopback
               tests.  The old loopback algorithm for the earlier 
               bcm5700 dirvers remains intact.


Version 6.3.7 (Dec. 2, 2004)
---------------------------------

   Fixes:
   =============
   1. Problem:        
               pci.ids file should be accessible by applications
               interfacing with BMAPILNX even when the resource 
               file .bmapi.conf is not configured.
      Cause:
               The routine to locate the pci.ids file is not called
               when the resource file is not present.
      Change:
               Re-work the logic so that pci.ids can be successfully 
               located before checking the presence of the resource 
               file.
      Impact:
               All applications interfacing with BMAPILNX should be 
               able to locate the pci.ids regardless of the presence
               of the resource file.


Version 6.3.6 (Nov. 24, 2004)
---------------------------------

   Fixes:
   =============
   1. Problem: CQ11272
               BMAPILNX failed to access pci.ids file.
      Cause:
               The code used to depend on some pre-designated paths.
      Change:
               Change algorithm to locate the file without having to
               depend on some pre-designated paths.
      Impact:
               BMAPILNX should be able to locate the pci.ids on all
               systems. 

   2. Problem: 
               BMAPILNX needs to report ui_number for 64-bit machine.
      Cause:
               The internal access method was only good for the 
               32-bit machine but not for the 64-bit machine.
      Change:
               Change internal access method to locate the PCI IRQ 
               Routing Table for both 32-bit and 64-bit machines.
      Impact:
               The ui_number field should be reported correctly for
               the 64-bit machine.


Version 6.3.5 (Nov. 2, 2004)
---------------------------------

   Fixes:
   ======
   1. Problem: 
               Re-geneate RPM files to be backward compatible with
               applications using older version of gcc compiler.
      Cause:   
               RPM files generated on a later Redhat kernel using 
               newer version of gcc might introduce problems to a 
               dependent application using an older version of gcc. 
      Change:
               Re-generate RPM files on Redhat 7.3 (kernel/2.4.18-3;
               gcc/2.96)
      Impact:
               None.


Version 6.3.4 (Oct. 29, 2004)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               To provide L2 support for BRCM5706 open source driver.
      Change:
               Add the requested support in all related functions.
      Impact:
               All APIs with the following exceptions:
                  1. All APIs related to ASF/DIAG/TEST/Statistics 
                     remain intact.
                  2. The following APIs remain the same too. 
                     BmapiReadFirmware(), 
                     BmapiWriteFirmware,
                     BmapiGetFirmwareInfo(),
                     BmapiReadNicMem(),
                     BmapiWriteNicMem(),
                     BmapiGetBRCMNicInfoEx(),
                     BmapiGetBRCMNicStatistics(),

               The released version was tested on the following 
               Linux platforms:
                  - Redhat EL 3.0 (2.4.21-4.EL, i686)
                  - Redhat EL 3.0 Update 2 AMD64 (2.4.21-15.EL, x86_64)
                  - Redhat 4.0 Beta (2.6.8, x86_64)


Version 6.3.3 (Oct. 14, 2004)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               1. Change access method to get PCI configuration data.
               2. Remove use of /tmp/bmapi.lspci and /tmp/bmapi.tmp.
      Change:
               The access method of getting the PCI configuation data
               has been changed using a better algorithm. 
               In addition, the two files mentioned above are removed.
      Impact:
               User interface remains the same.


Version 6.3.2 (Oct. 8, 2004)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               Make BMAPILNX code base to be GNU clean and open source 
               compliant.
      Change:
               Re-worked some functionalities and cleaned up existing
               code.
      Impact:
               User interface remains the same.


Version 6.3.1 (Aug. 3, 2004)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               Add flags to indicate ASF 2.0 support in NIC
      Change:
               Add flags in BM_ASF_TABLE to indicate ASF 2.0
               capability.
      Impact:
               BM_ASF_TABLE


Version 6.3.0 (Jun. 7, 2004)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ10254
               implement BmapiGetFirmwareInfo() for Linux
      Change:
               add BmapiGetFirmwareInfo()
      Impact:
               BmapiGetFirmwareInfo()


Version 6.2.3 (Jun. 1, 2004)
---------------------------------

   Enhancements:
   =============
   1. Request: 
               Add support 5751F.
      Change:
               Add ID for 5751F.
      Impact:
               all

   1. Request: 
               Check for driver for diagnostics functions.
      Change:
               BmapiInitDiag() will check whether the driver name is
               bcm5700 or not. If the driver is not bcm5700, error
               code BMAPI_NOT_SUPPORTED_DRV will be returned.
      Impact:
               BmapiInitDiag()


Version 6.2.2 (Mar. 15, 2004)
---------------------------------

   Fixes:
   ======
   1. Request: CQ9504
               BMAPI does not recognize the updated ASF cfg table
      Cause:
               SQA is testing the new firmware with old BMAPI which
               does not have knowledge of the new data structure.
      Change:
               include the new ASF structure
      Impact:
               BmapiGetASFTable() and BmapiSetASFTable()


Version 6.2.1 (Feb. 20, 2004)
---------------------------------

   Fixes:
   ======
   1. Request: 
               Application may see link error and may experience
               error (Segmentation Fault)
      Cause:
               The static link option for BMAPI is not done
               correctly.
      Change:
               link option in make file
      Impact:
               all applications


Version 6.2.0 (Feb. 17, 2004)
---------------------------------

   Fixes:
   ======
   1. Request: 
               Install BMAPI RPM on RedHat Enterprise Server 3.0 may
               show error during installation.
      Cause:
               RPM stops installtion because the dependent version of
               C and/or C++ standard library does not exist on the
               system.
      Change:
               Link against static libraries.
      Impact:
               All applications but low risk.

   Enhancements:
   =============
   1. Request: 
               Add BmapiGetBRCMNicStatistics() (required by CDM
               provider).
      Change:
               Add statiscitcs support.
      Impact:
               none.

   2. Request: 
               Support 575x devices.
      Change:
               Add 575x support in related functions.
      Impact:
               All APIs.

   3. Request: 
               Support ASF 2.0.
      Change:
               Add ASF 2.0 support in ASF related functions.
      Impact:
               All ASF related APIs.

Version 6.1.0 (Sep. 28, 2003 )
---------------------------------

   Fixes:
   ======
   1. Request: (CQ 8449)
               BMAPI fails to compile diag with redhat 9.
      Cause:
               Gcc link to wrong default C library when link with C++
               based obj.
      Change:
               Change Makefile to force to link with 'stdc++'.
      Impact:
               All applications but low risk.

   Enhancements:
   =============
   1. Request: 
               Three new APIs, BmapiGetBRCMNicInfoEx(),
               BmapiReadNicMem() and BmapiWriteNicMem() were added.
      Change:
               
      Impact:
               none

Version 6.0.2 (July 28, 2003 )
---------------------------------

   Enhancements:
   =============
   1. Request: (CQ 7965)
               Add external loopback capability to BMAPI.
      Change:
               BmapiTestLoopBackEx() will accepts
               BMAPI_LOOPBACK_TYPE_EXTERNAL as parameter to
               perform external loopback test.
      Impact:
               All chips except 4401 based NIC. For 570x based NICs,
               driver version 6.2.19 or later is REQUIRED.
               For detail information, please refer to BMAPI
               document.

Logs
--------
v6.0.1
- Fix CQ7112: BmapiResumeDriverEx() failed to resume driver after
  BmapiSuspendDriverEx() is called.
  Description: If an interface does not have cable connected and
  manually brought up (ifconfig ethX up), the intefrcae will be
  brought down by BMAPI at the end of diagnostics. The cause is that
  BMAPI check both 'UP' and 'RUNNING' flag for the interface.
  Resolution: BMAPI will check status 'UP' only in BmapiInitDiag().
- Starting driver v5.20, driver will deny MII register access and
  cause LED test failed if the interface is a fiber NIC. Bmapi will
  check the media before performing LED test. If the media is fiber,
  BMAPI will not use MII regesters. Note that bmapi can only blink
  LEDs controlled by MAC registers.

v6.0.0
- Bmapilnx will try to bring up the target interface for diagnostics
  in BmapiInitDiag() if the interface is not 'UP'. Bmaplnx will
  restore the interface to its original state in BmapiUnInitDiag().
- Support ASF! table in ACPI 2.0 BIOS.

v3.0.13
- Not to resolve host name when scanning routing table.

v3.0.12
- Handle one interface with multiple IP properly.
- Support rpm upgrade option.

v3.0.11
- Fix man pages installation problem.
- Fix exception when BMAPI is un-initialize and initialize again.
- Support 5700, 5701, 5702, 5703 and 5705 based deviced.

v3.0.10
- Require miniport driver 5.0.12 or later.
- Add following APIs.
  BmapiDoNicIOCTL()
  BmapiSuspendDriverEx()
  BmapiResumeDriverEx()
  BmapiTestControlRegistersEx()
  BmapiTestMIIRegistersEx()
  BmapiTestInternalMemoryEx()
  BmapiTestInterruptEx()
  BmapiTestLoopBackEx()
  BmapiTestCPUEx()
  BmapiTestLEDsEx()
  BmapiTestEEPROMEx()
  BmapiTestASF()
  BmapiRefreshData()

v3.0.9
- Support 'ui_number' field.

v3.0.8
- Support ASF on 5705.

v3.0.7
- Fix ClearQuest:
  5616: BMAPI get system asf table doesnt work.

v3.0.6
- Require driver v4.0.1 or later.
- Support ASF SNMP community name.
ATTENTION: Support 5700, 5701, 5702 and 5703 based adapters ONLY.

v2.2.25
- Require driver v3.0.11 or later.
- Support 'dhcp_enabled' attribute.
- Support 'default_gateway' attribute.
- BmapiSetASFTable() will generate chip reset to make changes take
  effect immediately.

v2.2.24
- Fix ClearQuest:
  5043: ASF status (in BM_ASF_CFG struc) is mismatched when compared
  between DOS diag and bmapilnx.
- Release version for 'man page' remains the same.

v2.2.23
- Add man pages for APIs support on Linux platform.

v2.2.22
- First release for Linux. Support Redhat Linux 7.3 on i386
  architecture.
- Require Broadcom miniport driver for Linux (module name bcm5700)
  version 3.0.6 or later.
