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

        Marvell Network Controller Windows Firmware Upgrade Tool
                Copyright (c) 2005-2020 Marvell Semiconductor Inc.
                            All rights reserved.

Version 2.10.86 (May 12, 2020)
----------------------------
   Fixes:
   =====
1. Problem: (Cont00108922)
            MBI Upgrade failed if META image is corrupted

   Cause  : META parsing logic fails if META is corrupted
   
   Change : Use MBI META instead of NVM META for parsing
   
   Impact : upgrade cmd, update_cfg cmd

Version 2.10.85 (Apr 20, 2020)
----------------------------
   Fixes:
   =====
1. Problem: (Cont00108800)
			Block diagnostic test on storage interfaces on Windows

   Cause  : diag tests are only supported on NIC interfaces
   
   Change : block diag test to run on storeage interface
   
   Impact : diag cmd
   
Version 2.10.84 (March 30, 2020)
----------------------------
   Fixes:
   =====
1. Problem: Gracefully handle Firmware lockdown mode for oem specific adapters

   Cause  : new request
   
   Change : as requested
   
   Impact : upgrade cmd

Version 2.10.83 (March 5, 2020)
----------------------------
   Fixes:
   =====
Sync'ed with Linux FwUpg tool version

Version 2.10.82 (Dec 20, 2019)
----------------------------
   Fixes:
   =====
1. Problem: (Cont00107901) 
			MBI update failed with error message "NIC not supported" when upgrading through upgrade script

   Cause  : Tool not able to validate MBI against adapter present
   
   Change : Updated logic to validate MBI against adapter
   
   Impact : upgrade cmd

Version 2.10.81 (Dec 6, 2019)
----------------------------
   Fixes:
   =====
Sync'ed with Linux FwUpg tool version

Version 2.10.80 (Nov 26, 2019)
----------------------------
   Fixes:
   =====
1. Problem: FwUpg upgrade fails if path to MBI contains spaces

   Cause  :  spaces in folder name not handled correctly 
   
   Change :  wrap the complete path in quotes
   
   Impact :  upgrade, dumpnvram and restorenvram cmds

2. Problem: Add support for new PHY type

   Cause  :  new request 
   
   Change :  as requested
   
   Impact :  upgrade cmd

Version 2.10.79 (Nov 8, 2019)
----------------------------
   Fixes:
   =====
Sync with ESXi FwUpg tool version

Version 2.10.78 (Oct 10, 2019)
----------------------------
   Fixes:
   =====
1. Problem: (Cont00107381)
            Add user option to change VF BAR2 size

   Cause  :  New Request 
   
   Change :  As requested
   
   Impact :  cfg cmd

Version 2.10.77 (Sept 27, 2019)
----------------------------
   Fixes:
   =====
1. Problem: Fix a memory leak

   Cause  :  New Request 
   
   Change :  As requested
   
   Impact :  upgrade cmd

2. Problem: Add support for developers logs

   Cause  :  New Request 
   
   Change :  As requested
   
   Impact :  FwUpg tool

Version 2.10.76 (Sept 20, 2019)
----------------------------
   Fixes:
   =====
1. Problem: Cosmetic changes, no changes in functionality

   Cause  :  New Request 
   
   Change :  As requested
   
   Impact :  upgrade cmd

Version 2.10.75 (Aug 26, 2019)
----------------------------
   Fixes:
   =====
1. Problem: Add support for bitmask extension for MBI

   Cause  :  New Request 
   
   Change :  As requested
   
   Impact :  upgrade cmd

2. Problem: (Cont00106862) 
            Extra "v" is displayed for EFI version when trying to extract firmware versions from MBI file.

   Cause  :  Typo error 
   
   Change :  Removed extra "v" 
   
   Impact :  xml cmd

Version 2.10.74 (Jun 19, 2019)
----------------------------

     Updated binaries with new digital signature requirements.

Version 2.10.73 (Jun 07, 2019)
----------------------------
   Fixes:
   =====
1. Problem:  Add new cfg option to modify Bar2 size for E4 adapters

   Cause  :  New request 
   
   Change :  as requested 
   
   Impact :  cfg cmd
   
Version 2.10.72 (Apr 02, 2019)
----------------------------
   Fixes:
   =====
1. Problem:  Before MBI upgrade check for CRC errors and print warning message if found

   Cause  :  New request 
   
   Change :  as requested 
   
   Impact :  upgrade cmd
   
Version 2.10.71 (Mar 22, 2019)
----------------------------
   Fixes:
   =====
Sync with Linux FwUpg tool version

Version 2.10.70 (Feb 01, 2019)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ104940) 
             Wrong Exit code returned by tool in case of CRC mismatch found after MBI upgrade

   Cause  :  Exit code got overwritten during executing quit cmd 
   
   Change :  fixed the exit code by returning error code of CRC mismatch  
   
   Impact :  upgrade cmd

2. Problem:  (CQ104895) 
             Fwupg tool should mention that with inbox only FW update is supported and other NVRAM operations like dir/crc would fail. 

   Cause  :  improve on error code description
   
   Change :  as requested
   
   Impact :  upgrade cmd

Version 2.10.69 (Dec 18, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ104699) 
             AH Adapter disappear in HII after downgrade MBI in Secure boot mode 

   Cause  :  UEFI FW size is not getting updated in NVM_CFG 
   
   Change :  Code changed to updates UEFI FW size in NVM_CFG
   
   Impact :  upgrade cmd

Version 2.10.68 (Dec 13, 2018)
----------------------------
   Fixes:
   =====
Sync with Linux FwUpg tool version

Version 2.10.67 (Dec 04, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ104090) 
             On E4 adapter FwUpg Tool does not update UEFI version in NVM_CFG 
			 if MBA image is upgraded

   Cause  :  Tool only updates UEFI version in NVM_CFG only in case of MBI upgrade
   
   Change :  Code changed to updates UEFI version in NVM_CFG in case of 
			 both MBA and MBI upgrade
   
   Impact :  upgrade cmd

2. Problem:  (CQ104588 & CQ104595)
             Error seen while upgrading MBI on AH adapters

   Cause  :  buffer overflow while parsing META image
   
   Change :  increased buffer size
   
   Impact :  upgrade cmd

Version 2.10.66 (Nov 14, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ102809) 
             Some OEM specific adapter stops working on configuring storage from Hii
             after reboot

   Cause  :  Hii writes to wrong NVM offset to clear logged in iscsi target
   
   Change :  On MBI upgrade fix the CRC errors
   
   Impact :  upgrade cmd

Version 2.10.65 (Oct 24, 2018)
----------------------------
 Fixes:
   =====
1. Problem:  (CQ104102) 
			 Request to add MBI checksum verification before MBI upgrade
			 
   Cause  :  checksum validation was not implemented for MBI image
   
   Change :  implemented checksum validation for MBI image
   
   Impact :  upgrade cmd

Version 2.10.64 (Oct 08, 2018)
----------------------------
 Fixes:
   =====
1. Problem:  Add support for new options in "nw_port_mode" 
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  cfg cmd

Version 2.10.63 (Sept 27, 2018)
----------------------------
 Fixes:
   =====
Synced version with Linux FwUpg tool release

Version 2.10.62 (Sept 24, 2018)
----------------------------
 Fixes:
   =====
Synced version with Linux FwUpg tool release

Version 2.10.61 (Sept 20, 2018)
----------------------------
 Fixes:
   =====
1. Problem:
        Problem parsing the VPD buffer.
   Cause:
        Comparison between signed and unsigned integer 
		fails for negative values.
   Changes:
        Fixed parsing the VPD properly on 579XX adapters.
   Impact:
        FwUpg tool

Version 2.10.60 (Sept 12, 2018)
----------------------------
   Fixes:
   =====
1. Problem: MBI upgrade failed on specific OEM adapter

   Cause  : comparison between signed and unsigned integer 
            fails for negative values 
   
   Change :  changed data type to signed integer
   
   Impact :  upgrade cmd
   
2. Problem: (CQ103340)
			 After CRC mismatch fwupg Library not restoring with the dump while upgrading MBI for specific OEM E3 Adapter.
   
   Cause: 	The Restore operation is not getting called due to error mismatch after CRC check.
   
   Changes: Corrected error code validation in-case of CRC mismatch found.
	
   Impact :  upgrade cmd
   
Version 2.10.59 (Aug 20, 2018)
----------------------------
   Fixes:
   =====
Synced version with Linux FwUpg tool release
                                
Version 2.10.58 (Aug 09, 2018)
----------------------------
   Fixes:
   =====
Synced version with Linux FwUpg tool release

Version 2.10.57 (Aug 06, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Enable PLDM after MBI upgrade even if META image is not present for OEM specific adapter

   Cause  :  PLDM cant be enabled if META image not  present
   
   Change :  added code so that PLDM can be enabled enve if META image is not present
   
   Impact :  nvm cfg cmd

2. Problem:  LLDP MAC becomes 0 after factory_defaults

   Cause  :  LLDP MAC address not preserved during factory_defaults
   
   Change :  added code to preserve LLDP MAC address during factory_defaults
   
   Impact :  factory_defaults cmd

Version 2.10.56 (July 27, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ101036)
             Device storage configuration values are persistent after factory_defaults

   Cause  :  Default settings were only applied on NVM CFG and not on storage settings 
   
   Change :  Default settings are also applied on storage settings
   
   Impact :  factory_defaults cmd

Version 2.10.55 (July 11, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Enable PLDM after MBI upgrade for OEM specific adapter

   Cause  :  new request
   
   Change :  as requested
   
   Impact :  upgrade cmd

2. Problem:  Install driver via batch script if driver payload is detected

   Cause  :  new request
   
   Change :  as requested
   
   Impact :  WinQLgcUpg batch file

Version 2.10.54 (June 22, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ101782)
			 Display MFW firmware version and asterisk '*' in front of 
			 device which is currently selected.
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  dev cmd

Version 2.10.53 (June 18, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Provide cfg option to update LLDP MAC address
			 
   Cause  :  new request
   
   Change :  new cmd option "cfg -lldpmac <mac_address>" is implemented
   
   Impact :  cfg cmd

Version 2.10.52 (June 08, 2018)
----------------------------
   Fixes:
   =====
Synced version with Linux FwUpg tool release
                                
Version 2.10.51 (May 14, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ101674)
			 Intermittent Diag test failure on specific OEM adapter
			 
   Cause  :  SuspendDriver routine sometime returns device not started error
   
   Change :  Added retry for SuspendDriver routine
   
   Impact :  diag test

Version 2.10.50 (May 14, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Seeing "grc attn timeout" messages while launching F/W Upgrade Tool.
			 
   Cause  :  Collision with MFW register access
   
   Change :  Adding work around to avoid MFW issue by updating the reg read sequence.
             first use /dev/mem method.
   
   Impact :  FwUpg tool

Version 2.10.49 (Apr 20, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ100989) 
             Request to update or generate vlan table more smartly 
			 on E3 adapter
			 
   Cause  :  new request
   
   Change :  new command "vlant" is added 
   
   Impact :  vlant cmd

2. Problem:  (CQ101255) 
             Error Messages while launching Firmware Upgrade Tool on SLES15
			 
   Cause  :  "ibv_devinfo" command was not installed on system
   
   Change :  check for the presence of "ibv_devinfo" command before invoking it
   
   Impact :  FwUpg tool

Version 2.10.48 (Mar 08, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ100554) 
             After MBI upgrade enable iWarp on OEM specific adapters
			 
   Cause  :  iWarp was disabled
   
   Change :  enabled iWarp after MBI upgrade
   
   Impact :  upgrade cmd

Version 2.10.47 (Mar 08, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ100228) 
             Cmd "cfg -show" shows incorrect status of wol
			 
   Cause  :  wol setting was read from wrong offset
   
   Change :  made changes to read wol from correct offset
   
   Impact :  cfg -show cmd

Version 2.10.46 (Feb 27, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ99864) 
             Do not enable iWarp after MBI upgrade for OEM specific adapter
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  upgrade cmd

Version 2.10.45 (Feb 15, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Added support for OEM specific adapter
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  fwupg tool

Version 2.10.44 (Jan 29, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Improved error handling and error messages
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  fwupg tool

2. Problem:  (CQ99384)
             "vpd -show" not displaying vpd data in command line mode
			 
   Cause  :  problem in tcl lib call
   
   Change :  fixed the problem
   
   Impact :  vpd -show

3. Problem:  (CQ98529)
             Add a support to retrieve MFW crash dump in OS
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  dumpnvram cmd

Version 2.10.43 (Jan 18, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Enable iWARP for specific OEM adapters
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  Upgrade cmd
   
2. Problem:  (CQ99138)
             re-enable "cfg -show vpdv0" cmd as specific OEM fw upg still 
			 depends on this deprecated cmd 
			 
   Cause  :  "cfg -show vpdv0" was deprecated
   
   Change :  re-enable "cfg -show vpdv0" cmd
   
   Impact :  cfg cmd
   
Version 2.10.42 (Jan 12, 2018)
----------------------------
   Fixes:
   =====
1. Problem:  Change nvm cfg option 140 from consortium to BAM for oem specific
             adapter
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  Upgrade cmd
   
2. Problem:  (CQ98356)
             Enable iWARP capability for all BB based adapter.
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  Upgrade cmd
   
Version 2.10.41 (Dec 21, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Diag help cmd formatting issue
			 
   Cause  :  typo error
   
   Change :  fixed typo error
   
   Impact :  diag cmd
   
Version 2.10.40 (Dec 13, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Link up not coming in specific OEM adapter
			 
   Cause  :  driver speed mask was not set correctly in nvm cfg
   
   Change :  fixed driver spped mask
   
   Impact :  fwupg tool
   
Version 2.10.39 (Dec 08, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Updated latest QLMAPI library
			 
   Cause  :  no changes
   
   Change :  no change
   
   Impact :  fwupg tool
   
Version 2.10.38 (Dec 07, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Updated latest QLMAPI library
			 
   Cause  :  no changes
   
   Change :  no change
   
   Impact :  fwupg tool
   
Version 2.10.37 (Dec 06, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Updated latest QLMAPI library
			 
   Cause  :  no changes
   
   Change :  no change
   
   Impact :  fwupg tool
   
Version 2.10.36 (Nov 03, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Displaying incorrect EFI version in generated xml
			 
   Cause  :  EFI version in E3 is 3 bytes and in E4 its 4 bytes
             printing function doesnt differentiate between E3 and E4
   
   Change :  added the missing check
   
   Impact :  xml cmd
   
Version 2.10.35 (Oct 25, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ97474) 
             'factory_defaults' command not working
			 
   Cause  :  'factory_defaults' used to go through nvm translation
   
   Change :  overwrite NVM_CFG1 with DEFAULT_CFG
   
   Impact :  factory_defaults cmd
   
Version 2.10.34 (Oct 11, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Missing INIT_HW version in generated xml
			 
   Cause  :  reading version INIT_HW was missed
   
   Change :  added logic for reading version of INIT_HW version
   
   Impact :  xml cmd
   
Version 2.10.33 (Oct 06, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Extend support for cmd line option "-all" to "dir" and "crc" cmds
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  dir cmd, crc cmd

2. Problem:  Add new cmd to export firmware versions either from NVM or MBI file
			 to a xml file
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  xml cmd

Version 2.10.32 (Sept 21, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ96380)
             Add nvm cfg option "nw_port_mode" 
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  cfg cmd

2. Problem:  Add nvm cfg option "pcie_relaxed_ordering"
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  cfg cmd

3. Problem:  Add new cmd "vpd -show" to display VPD information
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  vpd cmd

4. Problem:  UEFI not loading at POST for specific OEM adapter
			 
   Cause  :  Header of MBA image had incorrect device ID
   
   Change :  Update of MBA header with device ID read from chip
   
   Impact :  upgrade cmd

5. Problem:  Extend WoL cmd "-w" for E4
			 
   Cause  :  New request
   
   Change :  As requested
   
   Impact :  -w cmd

Version 2.10.31 (Sept 13, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ94875)
             Enable DCi support after fw upgrade on some OEM specific adapters
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  upgrade cmd

2. Problem:  Enable iWarp capability in NVM CFG for some OEM specific E4 adapter
             after MBI upgrade
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  upgrade cmd

Version 2.10.30 (Sept 01, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Enable iWarp capability in NVM CFG for some OEM specific adapters
             after MBI upgrade
			 
   Cause  :  New Request
   
   Change :  As requested
   
   Impact :  upgrade cmd

2. Problem:  (CQ96189) 
             Fail to upgrade individual MBA image
			 
   Cause  :  MBA upgrade was success but efi version was not getting 
             updated in NVM CFG
   
   Change :  properly upgrading efi version in NVM CFG
   
   Impact :  upgrade cmd

3. Problem:  Add PLDM image support for some OEM specific adapters
			 
   Cause  :  New request
   
   Change :  as requested
   
   Impact :  upgrade cmd

Version 2.10.29 (Aug 15, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ95557) 
             MBI Version shows 00.00.00 in Firmware image properties after updating to 
			 latest MBI
			 
   Cause  :  MBI upgrade failed due to missing DEFAULT_CFG 
   
   Change :  Treat nvm cfg from MBI as DEFAULT_CFG
   
   Impact :  upgrade cmd, update cmd

2. Problem:  Added new exit codes and Windows Nano and Windows 2016 
             as supported OS in Readme.txt
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  Readme.txt

Version 2.10.28 (Aug 04, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  During MBI upgrade, update MBI version in NVM CFG before 
             upgrading NVM CFG image
			 
   Cause  :  upgrading NVM CFG may fail if NVM does not contain either
             DEFAULT_CFG or META and as result MBI version was not written
			 to NVM CFG
   
   Change :  write MBI version to NVM before attempting NVM_CFG upgrade
   
   Impact :  upgrade cmd

Version 2.10.27 (Aug 01, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ94997)
             Specific OEM adapter does not show up in HII after flashing with FWupg tool
			 
   Cause  :  Expansion ROM size was updated after MBI upgrade
   
   Change :  Properly updated Expansion ROM size after MBI upgrade
   
   Impact :  upgrade cmd

2. Problem:  (CQ95584)
             Boot mode is changed to PXE from iSCSI/FCOE after MBI update
			 
   Cause  :  Boot mode option got overwritten after MBI upgrade
   
   Change :  Boot mode option is preserved (if changed from default value) 
             after MBI upgrade
   
   Impact :  upgrade cmd

Version 2.10.26 (July 26, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  One of two physical adapters failed to initialize drivers for 
             specific OEM adapter			 
			 
   Cause  :  nvm cfg option THERMAL_EVENT_GPIO was set to incorrect value
             after upgrade for this particular adapter
   
   Change :  nvm cfg option THERMAL_EVENT_GPIO is now set to corect value
             after upgrade for this particular adapter
   
   Impact :  upgrade cmd

Version 2.10.25 (July 17, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  One of two physical adapters failed to initialize drivers for 
             specific OEM adapter			 
			 
   Cause  :  nvm cfg option THERMAL_EVENT_GPIO was set to incorrect value
             after upgrade for this particular adapter
   
   Change :  nvm cfg option THERMAL_EVENT_GPIO is now set to corect value
             after upgrade for this particular adapter
   
   Impact :  upgrade cmd

Version 2.10.24 (July 03, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Add support to display "Serial number"
			 dor both E3 and E4
			 
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  cfg cmd

Version 2.10.23 (June 23, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Enable nvm cfg option to set MBA boot protocol.

   Cause  :  option was disbaled for E4
   
   Change :  enabled the cfg option
   
   Impact :  cfg cmd

Version 2.10.22 (June 21, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ94737)
             Range mismatch in "RoCE Priority mode" where FwUpg 
             allows between 0 or 1 and HII allows between 0 to 7.

   Cause  :  Fwupg tool and Hii not in sync
   
   Change :  Fwupg tool implements range as per Hii 
   
   Impact :  cfg cmd

Version 2.10.21 (June 14, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ94394)
             After Firmware upgrade unable to access/configure adapter in HII 
			 HII displays the following error message "Question value does not match the otion value"
			 Issue is specific to a specific OEM adaper

   Cause  :  Problem in identifying adapter capability 
   
   Change :  Fixed the problem
   
   Impact :  upgrade cmd

Version 2.10.20 (June 06, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Added support for specific OEM adatpers

   Cause  :  New request
   
   Change :  As requested
   
   Impact :  fwupg tool

Version 2.10.19 (May 15, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Update META fw from MBI if its not present in NVM
             from OEM specific adapter

   Cause  :  New request
   
   Change :  As requested
   
   Impact :  upgrade cmd
   
Version 2.10.18 (May 08, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ93394) 
             NPAR functions MAC got corrupted after flashing MBI
   
   Cause  :  Problem in calculating NVM offsets of NPAR fields
   
   Change :  Use QLMAPI API for initializing NPAR block
   
   Impact :  upgrade cmd

2. Problem:  (CQ93242) 
             Help are showing some unsupported command and its info.
   
   Cause  :  Help cmd implemented generically
   
   Change :  Help cmd to differentiate between E3 and E4
   
   Impact :  help cmd
   
Version 2.10.17 (Apr 12, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ93072)
             Factory_defaults command fails on Bigbear adapter
   
   Cause  :  Bigbear doesn't have META image which was required for 
             Factory_defaults to work
   
   Change :  META image is made optional for Factory_defaults cmd
   
   Impact :  factory_defaults cmd

2. Problem:  (CQ93110)
             Using 32bit binary on 64bit Windows results in segmentation fault
			 during firmware upgrade
  
   Cause  :  "_alloca" fails to allocate large chunk of memory
                
   Change :  use malloc instead of _alloca
   
   Impact :  upgrade cmd

Version 2.10.16 (Apr 10, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ93092)
             Observed redbox error when trying to access the NIC's UEFI HII settings
			 for specific OEM adapter
   
   Cause  :  cfg option #73 incorrectly set to SF instead of MF_Allowed
   
   Change :  set cfg option #73 to MF_Allowed after firmware upgrade
   
   Impact :  upgrade cmd

Version 2.10.15 (Apr 05, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  On updating firmware and moving NIC to diff slot, FW version changes
   
   Cause  :  Moving to different slot will trigger factory_defaults
             and default_cfg contains old mbi version 
   
   Change :  during update update the mbi_version in default_cfg as well
   
   Impact :  upgrade cmd

Version 2.10.14 (March 30, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Enable DCi support for oem specific adapter
   
   Cause  :  new request 
   
   Change :  as requested
   
   Impact :  upgrade cmd

Version 2.10.13 (March 29, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Some options like MAC address gets zeroed on executing  
             factory_defaults immediatly after MBI upgrade
   
   Cause  :  options like MAC address are not preserved in DEFAULT_CFG 
   
   Change :  preserve the options with NVM_CFG1 values
   
   Impact :  upgrade cmd, factory_defaults

Version 2.10.12 (March 21, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Option 206 gets cleared after MBI upgrade
   
   Cause  :  While updating mbi version in nvm bits reserved for 
             option 206 get zeroed out
   
   Change :  fixed the issue
   
   Impact :  upgrade cmd

Version 2.10.11 (March 20, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ92426)
             Incorrect year in mbi date
   
   Cause  :  Byte Swapping issue
   
   Change :  Fixed Byte Swapping issue
   
   Impact :  upgrade cmd, dir cmd

2. Problem:  (CQ92635)
             Some OEM specific adapter shows CRC Mismatch after flashing 
			 with MFG Kit.
   
   Cause  :  CRC mismatch due to CRASH_DUMP
   
   Change :  CRC on CRASH_DUMP must be skipped
   
   Impact :  crc cmd

Version 2.10.10 (Feb 17, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Fixed some internal CQ, no functionality change
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  cfg cmd

Version 2.10.9 (Feb 10, 2017)
----------------------------
   Fixes:
   =====
1. Problem: (CQ91613) 
            Upgrade MFW before PK, if PK is being programmed for 
			the first time
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd

Version 2.10.8 (Feb 08, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  Extract META from MBI (if available) 
             or extract it from MFW
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd, update_cfg cmd

Version 2.10.7 (Feb 06, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ91204)
             Need ability to set nvm cfg option for EEE Power mode
			 on E3 & E4
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  cfg cmd

2. Problem:  (CQ91495)
             Segmentation fault while upgrading MBI with Public key 
			 on LINUX 
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd
   
3. Problem:  (CQ91338)
             Block downgrade for some specific OEM adapters for a 
			 perticular program
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd

4. Problem:  (CQ91331)
             Add support for setting Forced SF mode for E3 
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  cfg cmd

5. Problem: 
             Add support for setting FEC and SmartlinQ settings for E4 
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  cfg cmd

Version 2.10.6 (Jan 13, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ87522)
             Add support to update Public key for 
			 Secured NVRAM Update
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd

2. Problem:  (CQ88980)
             Add new cmd to upgrade NVM_CFG and DEFAULT_CFG
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  update_cfg cmd

3. Problem:  (CQ90938)
             Set NVM CFG option 202 to 1(RoCE) after upgrade for 
             specific OEM adapters
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd

4. Problem:  (CQ091071)
             Add value validation for NVM CFG options before writing to NVM
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  cfg cmd

Version 2.10.5 (Jan 13, 2017)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ90992)
             VPD block is corrupted after update for specific OEM
   
   Cause  :  calculated wrong number of entries in list
   
   Change :  fixed the problem
   
   Impact :  upgrade cmd

2. Problem:  (CQ90938)
             Set NVM CFG option 202 to 1(RoCE) after upgrade for 
             specific OEM adapters
   
   Cause  :  New feature
   
   Change :  As requested
   
   Impact :  upgrade cmd

Version 2.9.42 (Dec 21, 2016)
----------------------------
   Fixes:
   =====
   
1. Problem:  (CQ88834) 
             Add support to enable / disable dcbx (option 26) and roce_priority_mode 
			 (option 20) cfg options for E4 adapters 
             
   Cause  :  New request
   
   Change :  Added '-dcbx' and '-roce_priority_mode' options
   
   Impact :  cfg cmd

 2. Problem:  (CQ90364) 
             Add new command that display current active SWIM
             
   Cause  :  New request
   
   Change :  As requested
   
   Impact :  info cmd
   

Version 2.9.41 (Dec 14, 2016)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ90584) 
             Need to change cfg option LED_MODE (option 16) from PHY1 to PHY3 
			 for specific OEM
             
   Cause  :  New request
   
   Change :  As requested
   
   Impact :  upgrade cmd
     
Version 2.9.40 (Dec 06, 2016)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ89556) 
             Add temperature capability to the FW Update tool
             
   Cause  :  New request
   
   Change :  As requested
   
   Impact :  info cmd
   
Version 2.9.39 (Nov 10, 2016)
----------------------------
   Fixes:
   =====
1. Problem:  (CQ89070) 
             Add support for additional SWIMs on E3 adapter
             
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  upgrade cmd

Version 2.9.38 (Oct 05, 2016)
----------------------------
   Fixes:
   =====
1. Problem:  Added support for QL41XXX adapters
             
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  phy cmds

2. Problem: (CQ87523)
			 External PHY FW update support (for 10Gbase-T cards)
             
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  phy cmds
 
Version 2.9.37 (Sept 27, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ87523)
			 External PHY FW update support (for 10Gbase-T cards)
             
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  phy cmds
 
Version 2.9.36 (Sept 13, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ88932)
			 Add some cfg options for E4
             
   Cause  :  new request
   
   Change :  as requested
   
   Impact :  cfg cmds

2. Problem: (CQ84759)
          :  Dump and Restore feature for E3 after MBI update in case if CRC or upgrade failures
             
   Cause  :  New request
   
   Change :  As requested
   
   Impact : upgrade and CRC cmds
   
Version 2.9.35 (Aug 31, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ88671)
             For E3 enable option #248 for specific OEM adapters.
             
   Cause  :  new request
   
   Change :  as requested
   
   Impact : upgrade and cfg cmds

Version 2.9.34 (Aug 25, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ88425)
             Restorenvram displays success for E4 instead of feature not supported msg.
             
   Cause  :  error not handled properly
   
   Change :  fixed the error handling
   
   Impact : restorenvram cmd

Version 2.9.33 (Aug 05, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ87675)
             For specific OEM Some Blade return unexpected error after 
			 creating LE with SPP
             
   Cause  :  SWIM_B images got deleted when they are active
   
   Change :  Do not delete the SWIM_B images if they are active
   
   Impact : upgrade cmd

Version 2.9.32 (July 28, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ88263)
             NVM corruption while updating VPD info on specific OEM adapter
             
   Cause  : Adapter not identified as ID was missing in code
   
   Change : Added the ID in code
   
   Impact : upgrade vpd cmd

Version 2.9.31 (July 25, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Fixed Fwupg issue on nano server
             
   Cause  : mismatch in nvm_cfg length of new cfg and 
            what is already present on adapter
   
   Change : Corrected the mismatch
   
   Impact : upgrade cmd
   
Version 2.9.30 (July 06, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ80273) 
            FwUpg Utility shows incorrect mdump version
             
   Cause  : version read from incorrect nvm offset
   
   Change : Corrected offset value
   
   Impact : dir cmd
   
2. Problem: (CQ83402) 
            cfg -mac command does not update MAC of second port on E4
             
   Cause  : problem in identifying correct function offset
   
   Change : Corrected the function number
   
   Impact : cfg -mac cmd 

3. Problem: (CQ87288)
            Do nvm cfg translation if environment variable "DONVM_TRANSLATION is 
			set for specific OEM adapter
                         
   Cause  : New request
   
   Change : As requested
              
   Impact : update cmd

Version 2.9.29 (June 21, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Wrong MAC issue using restore nvm on specific OEM adapter
             
   Cause  : MAC fix was skipped for those adapters
   
   Change : Applied the fix
   
   Impact : restorenvram cmd

Version 2.9.28 (June 14, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ86968)
            Update cfg option 247 for specific OEM adapter
             
   Cause  : New request
   
   Change : As requested
   
   Impact : upgrade cmd

Version 2.9.27 (June 13, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ84888)
            To add option kit support for specific OEM adapter
             
   Cause  : New request
   
   Change : As requested
   
   Impact : cfg cmd

Version 2.9.26 (May 12, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Show vpdv0 info in "cfg -show vpdv0" option
             
   Cause  : New request
   
   Change : As requested
   
   Impact : cfg cmd

Version 2.9.25 (May 10, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ86481) 
            Allow CCM programming if NVRAM doesn't have it already
             
   Cause  : Components not available in NVRAM cant be upgraded
   
   Change : CCM can be now upgraded even if it is not present in NVRAM
   
   Impact : upgrade cmd

2. Problem: (CQ84340) 
            Zero out mbi version if individual components like mfw got updated
             
   Cause  : not implemented previously
   
   Change : as requested
   
   Impact : upgrade cmd

3. Problem: (CQ85179) 
            Display available cfg options based on adapter type
             
   Cause  : cfg option help was implemented generically
   
   Change : available cfg option help will be displayed based on adapter type
   
   Impact : cfg cmd

Version 2.9.24 (Apr 26, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ79334) 
            Add ability to dump MDUMP image
             
   Cause  : new request
   
   Change : as requested
   
   Impact : dumpnvram cmd

2. Problem: (CQ84583) 
            Add ability so that user can change the nvram setting of MDUMP
             
   Cause  : new request
   
   Change : as requested
   
   Impact : cfg cmd
   
Version 2.9.23 (Apr 04, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Update nvm cfg option #27 and #28 for specific OEM adapter
             
   Cause  : new request
   
   Change : as requested
   
   Impact : upgrade cmd
 
Version 2.9.22 (Apr 01, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Accomodate NVM_CFG updates for specific OEM
             
   Cause  : new request
   
   Change : as requested
   
   Impact : upgrade cmd
 
Version 2.9.21 (Mar 31, 2016)
----------------------------
   Fixes:
   =====
1. Problem: fwupg hang on sepcific OEM adapter
             
   Cause  : error in logic to move swim images
   
   Change : fixed the logical error
   
   Impact : upgrade cmd

Version 2.9.20 (Mar 25, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Set option #95 and option #127 for sepcific OEM adapter
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : upgrade cmd

Version 2.9.19 (Mar 18, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Revert AN to fixed speed for specific OEM adapter
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : upgrade cmd

Version 2.9.18 (Mar 15, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ85644)
            Need ability to change option #22 and #85 on specific OEM adapter
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : cfg cmd
   
2. Problem: (CQ85631)
            NIC failure after downgrade to firmware for specific OEM adapter
             
   Cause  : BDN image relocated improperly
   
   Change : fixed the issue
   
   Impact : upgrade cmd

Version 2.9.17 (Mar 14, 2016)
----------------------------
   Fixes:
   =====
1. Problem: Disable LB test in FWupgTOol
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : Diag command on Windows.
   
Version 2.9.16 (Mar 11, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ85357)
            Accomodate NVM_CFG updates for specific OEM
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : upgrade cmd

2. Problem: (CQ85358)
            Accomodate NVM_CFG updates for specific OEM
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : upgrade cmd

Version 2.9.15 (Mar 03, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ85396)
            Accomodate NVM_CFG updates for specific OEM
             
   Cause  : New Request
   
   Change : As requested
   
   Impact : upgrade cmd

2. Problem: (CQ85410)
            Tool shows the mba hide setup mask bit in the cfg -show output
             
   Cause  : Typo error
   
   Change : fixed the error
   
   Impact : cfg cmd

Version 2.9.14 (Feb 26, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ83403) 
             Enable "cfg -show" cmd on E4

   Cause  : New Request
   
   Change : As requested
   
   Impact : cfg cmd

2. Problem: (CQ85284)
            Unable to upgrade PHY on OEM specific adapter
             
   Cause  : Adapter PHY type is new and was not added in code
   
   Change : Added the new PHY
   
   Impact : phy -upg

3. Problem: (CQ85333)
            FWUpg utility 2.9.13 fails to upgrade MBI
             
   Cause  : MBI sub-component version match was treated as error
   
   Change : Check for MBI version and force upgrade the sub-component
   
   Impact : upgrade -upg
   
Version 2.9.13 (Feb 24, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ76689) 
             Failure with NC382i firmware update

   Cause  : Call to init QLmapi fails since 
            windows driver is not up
   
   Change : properly handed the return error code
   
   Impact : reset and upgrade cmd

2. Problem: Cleanup bin files after MBI upgrade
             
   Cause  : Cleanup code not implemented
   
   Change : Implemented the cleanup code
   
   Impact : upgrade cmd
   
3. Problem: (CQ84411) 
             Add support for HW_Init firmware
             
   Cause  : New request
   
   Change : As requested
   
   Impact : upgrade cmd

4. Problem: MBI upgrade fails for MBA having pxe component
             
   Cause  : E4 device-id entry missing in MBA validation
   
   Change : Added the device ID
   
   Impact : upgrade cmd

5. Problem: (CQ85242)
            winfwnx2 diag failure on several components for E4
             
   Cause  : driver need to be suspended for CPU and EEPROM test
   
   Change : implemented the same
   
   Impact : diag cmd

6. Problem: Set option 27 and 28 on all the 25G adapters
             
   Cause  : New request
   
   Change : As requested
   
   Impact : upgrade cmd

7. Problem: Abort upgrading MBI if upgrade fails for any sub-component
             
   Cause  : New request
   
   Change : As requested
   
   Impact : upgrade cmd

Version 2.9.12 (Feb 18, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ79980) 
             iDrac IP lost after upgrading FW

   Cause  : active SWIMs are relocated
   
   Change : aviod relocation of active SWIMs
   
   Impact : upgrade cmd

2. Problem: (CQ82621) 
             Add support to enable SRIOV on E4
			 
   Cause  : New Request
   
   Change : As requested
   
   Impact : cfg cmd

Version 2.9.11 (Feb 15, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ84607) 
             MBA/EFI image gets updated after running fw_dup twice

   Cause  : stale value of efi version was written
   
   Change : new value of efi version was written
   
   Impact : upgrade cmd

2. Problem: (CQ84467) 
             Factory default with Fw upgrade tool change NPAR settings and modify mac address to NULL
			 
   Cause  : incorrect size of NVM_CFG written to NVM
   
   Change : corrected the size calcualtion
   
   Impact : factory_defaults cmd
   
3. Problem: (CQ84968) 
             Display MBI version and Date in "dir" cmd for E4

   Cause  : New request
   
   Change : As requested
   
   Impact : dir cmd

4. Problem: Support "-all" option for factory_defaults cmd for E4

   Cause  : New request
   
   Change : As requested
   
   Impact : factory_defaults cmd

5. Problem: Enable Diag cmd for E4

   Cause  : New request
   
   Change : As requested
   
   Impact : diag cmd

Version 2.9.10 (Feb 10, 2016)
----------------------------
   Fixes:
   =====
1. Problem:  Add support for Diagnostic tests for E4 adapters

   Cause  : New request
   
   Change : As requested
   
   Impact : diag cmd

Version 2.9.10 (Feb 10, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ84831) 
             Enable Full functionality of FwUpg utility for Channel 2015u2 release

   Cause  : New request
   
   Change : As requested
   
   Impact : FwUpg Utility

Version 2.9.9 (Feb 08, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ84643) 
             Set nvm cfg optioin #27 and #28 for supported link modes for specific OEM adapter

   Cause  : New request
   
   Change : As requested
   
   Impact : upgrade cmd

Version 2.9.8 (Feb 04, 2016)
----------------------------
   Fixes:
   =====
1. Problem: 
            Support "-all" option for diag cmd

   Cause  : New request
   
   Change : As requested
   
   Impact : diag cmd

Version 2.9.7 (Jan 21, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ84323) 
             FwUpg reports existing 382i firmware as invalid

   Cause  : Error in merging to E4 branch
   
   Change : Fixed the error
   
   Impact : upgrade cmd

Version 2.9.6 (Jan 19, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ84352) 
             Add restore factory defaults feature for nvm_cfg

   Cause  : Feature request
   
   Change : Added the feature
   
   Impact : factory_defaults
   
2. Problem: (CQ83917)
            5709 device not getting upgraded
            
   Cause  : Check for 5706 Adapter missing
   
   Change : Added the check
   
   Impact : upgrade cmd
   
Version 2.9.5 (Jan 15, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ83525) 
             UEFI driver version is not updating after running DUP

   Cause  : efi_version not updated in NVM
   
   Change : updated the efi_version in NVM
   
   Impact : upgrade cmd
   
Version 2.9.4 (Jan 12, 2016)
----------------------------
   Fixes:
   =====
1. Problem: (CQ83463) 
            Phy Loopback test fails with "Invalid ASF Image" message on Windows

   Cause  : improper check for supported adapters
   
   Change : fixed the check
   
   Impact : diag cmd
								
Version 2.9.3 (Dec 17, 2015)
----------------------------
   Fixes:
   =====
1. Problem: (CQ83974) 
            FW Upg tool shows incorrect "from version" for E4 adapters

   Cause  : problem in bit shifting
   
   Change : fixed the problem
   
   Impact : upgrade cmd

Version 2.9.2 (Dec 16, 2015)
----------------------------
   Fixes:
   =====
1. Problem: (CQ83974) 
            FW Upg tool shows incorrect "from version"

   Cause  : problem in bit shifting
   
   Change : fixed the problem
   
   Impact : upgrade cmd
                               
Version 2.9.1 (Dec 15, 2015)
----------------------------
   Fixes:
   =====
1. Problem: (CQ83900) 
            FW image version is incorrect after FW upgrade

   Cause  : problem in bit shifting
   
   Change : fixed the problem
   
   Impact : upgrade cmd

Version 2.9.0 (Dec 03, 2015)
----------------------------
   Fixes:
   =====
1. Problem: Linux and Windows QLMAPI.h have different #define for E4

   Cause:
         QLMAPI.h Code was not sync'ed on both the platforms
   Change: 
         Sync'ed the code
   Impact:
         All QLogic Mgmt applications.

                               
Version 2.8.6 (Nov 23, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: Add a new command fixmac to fix MAC address corruption.

   Cause  : Added the new option.

   Change : Updated the logic.

   Impact : restorenvram and mfw upgrade commands.
   
   
Version 2.8.5 (Nov 18, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ83336)
            CRC mismatch after fw update on E3 adapters

   Cause  : error in calculating FW Offset

   Change : fixed the error

   Impact : crc cmd

Version 2.8.4 (Sept 28, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ82153)
	    Windows FW upgrade tool not updating family firmware version

   Cause  : VPDV0 was not updated with FFV after MBI upgrade

   Change : VPDV0 is updated with FFV

   Impact : upgrade cmd

Version 2.8.3 (Sept 09, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ81755)
	    Gives same NVRAM version error for all the MBI versions

   Cause  : typo error

   Change : fixed the errror

   Impact : upgrade cmd


Version 2.8.2 (Aug 26, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ81537)
            MBA EFI version displays incorrect version

   Cause  : EFI new version format not implemented

   Change : Implemented parsing for new version format

   Impact : Dir cmd, upgrade cmd
   
   
Version 2.8.1 (Aug 17, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: CQ80721
	    MBA version not displayed during the MBI upgrade

   Cause  : MBA contains only UEFI firmware,
            Parsing UEFI firmware for version not implemented

   Change : Implemented parsing UEFI for version

   Impact : Upgrade cmd


Version 2.7.23 (Aug 14, 2015)
-----------------------------

1. Problem: While restoring MFG kit, NPAR MAC not retored when same version is used.
			
   Cause  : MFG Version check improper

   Change : Updated to check MFG kit version and update NPAR 
            when FORCE option is used.

   Impact : restorenvram cmd



Version 2.7.22 (Aug 04, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: While restoring MFG kit, NPAR block is also updated 
            for OEM specific devices
			
   Cause  : New request

   Change : As Requested

   Impact : restorenvram cmd



Version 2.7.21 (July 31, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: While restoring MFG kit, NPAR block is also updated 
            for OEM specific devices
			
   Cause  : New request

   Change : As Requested

   Impact : restorenvram cmd



Version 2.7.20 (July 30, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ80761)
            Add upgrade support for Monolithic Image for QLE84xx adapters
			
   Cause  : New request

   Change : As Requested

   Impact : upgrade cmd


Version 2.7.19 (July 23, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ80851)
            Enable FCoE and iSCSI personality options on OEM specific adapter
			
   Cause  : New request

   Change : As requested 

   Impact : upgrade cmd

2. Problem: (CQ80821)
             Enable NIC personality to be saved for iSCSI on OEM specific adapter
			
   Cause  : New Request

   Change : As requested 

   Impact : upgrade cmd


Version 2.8.0 (July 07, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: Add support for E4

   Cause  : New request

   Change : As requested

   Impact : upgrade cmd, dir cmd, crc cmd


Version 2.7.18 (June 19, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: Remove Diagnostic Test support for 1Gb cards

   Cause  : New request

   Change : As requested

   Impact : daig cmd


Version 2.7.17 (June 02, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: Display "Manufacture Kit version" and "Manufacture Date"
            in cfg -show option

   Cause  : New request

   Change : As requested

   Impact : cfg Cmd

2. Problem: (CQ79796)
            Winfwnx2 utility crashes while restoring the nvram 
            image on 64-bit

   Cause  : crash in tcl

   Change : upgraded to new version of tcl

   Impact : restorenvram cmd

3. Problem: (CQ79932)
            Upgrade fails for MFW 7.12.55

   Cause  : tool does not recognise newly added 
            mdump firmware

   Change : added support for mdump firmware

   Impact : upgrade cmd


Version 2.7.16 (May 13, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: Add support for Diagnostic tests 

   Cause  : New request

   Change : added new cmd "diag"

   Impact : diag Cmd


Version 2.7.15 (April 28, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: Added support for upgrading Monolithic Image

   Cause  : New feature

   Change : As requested

   Impact : Upgrade Cmd


Version 2.7.14 (March 20, 2015)
-----------------------------
   Fixes:
   ======
1. Problem: (CQ78522)
            WinQlgcUpg:Script gives false message "ibootv712.xx is 
            successfully upgraded" on Killarney board

   Cause  : DOS evnironment variable not set properly

   Change : Moved the code in FwUpg application

   Impact : WinQlgcUpg script


2. Problem: (CQ78498)
            WinQLgcUpg:Failed to upgrade MFW on channel board 

   Cause  : type error in cmd

   Change : fixed the error

   Impact : WinQlgcUpg script

3. Problem: (CQ78494)
	    WinQlgcUpg script:Script should run upgrade command on only 
            one port of each adapter and not all the ports of the adapter

   Cause  : New request

   Change : As requested

   Impact : Upgrade cmd

4. Problem: (CQ78489)
	    Upgrade script:CCM not getting upgraded

   Cause  : ccm cmd missing from script file

   Change : added the cmd

   Impact : WinQlgcUpg script


Version 2.7.12 (March 13, 2015)
-----------------------------

   Fixes:
   ======
1. Problem: (CQ78290)
			Display FCODE level and USR BLOCK

   Cause  : New Request

   Change : As requested

   Impact : cmd dir
 
2. Problem: (CQ78094)
			SVID/SSID mismatch error during MFW upgrade

   Cause  : Debug messages are printed

   Change : Removed the debug messages

   Impact : cmd upgrade

Version 2.7.11 (March 09, 2015)
-----------------------------
   Fixes:
   ======

1. Problem: (CQ77531) cfg -vpdv0 7.12a.1.3 fails with "Invalid VPD V0 information"

   Cause  : VPD-V0 format validation need to be relaxed

   Change : Updated VPD-V0 validation to accept new x.x.x.x format

   Impact : VPDV0 configuration  


Version 2.7.9 (Feb 12, 2015)
-----------------------------

   Fixes:
   ======

1. Problem: (CQ77531) cfg -vpdv0 7.12a.1.3 fails with "Invalid VPD V0 information"

   Cause  : VPD-V0 format validation need to be relaxed

   Change : Updated VPD-V0 validation to accept new x.x.x.x format

   Impact : VPDV0 configuration  



Version 2.7.8 (Jan 09, 2015)
-----------------------------
   Fixes:
   ======

1. Problem: (CQ77254) 
            Set NVM cfg option #239 to enabled automatically during MFW upgrade for specific OEM device
   Cause  : 
            New request
   Change : 
            As requested
   Impact : 
            FW upgrade command


Version 2.7.7 (Dec 16, 2014)
-----------------------------

   Fixes:
   ======

1. Problem: (CQ77213) Remove CRC Check

   Cause : Defered

   Change : As requested

   Impact : FW upgrade, prg, dumpnvram, restorenvram commands


Version 2.7.6 (Dec 02, 2014)
-----------------------------

   Fixes:
   ======

1. Problem: (CQ76947) Add CRC Check

   Cause  : CRC was unavailable in FW Images

   Change : Check for CRC bytes and signature and reject 
            FW images without CRC/signature if force option is not used

   Impact : FW upgrade,prg,dumpnvram,restorenvram commands


Version 2.7.5 (Nov 24, 2014)
------------------------------
   Fixes:
   ======

1. No Change.

Version 2.7.4 (Nov 21, 2014)
------------------------------
   Fixes:
   ======

1. Added list of acceptable device Ids for MBA validation.


Version 2.7.3 (Oct 21, 2014)
------------------------------
Rebranding/split application release.


Version 2.7.2 (Sept 11, 2014)
------------------------------
This application is rebranded to QLogic 


Version 2.6.21 (August 21, 2014)
------------------------------
   Fixes:
   =====
1. Problem: (CQ 73622) 
	  FWUPG VMware: incorrect string name for HP 10G bLOM.
   Cause:
	  Original issue was found to be missing entry for this adapter in the brcm_pci.ids 
	  file.New issue was incorrect line ending characters found in the brcm_pci.ids file.
  	
   Change:
	  Removed all of the offending line ending characters in brcm_pci.ids file.
   Impact:
          firmware upgrade utility for NX2 Adapters.

2. Problem: (CQ 74590) 
	  Readme file needs to be updated.
   Cause:
	  Information update in Reademe file for end user.
  	
   Change:
	  Updated Readme files in Linux, Windows, and VMware with information regarding 
	  “restorenvram”,“upgrade”, and “cfg” commands.  Also, updated BMAPI version requirements.

   Impact:
          firmware upgrade utility for NX2 Adapters.

3. Problem: (CQ 74329) 
	  Utility to recover YB Strings that were zeroed by firmware upgrage tools due to CQ74297.
   Cause:
	  Latest issue was the failure of the “cfg –vpdyb” command from the DOS command line.  
	  When the “cfg –vpdyb” command is issued from the DOS command line, the firmware upgrade tool 
	  would give an incorrect parameter error.  Issue was found to be the parsing of the parameters 
	  on the DOS command line.  The parameter string of binary data on the DOS command line would be 
	  parsed into separate parameter strings (each of which represented one byte of data) and then 
	  passed into the software.  Since the command was expecting only a single string of data, the 
	  software would issue an incorrect parameter error
  	
   Change:
	  The fix was made to recombine the data back into a single string of data before passing 
	  the data along to be processed.

   Impact:
          firmware upgrade utility for NX2 Adapters.


Version 2.6.20 (July 28, 2014)
------------------------------
   Fixes:
   =====
1. Problem: (CQ74329) 
	  “cfg –show vpdyb” command and “cfg –vpdv0 <version string>” command cause segmentation 
	   fault on Linux x86_64.
   Cause:
	  The segmentation fault was caused by the incorrect use of Tcl_AppendResult().  
	  When the data could not be parsed correctly, the error message being put in 
          Tcl_AppendResult() was in the wrong format which caused the segmentation fault.
  	
   Change:
	  The parsing of the data was also an issue in that the bytes in the data buffer was 
	  in the incorrect order.  Determination of whether to swap the bytes of the buffer 
	  was incorrect and caused the data to be parsed incorrectly.  The byte swapping at 
          this point in the software is now done correctly.

   Impact:
          firmware upgrade utility for NX2 Adapters. 

2. Problem: (CQ73622) 
	  Incorrect string name for 57840b1 10 Breezy.
   Cause:
	  Missing entry in the brcm_pci.ids file for this adapter.
  	
   Change:
	  Added entry with correct string name into the brcm_pci.ids file.

   Impact:
          firmware upgrade utility for NX2 Adapters.



Version 2.6.19 (July 23, 2014)
------------------------------
   Fixes:
   =====
1. Problem: (CQ74398) 
	  Customer/Factory required to run "nvm crc" to pass NIC self-test.
   Cause:
	  CRC fails because of upgrade key missing	
   Change:
	  recalculate CRC and update nvram
   Impact:
          crc command


Version 2.6.18 (July 23, 2014)
------------------------------
   Fixes:
   =====
1. Problem: (CQ74726) 
	  lnxfwupg:maximum length of the YB string abnormal over 128 bytes.
   Cause:
	Issue involves the size limit on the YB string in a data structure and 
	the parsing not taking the size into account.
   
   Change:
	Added code to stop parsing the data after the 128 byte limit has been reached.
   
   Impact:
        firmware upgrade utility for NX2 Adapters.


2. Problem: (CQ74589) 
	  CCM upgrade needs -F switch even if higher version is flashed.
   Cause:
	Issue involves version string in CCM image file that does not have space for null terminator.  
        Since the string is 7.10.31 (7 characters, previous versions only had 6 characters or less), 
        there is no space for the null terminator in the file, so the firmware upgrade tool rejects 
        the version number because when it reads the version from the file, garbage characters are 
        added to the end.  

   Change:
	The fix is to read the version number until a non-printable character is encountered and assume 
        that non-printable character indicates the end of the version string.
   
   Impact:
        firmware upgrade utility for NX2 Adapters.


Version 2.6.17 (June 30, 2014)
----------------------------

   Fixes:
   =====
1. Problem: 
	 Enhancement: Set YB binary data into NVRAM for NX2 1G adapters.
   Cause:

   Change:
	Code was added to Set YB binary data into NVRAM for NX2 1G adapters.

   Impact:
        firmware upgrade utility for NX2 1G Adapters.


Version 2.6.16 (June 23, 2014)
----------------------------

   Fixes:
   =====
1. Problem: (CQ 72995)
          lnxfwnx2 must allow preservation of VPD and License NVRAM images.
   Cause:
        The main issue was improper processing of the NVRAM data on a
        BIG_ENDIAN system.

   Change:
        The key to the fix is to note that NVRAM should be handled
        as LE data in the application and anytime you access data that is larger than
        a byte from NVRAM data buffer should be byte swapped for BIG_ENDIAN system.

   Impact:
        firmware upgrade utility for NX2 cards.



Version 2.6.15 (June 14, 2014)
----------------------------


   Fixes:
   =====
1. Problem: (CQ74297)
         Contents of VPD is not preserved property when VPDV0 is updated.
   Cause:
         Some VPD information is binary only and needs to be 
		 preserved that as binary. That was not happening.
   Change:
         Preserve the VPD binary block as is during VPDV0 update.
   Impact:
         Windows firmware upgrade utility for NX2 cards.
		 
		 
Version 2.6.14 (June 10, 2014)
----------------------------


   Fixes:
   =====
1. Problem: Cont00074221
         Clone of 73635: Keep revision ID consistent after MFW upgrade
   Cause:
         MFW sets wrong revision ID.
   Change:
         Add new cfg option -revid_ctl to control revision ID update.
   Impact:
         Windows firmware upgrade utility for NX2 cards.




Version 2.6.13 (May 13, 2014)
----------------------------

   Fixes:
   =====
1. Problem: Cont00073676
         I_B_CFG 3,4 and FEB_CFG3,4 blocks are not updated for OEM board
   Cause:
         wrong sub-device ID of specific board check.
   Change:
         Fixed wrong sub-device ID of specific board check.
   Impact:
         Windows firmware upgrade utility for NX2 cards.



Version 2.6.12 (Mar 24, 2014)
----------------------------

   Fixes:
   =====
1. Problem: cont00000378
         SR-IOV update for 534FLB fails silently
   Cause:
         Implementation for MF mode for PT and VC modules was missing.
   Change: 
         Implemented code for MF mode for PT and VC.
   Impact:
         Windows firmware upgrade utility for NX2 cards.



Version 2.6.11 (Feb 27, 2014)
----------------------------

   Fixes:
   =====
1. Problem: Cont00073138
            FWUP does not display BDN for MFW firmware (T7.10)
      Cause:
                    Code necessary to display BDN was missing
      Change: 
                    Sync with ediag to display BDN
      Impact: 
                    Windows firmware upgrade utility for NX2 cards.


   
2. Problem:  Cont00073143  - Clone of CQ73093: 
            Not able set iscsi personality after enabling NPAR1.5 in CCM
      Cause:
            FEB_CFG3,4 and I_B_CFG3,4 were added based on nvm cfg settings which are now migrated to ccm.
      Change: 
            FEB_CFG3,4 and I_B_CFG3,4 are now always created for specific OEM and specific adapters. 
      Impact: 
           Windows firmware upgrade utility for NX2 cards.


Version 2.6.10 (Feb 04, 2014)
----------------------------

   Fixes:
   =====
   1. Problem: CQ72220
            Lin/WinFwNX2 do not return consistent codes when trying to upgrade without using -F to the same level
      Cause:
	        Wrong return codes were returned.
      Change: 
	        Return 35 if NVRAM has same version as the image file which is to be programmed.
      Impact: 
	        Windows firmware upgrade utility for NX2 cards.						   
							   						   

Version 2.6.9 (Dec 20, 2013)
----------------------------

   Fixes:
   =====
   1. Problem: CQ72032
            Clone of CQ69125: Winfwupg v7.5.1: Winfwupg can work on current user account is not administrator privileges.
      Cause:
	        MANIFEST_RESOURCE_ID definition missing in rc file
      Change: 
	        Included MANIFEST_RESOURCE_ID definition in rc file
      Impact: 
	        Windows firmware upgrade utility for NX2 cards.


Version 2.6.8 (Nov 26, 2013)
----------------------------

   Fixes:
   =====

   1. Problem: CQ71809
            Firmware Upgrade Command Line Interface changed improperly
      Cause:
            Fix for CQ71261 has removed mfw1, restored to keep backward compatibility.It will a synonyms to mfw command. 
      Change:
            Image table is changed so that mfw1,mfw are restored.
      Impact:
            MFW upgrade


   2. Problem: CQ71210
            Enhancement Request - Add OEM specific NPAR support.
      Cause:
            Feature not supported.
      Change:
            Implementation added.
      Impact:
             Windows firmware upgrade utility for NX2 cards.

   3. Problem: CQ71953
             Clone of CQ71448 :lnxfwnx2 must allow preservation of VPD and License NVRAM images.
      Cause:
            Feature not supported.
      Change:
            Implementation added.
      Impact:
             Windows firmware upgrade utility for NX2 cards.


Version 2.6.6 (Oct 4, 2013)
----------------------------

   Fixes:
   =====

   
   1. Enhancement: CQ70182
            Enhance fwupg tool to be more robust for handling upgrade/downgrade nvram components.
      Change:
            Fix the check if there is enough room for new image to not
            exit with failure in case encounters an unknown image type.
      Impact:
            FW upgrade/downgrade.


Version 2.6.4 (Aug 19, 2013)
----------------------------

   Fixes:
   =====
   1. Problem: CQ70625
            PXE FW can not be updated
      Cause:
            CLP check was preventing the upgrade.
      Change:
            CLP check for general MBA programming is not needed.
      Impact:
            PXE/MBA program


   2. Problem: CQ70448
            No information displayed for bastrop (and specific adapters) in discovery.xml
      Cause:
            CCM programming for HP FWUPG Library was not implemented
      Change:
            CCM programming implemented for HP FWUPG Library
      Impact:
            HP FWUPG Library.




Version 2.6.3 (July 05, 2013)
-----------------------------

   Fixes:
   =====
   1. Problem: CQ69464
            Error codes from 118 to 125 missing from Readme.txt
      Cause:
            Documentation issue.
      Change:
            Updated the error codes in Readme.txt
      Impact:
            Readme.txt


Version 2.6.2 (Jun 14, 2013)
-----------------------------
   1. Problem:
            CQ67871 - Burn automatically shadow image needed for
            NC-SI OEM commands upon nvm cfg changes, mfw upgrade or
            nvm prg command.
      Cause:
            The FwUpg tool did not support shadow image.
      Change:
            Add support for new FW image.
      Impact:
            Shadow image.

   2. Problem:
            CQ69375 - lnxfwnx2 failed to update mfw when
            boot_cfg_shadow loaded
      Cause:
            The FwUpg tool did not support shadow image.
      Change:
            Add support for new FW image.
      Impact:
            Shadow image.

   3. Problem:
            CQ69414 - Upgrading ISCSI image in MF_ALLOWED
            configuration, when I_B_CFG3,4 images do not exist,
            creates these images with incorrect IPV6 control flag
            setting.
      Cause:
            The IPV6 control flag does not set properly.
      Change:
            Set the IPV6 control flag for I_B_CFG3,4 correctly.
      Impact:
            I_B_CFG3,4


Version 2.6.1 (May 16, 2013)
------------------------

   Enhancements:
   =============
   1. Request: CQ68937
            Program iSCSI/FCoE boot cfg3 and cfg4 blocks for MF_ALLOWED config.
      Change:
            Program iSCSI/FCoE boot cfg3 and cfg4 blocks for MF_ALLOWED config.
      Impact:
            'upgrade' for NX2 NICs.


Version 2.5.6 (Feb 19, 2013)
----------------------------
   1. Problem: CQ67426
             The "[36m" characters showed up in console after upgrading
             MBA firmware.
      Cause:
             The FwUpg tool could not use these ESC characters to set
             color for the output message.
      Change:
             The FwUpg tool will use a different way to display output
             message in color.
      Impact:
             'upgrade -mba/-mfw1' commands.


Version 2.5.5 (Jan 28, 2013)
----------------------------

   Enhancements:
   =============
   1. Request: CQ65776
            Add 'cfg -vpdv0 <version string>' command to program
            the 'VPD V0 string' into VPD region in NVRAM.
            To display 'VPD V0 string', use 'cfg -show vpdv0' command.
      Change:
            Added 'cfg -vpdv0 <version string>' command to program
            the 'VPD V0 string' into VPD region in NVRAM.
            To display 'VPD V0 string', use 'cfg -show vpdv0' command.
      Impact:
            'cfg' command for NX2 NIC.


Version 2.5.4 (Dec 10, 2012)
-----------------------------
   Enhancements:
   =============
   1. Request: CQ66823
             Add support of new option for 'cfg' command
             for BCM57712 or later NICs.
      Change:
             Added support of new option for 'cfg' command
             for BCM57712 or later NICs.
      Impact:
             All BCM57712 or later NICs.


Version 2.5.3 (Dec 05, 2012)
-----------------------------
   1. Problem: CQ66745
             The 'dev <n>' command returned "Failed to read NVRAM"
             error for some ports.
      Cause:
             The FwUpg tool did not set up device variable correctly.
      Change:
             The FwUpg tool will set up device variable correctly.
      Impact:
             'dev <n>' commands for NX2 10G NICs.

    Note: This bug is injected in v2.5.2 release when implementing
          feature requested in CQ66417.


Version 2.5.2 (Nov 29, 2012)
-----------------------------
   Enhancements:
   =============
   1. Request: CQ66168
            Do not allow the '-sriov' option to work for the 1G
            port of E2 or later NICs.
      Change:
            The 'cfg -sriov' command will return "Feature not supported"
            error for 1G port of E2 or later NICs.
      Impact:
            'cfg -sriov' command for 1G port of E2 or later NICs.

   2. Request: CQ66417
            Sync up the MFW/MBA version in VPD block when upgrading
            the MFW/MBA firmware in NVRAM.
      Change:
            The MFW/MBA version in VPD block will be synced up when
            upgrading the MFW/MBA firmware in NVRAM.
      Impact:
            All NX2 10G NICs.


Version 2.5.1 (Nov 13, 2012)
-----------------------------
   Enhancements:
   =============
   1. Request: CQ66053
            Add -vf_per_pf option in 'cfg' command to set 
            the number of VF per PF
      Change:
            Add -vf_per_pf option in 'cfg' command to set 
            the number of VF per PF
            To display the setting, use 'cfg -show vf_per_pf'
            command.
      Impact:
            'cfg' command for NX2 10G NICs.

   2. Request: CQ65536
            Add 'prg -ccm <file>' and 'upgrade -ccm <file>' commands
            to add/upgrade the CCM firmware.
      Change:
            Add 'prg -ccm <file>' and 'upgrade -ccm <file>' commands
            to add/upgrade the CCM firmware.
      Impact:
            All NX2 NICs.

   3. Request: CQ66069
            Need to delete standalone CCM binary if MBA is programmed
            with built-in CCM.
      Change:
            The FwUpg will delete standalone CCM binary if MBA is
            programmed with built-in CCM.
      Impact:
            All NX2 NICs.


Version 2.5.0 (Oct 17, 2012)
----------------------------
   Enhancements:
   =============
   1. Request:
            Add support for BCM57840 NICs.
      Change:
            Added support for BCM57840 NICs.
      Impact:
            BCM57840 NICs.  The support is for SF mdoe only.

   2. Request: CQ65976
               Add support for upgrading PHY firmware for 84834
               external PHY. 
      Change:
               Added support for upgrading PHY firmware for 84834
               external PHY. 
      Impact:
               Adapter with 84834 external PHY.


Version 2.4.51 (Sep 27, 2012)
-----------------------------
   1. Problem: CQ65781
             The PCI Subsystem Device Id, SSDID, was modified to
             the one from image file for BCM57810 NIC in 'restorenvram'
             command even the 'config' option was not specified.
      Cause:
             The FwUpg tool did not preserve the SSDID correctly due
             to a bug.
      Change:
             The FwUpg will preserve the SSDID correctly in
             'restorenvram' command if 'config' option is not specified.
      Impact:
             'restorenvram' commands for NX2 10G NICs.


Version 2.4.50 (Sep 24, 2012)
-----------------------------
   Enhancements:
   =============
   1. Request: CQ65319
            Add '-sriov' option in 'cfg' command to enable/
            disable the setting of SRIOV.
      Change:
            Added '-sriov' option in 'cfg' command to enable/
            disable the setting of SRIOV.
            To display the setting, use 'cfg -show sriov'
            command.
      Impact:
            'cfg' command for NX2 10G NICs.


Version 2.4.7 (Aug 10, 2012)
----------------------------
   fixes:
   ======
   1. Problem: CQ65013
             The '-all upgrade/restorenvram' commands did not work for
             the BCM57810 NIC with error message 'NIC is not supported'
      Cause:
             There were 5709 and 57810 NICs in the system.  When FwUpg
             tried to validate each device for the '-all' option, it
             used only the first device, the 5709 NIC in this case, to
             qualify the firmware by mistake.
      Change:
             The FwUpg will qualify the firmware on each device
             individually when selecting the devices for '-all' option.
      Impact:
             '-all upgrade/restorenvram' commands for NX2 NICs.


Version 2.4.6 (Jul 06, 2012)
----------------------------
   Enhancements:
   =============
   1. Request: CQ63045
            Add '-sriov_hide_menu' option in 'cfg' command to
            configure the setting of showing SRIOV menu.
      Change:
            Added '-sriov_hide_menu' option in 'cfg' command to
            configure the setting of showing SRIOV menu.
            To display the setting, use 'cfg -show
            sriov_hide_menu' command.
      Impact:
            'cfg' command for NX2 10G NICs.


Version 2.4.5 (Jun 27, 2012)
----------------------------
   Enhancements:
   =============
   1. Request: CQ63409
            Expanded return code information from FwUpg when the
            'upgrade' command was failed.
      Change:
            Expanded return code information from FwUpg when the
            'upgrade' command was failed.
      Impact:
            'upgrade' command for NX2 10G NICs.

   fixes:
   ======
   1. Problem: CQ63668
             The 'restorenvram' command did not work for the
             BCM57811 NIC.
      Cause:
             The FwUpg tool did not validate the media type correctly
             for the BCM57811 NIC.
      Change:
             The FwUpg now validate the media type correctly for
             the BCM57811 NIC.
      Impact:
             'restorenvram' commands for BCM57811 NIC.

   2. Problem: CQ64220/CQ64225
             The FwUpg did not show device that is down with qlmapilnx
             v6.15.3.
      Cause:
             The qlmapilnx v6.15.3 returned QLMAPI_DRIVER_NOT_LOADED in
             QLmapiGetBRCMNicInfoEx API for device that is down.  FwUpg
             tool did not handle the return code and did not add the
             device to the device list.
      Change:
             The FwUpg will check on the return code and add the device
             to the device list.
      Impact:
             Device enumeration for FwUpg tool.


Version 2.4.4 (May 22, 2012)
----------------------------
   Enhancements:
   =============
   1. Request: CQ63252
            The NIV block should not be created in 'restorenvram'
            command under the following conditions:
            1. The image file contains a NIV block,
            2. The NIV block does not exist in the NVRAM originally,
            3. The 'config' option is not specified.
      Change:
            The NIV block will not be created in 'restorenvram'
            command under following conditions:
            1. The image file contains a NIV block,
            2. The NIV block does not exist in the NVRAM originally,
            3. The 'config' option is not specified.

            The FwUpg will create a default NIV block with L2 MAC
            Addresses under the following conditions:
            1. The image file contains a NIV block,
            2. The NIV block does not exist in the NVRAM originally,
            3. The 'config' option is specified.
      Impact:
            'restorenvram' command for NX2 10G NICs.


Version 2.4.3 (May 07, 2012)
----------------------------
   Enhancements:
   =============
   1. Request:
            Add MBA image validation based on device type.
      Change:
            Added MBA image validation based on device type.
      Impact:
            'upgrade -mba' command for NX2 10G NICs.

   fixes:
   ======
   1. Problem: CQ61658
            The NIV block is not preserved in 'restorenvram' command.
      Cause:
            FwUpg did not preserve the NIV block in 'restorenvram'
            command.
      Change:
            FwUpg will preserve the NIV block in 'restorenvram'
            command.
      Impact:
            'restorenvram' commands for NX2 10G NICs.

   2. Problem: CQ62804
            The NIV block is not initialized with correct MAC address
            in 'restorenvram config' command if it is not existing
            in the NVRAM initially.
      Cause:
            The NIV block is not initialized with correct MAC addresses
            in 'restorenvram config' command if it is not existing
            in the NVRAM initially.
      Change:
            FwUpg will initialize the MAC addresses in the NIV block
            correctly in the 'restorenvram config' command.
      Impact:
            'restorenvram' commands for NX2 10G NICs.


Version 2.4.2 (May 02, 2012)
----------------------------
   Enhancements:
   =============
   1. Request:
               Do not suspend driver when upgrading PHY firmware
               with evbd driver v7.2.51 or later.
      Change:
               Do not suspend driver when upgrading PHY firmware
               with evbd driver v7.2.51 or later.
      Impact:
               'phy -upg' command.


Version 2.4.1 (Mar 13, 2012)
----------------------------
   Enhancements:
   =============
   1. Request:
               Add '-noreset' option for 'cfg' command in
               CLI mode.
      Change:
               Added '-noreset' option for 'cfg' command in
               CLI mode.
      Impact:
               'cfg' command in CLI mode.

   fixes:
   ======
   1. Request: CQ61207
             FwUpg crashed in 'dir' command if NPAR is in NVRAM.
      Cause:
             During parsing the data in extended_dir, the FwUpg tool
             tried to copy more data than the buffer allocated.
      Change:
             The FwUpg will make sure the data copied equal to the
             buffer allocated.
      Impact:
             'dir' command for NX2 NICs with extended_dir in NVRAM.


Version 2.3.12 (Feb 20, 2012)
----------------------------
   Enhancements:
   =============
   1. Request: CQ61507
               Add support of new option for 'cfg' command
               for BCM57712 or later NICs.
      Change:
               Added support of new option for 'cfg' command
               for BCM57712 or later NICs.
      Impact:
               All BCM57712 or later NICs.


Version 2.3.11 (Feb 06, 2012)
----------------------------
   Enhancements:
   =============
   1. Request: CQ59233
               Added support of some option for 'cfg' command
               for NX2 1G NICs.
      Change:
               Added support of some option for 'cfg' command
               for NX2 1G NICs.
      Impact:
               All NX2 1G NICs.

   fixes:
   ======
   1. Request: CQ61417
             FwUpg failed to configure MAC address with 'cfg -mac'
             command in CLI mode.
      Cause:
             The FwUpg tool did not validate the parameters of 'cfg'
             command correctly in CLI mode.
             The problem was injected in v2.3.9 release.
      Change:
             The FwUpg will validate the parameters of 'cfg' command
             correctly in CLI mode.
      Impact:
             'cfg' command for NX2 NICs in CLI mode.


Version 2.3.10 (Feb 02, 2012)
----------------------------
   Enhancements:
   =============
   1. Request: CQ59233
               Added support of '-all' option in CLI mode for some
               'cfg' commands.
      Change:
               Added support of '-all' option in CLI mode for some
               'cfg' commands.
      Impact:
               All NX2 NICs.


Version 2.3.9 (Jan 26, 2012)
----------------------------

   Enhancements:
   =============
   1. Request: CQ60110
             Remove I_B_CPRG block from NVRAM when upgrading to 
             iSCSI boot firmware 7.0.x.

      Change:
             Remove I_B_CPRG block from NVRAM when upgrading to 
             iSCSI boot firmware 7.0.x.
      Impact:
             'upgrade -ib' command for NX2 10G NICs.

   fixes:
   ======
   1. Request: CQ59707
             The 'upgrade -F -ib_ipv4n6 -p' command will cause a
             segmentation fault for BCM57710/11/12.
      Cause:
             The FwUpg tool did not handle the -p option correctly.
      Change:
             The FwUpg will handle the -p option correctly.  Actually,
             the '-p' and '-c' options are no longer needed.  All iSCSI
             bootcode, configuration, and config program will be
             programmed/upgraded into NVRAM automatically.
      Impact:
             'upgrade -ib -p' command for NX2 10G NICs.


Version 2.3.8 (Dec 14, 2011)
----------------------------

   fixes:
   ======
   1. Request: CQ60061
             The 'upgrade -mba' command failed to upgrade MBA/CLP
             firmware from v1.1.3 to v1.3.5.
      Cause:
             The MBA/CLP firmware in the NVRAM did not have the
             'Indicator' field within PCIR block set up correctly
             for the last image within the MBA/CLP firmware.
             The FwUpg tool relies on this field when processing
             the version of each image within the MBA/CLP firmware.
      Change:
             The FwUpg will double check on length of each image when
             processing the version of each image within the MBA/CLP
             firmware.
      Impact:
             'upgrade -mba' command for NX2 NICs.

   2. Request: CQ60282
             The output of 'dir' command did not display the firmware
             version correctly for BCM57712 NIC.
      Cause:
             The firmware version is using 3 digits, instead of 2, in
             the build version.  When the version string exceeds 12
             bytes, the last digit is dropped.
      Change:
             The version string can be up to 16 bytes now.
      Impact:
             'dir' command for NX2 10G NICs.


Version 2.3.7 (Oct 26, 2011)
----------------------------

   fixes:
   ======
   1. Request: CQ59405
             The output of 'dir' command was not logged in the log file
             for BCM57810 NIC.
      Cause:
             The output of 'dir' commmand was sent to console only and
             was not sent to the log file.
      Change:
             The output of 'dir' commmand is now sent to both console and
             the log file if log file is opened.
      Impact:
             'log' command for NX2 10G NICs.

   2. Request: CQ59407
             The 'cfg -show' command failed and FwUpg terminated abnormally
             for BCM57810 NIC in IA32 system.
      Cause:
             The FwUpg did not handle the pointer correctly when trying to
             display the VPD information.
      Change:
             The FwUpg will handle the pointer correctly when trying to
             display the VPD information.
      Impact:
             'cfg -show' command for NX2 10G NICs.


Version 2.3.6 (Oct 14, 2011)
----------------------------

   fixes:
   ======
   1. Request:
             The system hang during POST after upgrading MFW to the
             same version without '-F' option.
      Cause:
             Active SWIMs are deleted even if the 'upgrade' command failed
             to upgrade the MFW firmware due to version validation.
             The MFW will halt if it couldn't find the required SWIM image.
      Change:
             Delete the active SWIM modules only after version validation
             is successful.
      Impact:
             'upgrade -mfw1' command for BCM57712 or later NICs.

   2. Request: CQ59265
             The 'upgrade -bc' command failed for BCM5716S NIC.
      Cause:
             The BCM5716S device ID was not handled correctly in processing
             the 'upgrade -bc' command.
      Change:
             The BCM5716S device ID is handled correctly in processing
             the 'upgrade -bc' command.
      Impact:
             'upgrade -bc' command for BCM5716S NIC.  The BCM5716C NIC
             should not have this problem.


Version 2.3.5 (Sep 16, 2011)
----------------------------

   fixes:
   ======
   1. Request:CQ58591
             FCoE and iSCSI boot parameters are overwritten by default 
             when restoring a nvram image
      Cause:
             iSCSI boot parameters on port other than 0 are not preserved;
             FCoE boot parameters on all ports are not preserved
      Change:
             Add support for preserving iSCSI boot parameters for devices
             higher than the first device;
             Add support for preserving FCoE boot parameters
      Impact:
             'restorenvram' command for BCM57712 or later NICs.


Version 2.3.4 (Aug 16, 2011)
----------------------------

   Enhancements:
   =============
   1. Request:
             Added 'cfg -shadow_swim <value> command to enable/
             disable to Shadow SWIM feature support for BCM57712
             or later NICs.  This feature requires the CFG_SHARED
             entry in the Extended Directory.
      Change:
             Added 'cfg -shadow_swim <value> command to enable/
             disable to Shadow SWIM feature support for BCM57712
             or later NICs.  The 'cfg -show' command will display
             the current status of Shadow SWIM support.
      Impact:
             'cfg' command for BCM57712 or later NICs.


Version 2.3.3 (Aug 09, 2011)
----------------------------

   fixes:
   ======
   1. Request:CQ57382
             Entry in Extended Directory might disappear after upgrading
             the MFW firmware.
      Cause:
             The FwUpg tool did not update the Extended Directory correctly
             after programming the MFW firmware.
      Change:
             The FwUpg tool will update the Extended Directory correctly
             after programming the MFW firmware.
      Impact:
             'upgrade -mfw1' command for NX1 10G NICs.

   2. Request:CQ57695
             The 'cfg mgmt|mfw_wol_speed' command does not work for
             BCM57710/57711 NICs.
      Cause:
             The FwUpg tool did not validate the option against the NIC
             type correctly.
      Change:
             The FwUpg tool validates the option against the NIC type
             correctly now.
      Impact:
             'cfg' command for BCM57710/57711/57711E NICs.


Version 2.3.2 (Jul 29, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request:
             Do not allow 32-bit FwUpg to run in 64-bit platform.
      Change:
             The 32-bit FwUpg will check the 64-bit platform and
             exit with an error message.
      Impact:
             The 32-bit FwUpg will not run in the 64-bit platform.


Version 2.3.1 (Jul 25, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request:
             Added support for new SWIM modules.
      Change:
             Added support for new SWIM modules.
      Impact:
             Will support MFW firmware v7.0.24 or later.

   fixes:
   ======
   1. Request:CQ56439
             Failed to upgrade MFW/iSCSI firmware to BCM57810 NIC
             in NPAR mode.
      Cause:
             FwUpg tool did not support BCM57810 NIC in NPAR mode.
      Change:
             Added support for BCM57810 NIC in NPAR mode.
      Impact:
             'upgrade' command for BCM57810/57800/57840 NICs in NPAR
             mode.

   2. Request:CQ56602
             FwUpg did not validate version before upgrading the MFW
             firmware even the '-F' option was not specified in the
             'upgrade' command.
      Cause:
             FwUpg tool did not check the MFW firmware version before
             upgrading it to the NVRAM even the '-F' option was not
             specified in the 'upgrade' command.
      Change:
             FwUpg tool will check the MFW firmware version before
             upgrading it to the NVRAM if '-F' option is not specified
             in the 'upgrade -mfw1' command.
      Impact:
             'upgrade -mfw1' command for NX2 10G NICs.

      Note:
            The BMAPI v7.24.13 or later is required.


Version 2.3.0 (Jun 09, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ52616
             Added support for BCM57800/57810/57840 NICs.
      Change:
             Added support for BCM57800/57810/57840 NICs.
      Impact:
             BCM57800/57810/57840 NICs.

   fixes:
   ======
   1. Request:CQ55849
             Failed to upgrade MFW firmware to BCM57810 NIC.
      Cause:
             FwUpg tool did not support BCM57810 NIC.
      Change:
             Added support for BCM57810 NIC.
      Impact:
             'upgrade -mfw1' command for BCM57810 NIC.


Version 2.2.8 (May 27, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ55719
             Added '-vpd' option in 'upgrade' command to upgrade
             Extended VPD from a file.
      Change:
             Added '-vpd' option in 'upgrade' command to upgrade
             Extended VPD from a file.
      Impact:
             'upgrade -vpd <file>' command for NX2 10G NICs.


Version 2.2.7 (May 13, 2011)
----------------------------

   fixes:
   ======
   1. Request:CQ55460
             FwUpg tool terminated abnormally when running 'cfg -wol <value'
             command on devices under NPAR configuration.
      Cause:
             FwUpg tool did not configure the devices under NPAR
             correctly.
      Change:
             FwUpg tool will configure the devices under NPAR
             correctly.
      Impact:
             'cfg -mgmt/wol/mba' command for NX2-10G NICs under NPAR
             configuration.


Version 2.2.6 (May 06, 2011)
----------------------------

   fixes:
   ======
   1. Request:CQ55193
             FwUpg tool did not work with 'cfg -mgmt <value>' command
             on BCM57712 NIC with MFW firmware.
      Cause:
             FwUpg tool did not treat the MFW firmware as one with
             NCSI management firmware.
      Change:
             FwUpg tool will treat the MFW firmware as one with
             NCSI management firmware.
      Impact:
             'cfg -mgmt' command for NX2-10G NICs with MFW firmware.


Version 2.2.5 (Apr 28, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ55130
             FwUpg tool failed in 'restorenvram' command with
             'FCoE directory entry mismatch' error.
      Cause:
             FwUpg tool did not validate the FCoE entry in the
             Dump file correctly.
      Change:
             FwUpg tool now validates the FCoE entry in the Dump
             file correctly.
      Impact:
             'restorenvram' command for NX2-10G NICs.

      Note:
            The BMAPI v7.24.3 or later is required.


Version 2.2.4 (Apr 20, 2011)
-----------------------------

   fixes:
   ======
   1. Request: CQ54864
             The PCI vendor/device IDs in MBA firmware header were
             written with 0 after upgrading the MBA firmware for
             BCM57712.
      Cause:
             The FwUpg tool did not get the PCI vendor/device IDs
             correctly for the second port and write them to the
             header of MBA firmware during upgrading MBA firmware.
             There's no issue for upgrading the MBA firmware for
             the first port.
      Change:
             FwUpg tool will retrieve the PCI vendor/device IDs
             correctly for the second port.
      Impact:
             'upgrade -mba' command for BCM57712 NIC.


Version 2.2.3 (Apr 13, 2011)
-----------------------------

   fixes:
   ======
   1. Request: CQ54641
             The Shared Memory can't be read correctly after upgrade
             the Bootcode.
      Cause:
             The Shared Memory location was changed, but the Bootcode
             did not update the information.
      Change:
             FwUpg tool will notify the Bootcode to update the Shared
             Memory information.
      Impact:
             'upgrade -bc' command for NX2-10G NICs.


Version 2.2.2 (Apr 07, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ54486
             FwUpg tool failed in 'restorenvram' command with
             'FCoE directory entry mismatch' error.
      Cause:
             FwUpg tool did not validate the FCoE entry in the
             NVRAM correctly.
      Change:
             FwUpg tool now validates the FCoE entry in the NVRAM
             correctly.
      Impact:
             'restorenvram' command for NX1, NX2-1G, and NX2-10G NICs.


Version 2.2.1 (Mar 30, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ54246
             Added '-dcbx' option in 'cfg' command to enable/
             disable the DCBX.
      Change:
             Added '-dcbx' option in 'cfg' command to enable/
             disable the DCBX.
      Impact:
             'cfg -dcbx {1|0}' command for 57712 or later NIC.


Version 2.2.0 (Mar 25, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ54055
             Added option in 'upgrade' command to upgrade FCoE boot firmware.
      Change:
             Added option in 'upgrade' command to upgrade FCoE boot firmware.
      Impact:
             'upgrade -feb [-c] <file>' command for 57712 or later NIC.

   fixes:
   ======
   1. Request:CQ53875
             FwUpg tool failed to program NVRAM in 'restorenvram' command.
      Cause:
             FwUpg tool might encounter error when trying to find room to
             preserve the NIC-Part block.
      Change:
             FwUpg tool fixed an issue in the 'find room' algorithm.
      Impact:
             'restorenvram' command.


Version 2.1.19 (Mar 15, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ53648
             FwUpg tool deleted the NCSI firmware while upgrade/downgrade
             the Bootcode.
      Cause:
             FwUpg tool deleted the NCSI firmware when upgrade/downgrade
             both Bootcode and MFW firmware.
      Change:
             FwUpg tool will only delete the NCSI firmware when upgrade/
             downgrade the MFW firmware.  The NCSI firmware is intact
             when upgrade/downgrade the Bootcode.
      Impact:
             'upgrade -bc' command.


Version 2.1.18 (Mar 04, 2011)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ52477
	         Added the capability to upgrade MFW firmware for
	         BCM57712 NIC.  The FwUpg tool should also be able
	         to downgrade MFW firmware to BC1/BC2 firmware.
      Change:
             Added the requested feature.
      Impact:
             'upgrade -mfw1 <file>' commands for BCM57712 NIC.

   fixes:
   ======
   1. Request:CQ52339
             FwUpg tool can't detect the management firmware in MFW.
      Cause:
             FwUpg tool can't recognize the MFW firmware type.
      Change:
             FwUpg tool can recognize the MFW firmware type.
      Impact:
             'cfg -show' on BCM57712 NIC.


Version 2.1.17 (Feb 25, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ53067
             FwUpg tool might add a block of data into the NVRAM with
             'restorenvram' command.
      Cause:
             FwUpg tool wrote content into NVRAM without checking valid
             condition in 'restorenvram' command.
      Change:
             FwUpg tool will check condition before restoring content into
             NVRAM.
      Impact:
             'restorenvram' on BCM57712 NIC without NIC partitioning block.


Version 2.1.16 (Feb 11, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ52847
             FWUpgrade: unable to upgrade PHY version on 
             second port for BCM57712NIC
      Cause:
             Got wrong ext phy type on 2nd port
      Change:
             Get correct ext phy type on 2nd port
      Impact:
             'phy -upg <extphyimage>' on BCM57712NIC
      Note:
            The BMAPI v7.22.1 or later is required for this CQ.


Version 2.1.15 (Feb 01, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ52654
             restorenvram -all from command line does not execute 
      Cause:
             no default NIC was selected in command line mode
     Change:
             select device 0 by default
      Impact:
             'lnxfwupg -all restorenvram saved_file'


   2. Request:CQ52646
             unable to load/read files outside of the current 
             directory if back slash is used to specify file loc. 
      Cause:
             backslash should not be used
     Change:
             correct readme file
      Impact:
             'dumpnvram/restorenvram saved_file'

   3. Request:CQ52647
             application misreads entry as tab space
      Cause:
             backslash should not be used
     Change:
             correct readme file
      Impact:
             'dumpnvram/restorenvram saved_file'

Version 2.1.14 (Jan 17, 2011)
-----------------------------

   fixes:
   ======
   1. Request:CQ52292
             port2 iscsi boot config was overwritten when using 
             'restorenvram saved_file' command on BCM57712 NIC
      Cause:
             port2 iscsi boot config was not preserved
      Change:
             preserve port2 iscsi boot config for both ports
             for BCM57712 NIC 
      Impact:
             'restorenvram saved_file' for BCM57712 NIC

   2. Request:CQ52283
             Preserve the MAC addresses in NIC-partition block
             if '-mac' option in 'restorenvram' command was not
             specified.
      Cause:
             The MAC addresses in NIC-partition block was not
             preserved correctly.
      Change:
             Preserve the MAC addresses in NIC-partition block if
             '-mac' option is not specified. 
      Impact:
             'restorenvram saved_file' for BCM5771x NICs.


Version 2.1.13 (Dec 09, 2010)
-----------------------------

   fixes:
   ======
   1. Request:
             Failed to restorenvram on BCM57712 on NIC Partition mode
             when idmatch flag is missing  	
      Cause:
             Device ID validation checking is not correct for NIC 
             Partition mode 
      Change:
             Check Device ID Correctly
      Impact:
             'restorenvram idmatch' for BCM57712NIC


Version 2.1.12 (Dec 02, 2010)
-----------------------------

   fixes:
   ======
   1. Request: CQ51149
             Failed to restorenvram on BCM57712 on NIC Partition mode 	
      Cause:
             Device ID validation checking is not correct for NIC 
             Partition mode 
      Change:
             Check Device ID Correctly
      Impact:
             'restorenvram' for BCM57712NIC


Version 2.1.11 (Nov 24, 2010)
-----------------------------

   fixes:
   ======
   1. Request:
             Abnormal termination for 'cfg -show' for BMC57712 NIC 	
      Cause:
             Device index was corrupted 
      Change:
             Get correct device index
      Impact:
             'cfg -show' for BCM57712NIC


Version 2.1.10 (Nov 19, 2010)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ50321
	       BCM5709NIC - display VPD-V0 field from NVRAM 
      Change:
               Added display of VPD-V0 info in 'cfg -show'
      Impact:
               'cfg -show' commands for BCM5709NIC


Version 2.1.9 (Nov 12, 2010)
-----------------------------

   Enhancements:
   =============
   1. Request: CQ50202
	       Enable FWUpg tool to support new VPD directory structure 
      Change:
               Added support of new VPD directory
      Impact:
               'dir && cfg -show' commands

   2. Request: CQ50321
	       display VPD-V0 field from NVRAM 
      Change:
               Added display of VPD-V0 info in 'cfg -show'
      Impact:
               'cfg -show' commands

   3. Request: CQ46779
	       Add requested new feature for 'cfg'command for
               BCM57710/11/12 NICs.
      Change:
               Add the requested feature to 'cfg' command
      Impact:
               'cfg' command for for BCM57710/11/12 NICs



Version 2.1.8 (Sep 24, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ50054
               Add requested new feature for 'cfg' command for
               BCM57710/11/12 NICs.
      Change:
               Added the requested feature for 'cfg' command.
      Impact:
               'cfg' command.


Version 2.1.7 (Sep 10, 2010)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ49830
               FwUpg does not handle the dump file in Atmel format.
      Cause:
               The 'restorenvram' command did not support dump file
               in Atmel format.
      Change:
               Added support for dump file in Atmel format in
               'restorenvram' command.
      Impact:
               'restorenvram' command for NX2 NICs.


Version 2.1.6 (Aug 22, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ49563
               Added option for the 'cfg command for BCM5771x NICs.
      Change:
               Added option for the 'cfg command for BCM5771x NICs.
      Impact:
               'cfg' command for BCM5771x NICs.


Version 2.1.5 (Aug 16, 2010)
---------------------------------

   Fixes:
   =====
   1. Problem:
               The FwUpg tool could not process the option
               correctly in 'restorenvram' command in the
               command line mode.
      Cause:
               The FwUpg tool did not process the option
               correctly in the command line mode.
      Change:
               The FwUpg tool can process the option correctly
               in the command line mode.
      Impact:
               'restorenvram' command for BCM5771x NICs.


Version 2.1.4 (Aug 10, 2010)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ49293
               The FwUpg tool could not identify the 'media type'
               of the BCM5709S LOM correctly.
      Cause:
               The FwUpg tool did not check the media type of
               the BCM5709S LOM correctly.
      Change:
               The FwUpg tool can identify the 'media type'
               correctly for the BCM5709S LOM.
      Impact:
               'dev' command for BCM5709S LOM.


Version 2.1.3 (Aug 06, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ49241
               Added a hidden option for the 'restorenvram' command
               for BCM5771x NICs.
      Change:
               Added a hidden option for the 'restorenvram' command
               for BCM5771x NICs.
      Impact:
               'restorenvram' command for BCM5771x NICs.

   Fixes:
   =====
   1. Problem: CQ48460
               The FwUpg tool could not upgrade the bootcode
               for the BCM5708S LOM.
      Cause:
               The FwUpg tool did not determine the 'media type'
               of the BCM5708S LOM correctly when the LOM was
               connected to a remote COPPER PHY.
      Change:
               The FwUpg tool can identify the 'media type'
               correctly for the BCM5708S LOM and allows the
               the bootcode to be upgraded.
      Impact:
               'upgrade' command for BCM5708S.

   2. Problem: CQ49156
               The FwUpg tool could not set value in 'cfg' command.
      Cause:
               The FwUpg tool did not parse some options of the
               'cfg' command correctly.
      Change:
               The FwUpg tool can parse these options correctly for
               the 'cfg' command.
      Impact:
               'cfg' command.

   3. Problem: CQ48706
               The FwUpg tool failed in 'log' command with 64-bit
               Operating System.  The log file contains data that
               is not readable.
      Cause:
               The FwUpg tool did not write the correct data to
               the log file.
      Change:
               The FwUpg tool can write the correct data to the
               log file.
      Impact:
               'log' command for all NX1 NICs.


Version 2.1.2 (Jul 30, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ48766, CQ48788
               Added additional option for 'cfg' command for
               BCM5771x NICs.
      Change:
               Added additional option for 'cfg' command for
               BCM5771x NICs.
      Impact:
               'cfg' command for BCM5771x NICs.

   Fixes:
   =====
   1. Problem: CQ48595
               The FwUpg tool failed in 'phy -ver' command for
               BCM57712 NIC.
      Cause:
               The FwUpg tool could not recognize the BCM57712
               NIC and could not execute the command correctly.
      Change:
               The FwUpg tool can recognize BCM57712 NIC and
               execute the command correctly.
      Impact:
               'phy' command for BCM57712.

   2. Problem: CQ48598
               The FwUpg tool corrupted the NVRAM after upgrading
               Bootcode from 6.0.26 to 6.0.27.
      Cause:
               The NVRAM map was modified for BCM5771x NICs.
               That caused the checksum error in some firmwares
               after upgrading bootcode.
      Change:
               The FwUpg tool uses the new NVRAM map when upgrading
               the bootcode.
      Impact:
               'upgrade' command for BCM57712.


Version 2.1.1 (Jul 01, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ48119
               Add new option for 'cfg' command for BCM5708/09/16.
      Change:
               Add new option for 'cfg' command for BCM5708/09/16.
      Impact:
               'cfg' command for BCM5708/09/16 NIC.

   2. Request:
               Add support for dual-PHY.
      Change:
               Add support for dual-PHY.
      Impact:
               'phy' command for BCM5771x NIC.


Version 2.1.0 (Jun 17, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ48315
               Add support for BCM57712.
      Change:
               Add support for BCM57712.
      Impact:
               BCM57712 NIC, BMAPI v7.20.0 is required.

   2. Request: CQ47284, CQ46034
               Add support for external PHY 84823/8727.
      Change:
               Add support for external PHY 84823/8727.
      Impact:
               Adapter with external PHY 84823/8727.

   3. Request: CQ46047
               Add support for 'upgrade -bc' command for
               BCM57712 NIC.
      Change:
               Add support for 'upgrade -bc' command for
               BCM57712 NIC.
      Impact:
               BCM57712 NIC, BMAPI v7.20.0 is required.

   Fixes:
   =====
   1. Problem: CQ48016
               The FwUpg tool failed to upgrade NCSI firmware
               for BCM57711 NIC.
      Cause:
               The NCSI firmwrae v6.x.x has the version field at
               a different location in the firmware file.
      Change:
               The FwUpg tool will retrieve the NCSI version from
               NCSI firmware file correctly either before or after
               v6.x.x.
      Impact:
               'upgrade -ncsi <file>' command.

   2. Problem: CQ47380
               The FwUpg tool failed to display external PHY firmware
               version for some external PHY.
      Cause:
               The FwUpg tool could not identify the external PHY
               correctly.
      Change:
               The FwUpg tool can identify the external PHY correctly.
      Impact:
               'ext_phy_fw -ver' command.


Version 2.0.7 (Apr 28, 2010)
---------------------------------

   1. Problem: CQ47001
               The FwUpg tool crashed while executing 'upgrade -m_pn'
               command with specific module file.
      Cause:
               The module file contains 'vendor name' that is more
               than 16 characters and that was not handled correctly
               by the FwUpg tool.
      Change:
               The FwUpg tool will detect the error and display the
               error message.
      Impact:
               'upgrade -m_pn <file>' command for the 57710/11 NICs.


Version 2.0.6 (Apr 26, 2010)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ47358
               The FwUpg tool failed in 'cfg -mac <MAC ADDRESS>'
               command.
      Cause:
               The FwUpg tool did not handle the '-mac' correctly
               when adding new feature in v2.0.5.
      Change:
               The FwUpg tool can now handle '-mac' option
               correctly for the 'cfg' command.
      Impact:
               'cfg -mac <MAC ADDRESS>' command for NX-II NICs.


Version 2.0.5 (Apr 20, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ47176
               Add requested new feature for 'cfg' command for
               BCM57710/11/12 NICs.
      Change:
               Added the requested feature for 'cfg' command.
      Impact:
               'cfg' command.

   Fixes:
   =====
   1. Problem: CQ47144
               The FwUpg tool did not upgrade the module file to the
               NVRAM correctly if the 'vendor name' in the module
               file contains space character.
      Cause:
               The FwUpg tool did not handle the space character in
               the 'vendor name' and 'part name' correctly.
      Change:
               The FwUpg tool can handle the 'vendor name' and 'part
               name' with space character and program them into the
               NVRAM correctly.
      Impact:
               'upgrade -m_pn <file>' command for the 57710/11 NICs.


Version 2.0.4 (Feb 26, 2010)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ46186
               Enhanced the option of 'cfg' command for
               BCM57710/11/12 NICs.
      Change:
               Enhanced the option of 'cfg' command for
               BCM57710/11/12 NICs.
      Impact:
               'cfg' command.


Version 2.0.3 (Nov 24, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ44483
               The FwUpg tool failed to enable WOL on 5709S LOM.
      Cause:
               The FwUpg tool did not identify the 5709S LOM correctly
               and did not allow the WOL to be set for the device.
      Change:
               The FwUpg tool can identify the 5709S LOM correctly
               and allow the WOL to be set for the device.
      Impact:
               'Cfg -wol' command for the 5706/5708/5709 LOMs.


Version 2.0.2 (Sep 03, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ43161
               The Combo MBA firmware file with UEFI driver inside
               should not be device specific.
      Change:
               The FwUpg tool will generate the device specific ID
               according to the underneath NIC and use it for the
               device ID of the UEFI driver.
      Impact:
               'upgrade -mba' command.

   Fixes:
   =====
   1. Problem: CQ41716
               The version string of MBA was not displayed aligned to
               the version strings of other firmwares in the 'dir'
               command for BCM57710 NICs.
      Cause:
               The version string of MBA was not displayed aligned to
               the version strings of other firmwares in the 'dir'
               command for BCM57710 NICs.
      Change:
               The version string of MBA is displayed aligned to
               the version strings of other firmwares in the 'dir'
               command for BCM57710 NICs.
      Impact:
               'dir' command for BCM57710 adapters.

   2. Problem: CQ42295
               The FwUpg tool failed to upgrade Combo MBA firmware
               file that contained only UEFI driver or FCODE.
      Cause:
               The FwUpg tool expected the Combo MBA firmware file
               always contained the MBA firmware as the first
               component.
      Change:
               The FwUpg tool will handle the Combo MBA firmware
               file that contained any combination of MBA firmware,
               UEFI driver, or FCODE.
      Impact:
               'upgrade -mba' command for BCM57710 adapters.


Version 2.0.1 (Aug 05, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ42825
               The FwUpg tool could not display the version of MODULES_PN
               image.
      Cause:
               The FwUpg tool did not retrieve the version of MODULES_PN
               image from NVRAM.
      Change:
               The FwUpg tool will retrieve the version of MODULES_PN
               image from NVRAM.
      Impact:
               'dir' command for BCM57710 adapters.

   Enhancements:
   =============
   1. Request: CQ41717
               Make the back up of NVRAM content during upgrading firmware
               to be optional.
      Change:
               The FwUpg tool will not back up the NVRAM content if the backup
               file in the 'upgrade' command is not specified.  See Readme.txt
               for detail.
      Impact:
               'upgrade' command.


Version 1.0.69 (Jul 29, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ42852
               The FwUpg tool will cause segmentation fault when
               upgrading MBA firmware in the 64-bit system.
      Cause:
               The FwUpg tool has a bug in checking the MBA version.
      Change:
               The bug in checking the MBA versoin is fixed.
      Impact:
               'upgrade -mba' command for BCM5709 adapters in the
               64-bit system.


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

   Fixes:
   =====
   1. Problem: CQ42342
               FwUpg tool was not able to upgrade the NCSI firmware
               for BCM57710.
      Cause:
               The FwUpg tool can't detect the existing NCSI firmware
               in the NVRAM and does not allow the upgrade operation
               to continue.
      Change:
               The FwUpg tool can detect the NCSI firmware in the NVRAM
               and allow the upgrade operation to complete.
      Impact:
               'upgrade -ncsi' command for BCM57710 adapters.


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

   Fixes:
   =====
   1. Problem: CQ42219
               FwUpg tool was not able to upgrade the external PHY
               firmware for BCM8727 PHY.
      Cause:
               The FwUpg tool can't recognize the BCM8727 PHY on some
               adapters.
      Change:
               The BCM8727 PHY on those adapters can be detected now.
      Impact:
               'phy' command for NX2 adapters.


Version 1.0.66 (Jun 19, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ42097
               FwUpg tool was not able to upgrade the MBA firmware without
               the '-F' option.
      Cause:
               The FwUpg tool has a bug when it tries to get the MBA version
               from NVRAM for a comparison to the MBA version in the file.
      Change:
               The bug is fixed and the FwUpg tool can get the MBA version
               from the NVRAM and compare it to the version of the file.
      Impact:
               'upgrade -mba' command for NX2 adapters.


Version 1.0.65 (Jun 12, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ40897
               Added '-m_pn' option to the 'upgrade command to upgrade
               approved I/O Modules for BCM5771x NICs.
      Change:
               The feature is implemented.
      Impact:
               'upgrade -m_pn <io file> <dump>' command.


Version 1.0.64 (Jun 04, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ40131
               Added 'dir -delete <entry>' command to delete firmware
               and its entry in directory from NVRAM.
      Change:
               The feature is implemented.
      Impact:
               'dir -delete <entry>' command.

   Fixes:
   =====
   1. Problem: CQ41609
               FwUpg tool does not show management firmware in 'cfg -show'
               command when NCSI was programmed in NVRAM.
      Cause:
               The new NCSI firmware contains only NCSI entry in the NVRAM
               directory.  The FwUpg tool was checking on both NCSI and
               NCSI_ELIB which were contained in the old NCSI firmware for
               the existence of NCSI firmware.
      Change:
               The FwUpg tool will check only NCSI entry in the NVRAM
               directory for the existence of NCSI firmware.
      Impact:
               NCSI firmware for NX2 family of devices.

   2. Problem: CQ41554
               The FwUpg tool added iSCSI CFG2 in NVRAM after programming
               iSCSI bootcode on the single port adapter.
      Cause:
               The FwUpg tool automatically added the iSCSI CFG into NVRAM
               when programming iSCSI bootcode.  Both iSCSI CFG and iSCSI
               CFG were added due to a bug in programming iSCSI bootcode.
      Change:
               The FwUpg tool will add the iSCSI CFG/CFG2 according to the
               number of ports of the NIC.
      Impact:
               'prg -ib' command on BCM57710 NIC.

   3. Problem: CQ41790
               The 'upgrade -l2t' command does not work in command line mode.
      Cause:
               The FwUpg tool could not recognized the '-l2t' option in command
               line mode.
      Change:
               The FwUpg tool can process the '-l2t' option in command line
               mode and complete the operation.
      Impact:
               'upgrade -l2t' command on BCM57710 NIC in command line mode.


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

   Fixes:
   =====
   1. Problem: 
               With correct MBA file, command line nvram upgrade call
			   with "-all" option would fail.
      Cause:
               The file/device MBA filtering was not done correctly.
      Change:
               Seperated the logic of validating the MBA file versus
			   validating the file against the device.
      Impact:
               MBA upgrade on NX2 family of devices.

   2. Problem: CQ41050
               The FwUpg tool allows WOL enabling in port 3 & 4 of the
               BCM5709 4-port adapter.
      Cause:
               The FwUpg tool did not check the condition for WOL enabling
               of the port.
      Change:
               The FwUpg tool will will check the condition before enabling
               WOL capability of the port.
      Impact:
               Enabling WOL capability of the BCM5709 4-port NIC.


Version 1.0.62 (May 23, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ41425
               Added support to upgrade iSCSI boot with IPv6.
      Change:
               Added support to upgrade iSCSI boot with IPv6.
      Impact:
               'upgrade -ib|-ib_ipv6|-ib_ipv4n6' command.


Version 1.0.61 (May 19, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ39424
               Added support to add iSCSI bootcode for a selected
               BCM57710 NIC.
      Change:
               Added support to add iSCSI bootcode for a selected
               BCM57710 NIC.
      Impact:
               'prg -ib' command for a selected BCM57710 NIC.

   2. Request: CQ39660
               Added and update UEFI driver from MBA binary file.
      Change:
               The requested feature is implemented.
      Impact:
               'upgrade -mba' command.

   3. Request: CQ39988
               Added the ability to display version for UEFI driver
               and FCODE components.
      Change:
               The requested feature is implemented.
      Impact:
               'dir' command.

   Fixes:
   =====
   1. Problem: CQ39074
               The NCSI upgrade failed with segmentation fault for BCM5709
               on PPC64 system.
      Cause:
               The 64-bit pointer was not handled correctly when upgrading
               the NCSI firmware.
      Change:
               The 64-bit pointer is handled correctly when upgrading
               the NCSI firmware.
      Impact:
               'upgrade -ncsi' command for NCSI firmware for BCM5709 adapters
               on the PPC64 system.

   2. Problem: CQ39075
               The CRC check failed for BCM5709 on PPC64 system.
      Cause:
               The Big-Endian variable was not handled correctly when
               processing the 'crc' command.
      Change:
               The Big-Endian variable is now handle correctly when
               processing the 'crc' command.
      Impact:
               'crc' command for BCM5709 on PPC64 system.

   3. Problem: CQ40134
               Failed to upgrade to new NCSI binary file v2.0 or later.
      Cause:
               The new NCSI binary file has a different format that was
               not processed correctly by FwUpg tool.
      Change:
               The FwUpg tool will process the old and new format of the
               NCSI binary file correctly.
      Impact:
               'upgrade -ncsi' command for BCM5709 NIC.

   4. Problem: CQ37882
               The FwUpg tool downgrded IPMI v1.05 for BCM5708 without "-F"
               option.
      Cause:
               The IPMI v1.05 binary file used a different header and caused
               the version validation to fail.
      Change:
               The FwUpg tool will detect the different header and make an
               adjustment to retrieve the version.
      Impact:
               "upgrade -ipmi" that uses IPMI v1.05 for BCM5708 NIC.

   5. Problem: CQ40998
               The BACS failed to display the external PHY firmware version
               after using FwUpg tool to upgrade the bootcode.
      Cause:
               The upgrade function did not work correctly and corrupt the
               bootcode.
      Change:
               The FwUpg tool will upgrade the bootcode correctly and the
               external PHY firmware version can be returned correctly.
      Impact:
               "upgrade -bc" command for BCM57710 NIC.

   6. Problem: CQ40999
               The FwUpg tool failed to display the external PHY firmware
               version for adapter with BCM8727 PHY.
      Cause:
               The FwUpg tool did not recognize the BCM8727 PHY.
      Change:
               The FwUpg tool can now recognize the BCM8727 PHY and display
               the external PHY firmware version correctly.
      Impact:
               "phy -ver" command on adapter with BCM8727 PHY.


Version 1.0.60 (Mar 12, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ39853
               The 'upgrade -mba' caused segmentation fault when upgrading
               the combined MBA firmware file in 64-bit Linux system for
               BCM57710/57711/57712 adapters.
      Cause:
               The 64-bit pointer was not handled correctly when upgrading
               the combined MBA firmware.
      Change:
               The 64-bit pointer is handled correctly when upgrading
               the combined MBA firmware.
      Impact:
               'upgrade -mba' command for combined MBA firmware for
               BCM57710/57711/57712 adapters.


Version 1.0.59 (Feb 18, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ39013
               The FWUPG tool did not check the PHY firmware image
               file against the PHY device to be upgraded.
      Cause:
               The FWUPG tool did not check the PHY firmware image
               file against the PHY device to be upgraded.
      Change:
               The FWUPG tool will check the header in the PHY firmware
               image file against the PHY device before upgrading
               the PHY firmware.
      Impact:
               'phy -upg' command for all adapters.

    Note: New PHY firmware image file with header has to be used.


Version 1.0.58 (Dec 19, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ28499
               Added support to the old format of M-Key/U-Key
               block checksum.
      Change:
               Added support to the old format of M-Key/U-Key
               block checksum.
      Impact:
               'crc' and 'restore' command for BCM5706-based
               adapters with old format of M-Key/U-Key.


Version 1.0.57 (Dec 15, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request:
               FWUPG will validate the BMAPI and driver versions for
               the "phy" command.
      Change:
               FWUPG will validate the BMAPI and driver versions for
               the "phy" command.
      Impact:
               The 'phy' command.  The BMAPI has to be v7.15.8 or later.
               The VBD driver has to be v4.8.9 or later.


Version 1.0.56 (Dec 02, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ36353
               Added support to upgrade external PHY firmware
               for BCM57710/57711.
      Change:
               Added support to upgrade external PHY firmware
               for BCM57710/57711.
      Impact:
               New 'phy' command to upgrade external PHY firmware.


Version 1.0.55 (Oct 08, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ35469/CQ37498
               Added support to program iSCSI firmware into the
               NVRAM for some selected adapters.
      Change:
               Added support to program iSCSI firmware into the
               NVRAM for some selected adapters.
      Impact:
               'prg -ib' command for some selected adapters.

   Fixes:
   =====
   1. Problem: CQ37719
               The FWUPG tool displayed an "Invalid checksum in RV field"
               error message when executing the "cfg -wol 1" command.
      Cause:
               The checksum of VPD-R was not set correctly and the error
               message was displayed when the checksum error was detected.
      Change:
               The checksum of VPD-R is set correctly.  There will be no
               checksum error when executing the "cfg -wol 1" command.
      Impact:
               'cfg' command for all adapters.

   2. Problem: CQ37734
               The FWUPG tool did not display the iSCSI boot version string
               correctly in the PPC64 machine.
      Cause:
               The FWUPG tool did not handle the iSCSI boot version string
               correctly in the PPC64 machine.
      Change:
               The FWUPG tool handles the iSCSI boot version string correctly
               in the PPC64 machine now.
      Impact:
               'dir' command to display iSCSI boot version for all adapters.

   3. Problem: CQ36701
               The FWUPG tool did not check the version of I_B_CPRG firmware
               before upgrading it.
      Cause:
               The FWUPG tool did not check the version of I_B_CPRG firmware
               before upgrading it.
      Change:
               The FWUPG tool will check the version of I_B_CPRG firmware
               before upgrading it.
      Impact:
               'upgrade -ib -c -p' command for BCM57710 adapters.


Version 1.0.54 (Oct 03, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ36354
               Added support to upgrade L2 firmware for BCM57710.
      Change:
               Added support to upgrade L2 firmware for BCM57710.
      Impact:
               BCM57710-based adapters.

   2. Request: CQ37091
               Remove support for upgrading IPMI/UMP for BCM57710.
      Change:
               Remove support for upgrading IPMI/UMP for BCM57710.
      Impact:
               BCM57710-based adapter.

   Fixes:
   =====
   1. Problem: CQ37255
               The FWUPG tool displayed garbage value with 'cfg' command
               without any parameter.
      Cause:
               The FWUPG tool did not check for this error condition.
      Change:
               The FWUPG tool checks for this error condition and will
               display the correct error message.
      Impact:
               'cfg' command for all adapters.

   2. Problem: CQ36967
               The FWUPG tool return wrong exit code when downgrading
               firmware without '-F' option for BCM57710.
      Cause:
               The FWUPG tool did not return the exit code correctly
               when detecting this error condition.
      Change:
               The FWUPG tool will return the correct exit code when
               detecting this error condition.
      Impact:
               'upgrade' command for all adapters.


Version 1.0.53 (Aug 01, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem:
               The "upgrade -ib -p" command does not work in the
               command line mode.
      Cause:
               The "upgrade -ib -p" command was not correctly
               processed in the command line mode.
      Change:
               The "upgrade -ib -p" command is now processed
               correctly in the command line mode.
      Impact:
               The "upgrade -ib" command in command line mode
               for all Network NICs.


Version 1.0.52 (Jul 29, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ36543
               The "upgrade -ib" command does not upgrade the iSCSI
               Configration Program from the iSCSI image file.
      Cause:
               The "upgrade -ib" command was originally designed to
               upgrade the iSCSI boot code only.
      Change:
               The "upgrade -ib" command will have additional options
               "-c" and "-p" to upgrade the iSCSI Configuration and
               the iSCSI Configuration Program if they exist.
      Impact:
               The "upgrade -ib" command for all Network adapters.


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

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


Version 1.0.50 (Jul 08, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ36233
               The "upgrade -bc" command does not work for BCM57710
               with v1.0.48 or later.  It works with v1.0.47.
      Cause:
               A bug was injected in v1.0.48 that caused the type of
               Bootcode header for BCM57710 was not checked correctly.
      Change:
               The bug is fixed and the type of Bootcode header is
               checked correctly.
      Impact:
               The "upgrade -bc" command for BCM57710 adapters.


Version 1.0.49 (Jul 07, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ36203
               The "upgrade -mba" command does not work for v1.0.48.
               It works for v1.0.47.
      Cause:
               A bug was injected in v1.0.48 that caused the MBA
               firmware was not recognized.
      Change:
               The bug is fixed to recognize the MBA firmware file.
      Impact:
               The "upgrade -mba" command for all NX2 adapters.


Version 1.0.48 (Jul 03, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ32202
               Added capability to program MBA firmware for some adapters.
      Change:
               Added capability to program MBA firmware for some adapters.
      Impact:
               "prg" command for some specific adapters.


Version 1.0.47 (Jun 09, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ35769
                FwUpg tool failed to work with BAMPI v7.11.0.
      Cause:
                The FwUpg tool used common data structure that was
                available only in BMAPI v7.12.0.
      Change:
                The FwUpg tool uses common data structure that is
                available in BMAPI v7.11.0.
      Impact:
                All Network adapters.


Version 1.0.46 (Jun 04, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ34942
               Added "-2p5g" option in "cfg" command to enable
               or disable the support of 2.5Gb on LOM version
               of 5708S/5709S.
      Change:
               Added "-2p5g" option in "cfg" command to enable
               or disable the support of 2.5Gb on LOM version
               of 5708S/5709S.
      Impact:
               LOM version of 5708S/5709S adapters.


Version 1.0.45 (Apr 17, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ34826
                The "-all" option does not work since v1.0.41.
      Cause:
                An uninitialized variable caused error when
                FWUPG processed the "-all" option.
      Change:
                Use a different way to process the "-all" option.
      Impact:
                The "-all" option on add adapters.


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

   Fixes:
   ======
   1. Problem: CQ34754
                The "cfg -ncsi" command to enable/disable the
                ncsi capability did not apply to both ports.
      Cause:
                The FWUPG only set the configuration to one port.
      Change:
                The FWUPG now set the configuration to both ports.
      Impact:
                The "cfg" command on BCM5709 adapter.


Version 1.0.43 (Apr 08, 2008)
---------------------------------

   Fixes:
   ======
   1. Problem: CQ34434
                The "upgrade" command to downgrade the bootcode
                without "-F" option will corrupt the bootcode
                for BCM57710 adapter.
      Cause:
                The "upgrade" command corrupted the BootCode
                area due to a problem in FWUPG.  It caused the
                calculated CRC did not match to the stored CRC.
      Change:
                The problem is fixed and the BootCode area is
                no longer corrupted.
      Impact:
                The "upgrade" command on BCM57710 adapter.


Version 1.0.42 (Mar 25, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ34411
               Update the usage information for the "upgrade"
               and "cfg" commands to support NCSI firmware.
      Change:
               Update the usage information for the "upgrade"
               and "cfg" commands to support NCSI firmware.
      Impact:
               All adapters.


Version 1.0.41 (Mar 20, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ34083
               Add the support to upgrade NCSI firmware for
               BCM5709 adapter.
      Change:
               Added the support to upgrade NCSI firmware for
               BCM5709 adapter.
      Impact:
               BCM5709-based adapters.


Version 1.0.40 (Mar 10, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ34116
               Restore the support for BCM57710 NIC.
      Change:
               Restore the support for BCM57710 NIC.
      Impact:
               BCM57710-based adapters.

   Fixes:
   =====
   1. Problem: CQ33730
                There was a CRC error in the BootCode area
                after executing the "restore" command.
      Cause:
                The "restore" command corrupted the BootCode
                area due to a problem in FWUPG.  It caused the
                calculated CRC did not match to the stored CRC.
      Change:
                The problem is fixed and the BootCode area is
                no longer corrupted.
      Impact:
                The "restore" command on BCM57710 adapter.


Version 1.0.39 (Feb 08, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Remove the support for BCM57710 NIC.
      Change:
               Remove the support for BCM57710 NIC.
      Impact:
               BCM57710-based adapters.

   Fixes:
   =====
   1. Problem: CQ33451
                The 57710 Bootcode was written to BCM5709
                NVRAM without validating the image file.
      Cause:
                The Bootcode image file was not validated by
                FWUPG for the "upgrade -bc" command.
      Change:
                The Bootcode image file is validated against
                the device to be upgraded.  Only Bootcode image
                file bc710v42.0 or later has the correct image
                header information.
      Impact:
                All Network adapters.

   2. Problem: CQ33729
                The BCM57710 failed to be upgraded with Bootcode
                image file bc710v42.0.
      Cause:
                The Bootcode image file bc710v42.0 contain the image
                type information in the image header.  The FWUPG
                did not validate the image type information correctly
                and prevented the Bootcode to be upgraded.
      Change:
                The FWUPG validates the image type against the device
                correctly and the Bootcode image file bc710v42.0 can
                be upgraded to the BCM57710 NIC.
      Impact:
                BCM57710 adapters.


Version 1.0.38 (Jan 24, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ33436
                The 5708/5709 MBA firmware was written to BCM57710
                NVRAM without validating the image file.
      Cause:
                The MBA image file was not validated by FWUPG for
                the "upgrade -mba" command.
      Change:
                The MBA image file is validated against the device
                to be upgraded.
      Impact:
                All Network adapters.


Version 1.0.37 (Jan 09, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ33296
                The "cfg -mba 1" command caused FWUPG to crash with
                Segmentation fault.
      Cause:
                Data parameters were not set up correctly when processing
                the command.
      Change:
                The bug was fixed and these data parameters are set up
                correctly.
      Impact:
                BCM57710-based adapter.


Version 1.0.36 (Jan 03, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request:
                Use media type returned by BMAPI to determine
                the media type of the device.
      Change:
                The FWUPG will use the media type returned by
                BMAPI to determine the media type instead of
                reading from register directly.
      Impact:
                BCM5706/5708/5709-based adapters.


Version 1.0.35 (Dec 28, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ33221
                The "upgrade" command does not work for some
                BCM5708 adapters.
      Cause:
                The media type of the adapter was not detected
                correctly for some BCM5708 adapters.  The value
                returned by BMAPI and used by FWUPG to determine
                the media type is not the same as the value in
                the device's register.
      Change:
                The FWUPG will read directly from the device's
                register and use the the value to determine the
                media type.  This is the method used by v1.0.31
                and earlier versions.
      Impact:
                BCM5706/5708/5709-based adapters.


Version 1.0.34 (Dec 22, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ33199
                The "restorenvram" command does not work for
                5709S adapter.
      Cause:
                The dumped image file from 5709S was incorrectly
                identified as the image for the 5709C adapter.
                The error message was posted and the "restorenvram"
                command failed.
      Change:
                The dumped image file is now identified as the image
                for the 5709S adapter.  The "restorenvram" command
                is completed successfully.
      Impact:
                BCM5709-based adapters with SERDES media type.


Version 1.0.33 (Dec 20, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ33160
                The boot code for 5709S adapter can't be upgraded.
      Cause:
                The 5709S adapter was detected with COPPER media
                type by FWUPG.
      Change:
                The media type of 5709S adapter is detected correctly
                now and the boot code for 5709S can be upgraded.
      Impact:
                BCM5709-based adapters with SERDES media type.


Version 1.0.32 (Dec 04, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Support BCM57710 dual port NIC.
      Change:
               Added code to support BCM57710 dual port NIC.
      Impact:
               BCM57710-based adapters.
               The BMAPI v7.8.9 and the corresponding Windows drivers
               are required for this feature.


Version 1.0.31 (Nov 09, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ32184
                For BCM5709, a system reboot is required for the
                upgraded firmware to take effect.
      Cause:
                Currently, the FWUPG tool post a message to use
                the reset command or reload the driver.  Either
                action does not work for BCM5709.
      Change:
                The FWUPG tool post a "system reboot" message in
                order for the upgraded firmware to take effect.
      Impact:
                BCM5709-based adapters.

   Enhancements:
   =============
   1. Request: CQ27858
               Added an option in "cfg" command to display the settings
               of current configuration.
      Change:
               The "-show" option is added to the "cfg" command.
      Impact:
               The "cfg" command for Network adapters.


Version 1.0.30 (Oct 15, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ31848
                The "cfg -ipmi 1" command failed to detect the IPMI
                firmware in the NVRAM for BCM5709.
      Cause:
                The FWUPG utility checked for IPMI_CFG, IPMI_INIT, and
                IPMI_SERV to make sure the IPMI firmware is present.
                But, the IPMI firmware for BCM5709 has only IPMI_CFG and
                IPMI_INIT entries in the directory.  
      Change:
                The FWUPG utility will check for IPMI_CFG, IPMI_INIT, and
                IPMI_SERV for 5706/5708 as before.  But, it will check for
                IPMI_CFG, IPMI_INIT for 5709.
      Impact:
                BCM5709-based adapters.


Version 1.0.29 (Oct 09, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ31770
                The FWUPG utility allows the 5709 IPMI firmware to be
                upgraded to a 5706/5708 device.
      Cause:
                The IPMI image was not checked correctly.
      Change:
                The FWUPG utility checks the IPMI image correctly and
                prevents the 5709 IPMI firmware to be upgraded to a
                5706/5708 device.
      Impact:
                BCM5706/5708-based adapters.


Version 1.0.28 (Sept 26, 2007)
---------------------------------

   Enhancements:
   ============
   1. Request:
                If there is no proper header in the UMP firmware file, the
                UMP upgrade command for BCM5709 should fail.
      Change:
                The upgrade command will fail for 5709 if the UMP firmware
                does not have header information.
      Impact:
                BCM5709-based adapters.


Version 1.0.27 (Sept 19, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ31279
                The FWUPG utility should prevent the 5709 UMP firmware to be
                upgraded to a BRCM5708/5706 adapter or vice versa.
      Cause:
                The FWUPG utility did not check the UMP firmware header before
                upgrading the UMP firmware.
      Change:
                The FWUPG utility will check the UMP firmware header before
                upgrading the UMP firmware.
      Impact:
                All Network adapters.


Version 1.0.26 (Sept 10, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ30940
                The FWUPG command "restorenvram <filename> config" did not
                restore the iSCSI Config data.
      Cause:
                The FWUPG only restored the Manufacturer Config data when the
                'config' option was specified.
      Change:
                The FWUPG utility will restore both Manufacturer and iSCSI
                Config data when the 'config' option was specified.
      Impact:
                All Network adapters.

   2. Problem: CQ30990
                Typo in Release.txt and incorrect examples in Readme.txt.
      Cause:
                There were errors in documentation.
      Change:
                Typo and examples are corrected.
      Impact:
                Documentation.


Version 1.0.25 (Aug 06, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ30829
                The FWUPG crashed in command line mode if correct MAC address
                is entered without command.
      Cause:
                The FWUPG utility tried to process the command that was not
                specified.
      Change:
                The FWUPG utility will make sure the command is entered before
                processing it.  If the command is not specified, an error
                message is issued.
      Impact:
                All Network adapters in command line mode.


Version 1.0.24 (July 26, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ30793
                The FWUPG can't upgrade the Boot Code firmware for BCM5709.
      Cause:
                The BCM5709 board type was not detected correctly.
                Without the correct board type, the boot code is not allowed
                to be upgraded.
      Change:
                Detected the board type and set up the Chip ID correctly .
      Impact:
                BCM5709 adapters.


Version 1.0.23 (July 20, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem:
                The FWUPG tool returned 'driver version is too old'
                error message on adapter that has 0 on the first 0x600
                bytes of NVRAM.
      Cause:
                The driver was not loaded for such a device.  Therefore,
                the driver version returned was 0.0.0.
      Change:
                The FWUPG will check if driver is loaded before comparing
                the driver version to the minimum requirment.
      Impact:
                All Network adapters.

   2. Problem: CQ30598
                The old Head Quarter address is used in Readme.txt.
      Cause:
                Corporation Head Quarter was moved to new location.
      Change:
                Removed the Head Quarter address from Readme.txt.
      Impact:
                None.

   3. Problem: CQ30495
                Winfwnx2 returned error code 88 when an invalid MAC address
                was specified in a system with only one adapter.
      Cause:
                In the system with only one adapter, the <MAC address>
                parameter might be treated as a command.  Therefore, the
                error code 88 was issued.
      Change:
                A more specific error message was added before the error code
                88 to indicate the possible reason of the Invalid Command.
      Impact:
                All Network adapters.

   4. Problem: CQ30709
                Winfwnx2 Readme.txt was outdated.
      Cause:
                Some information in the readme.txt was outdated.
      Change:
                Updated the information in readme.txt.
      Impact:
                None.


Version 1.0.22 (July 16, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request:
               Support BCM5709 dual port NIC.
      Change:
               Added code to support BCM5709 dual port NIC.
      Impact:
               BCM5709-based adapters.
               The Linux bnx2 driver v1.6.3b is required for this feature.


Version 1.0.21 (June 12, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ29693
               Added the ability to do "First time install" of iSCSI
               boot in the field through 'prg' and 'restorenvram' for
               selective OEM Network adapters.
      Change:
               The 'prg' command can program iSCSI boot firmware
               into the NVRAM.
               The 'restorenvram' command is able to pick up an
               image file that contains the iSCSI boot firmware
               and restore them into the NVRAM of an identical device
               that did not have the iSCSI boot firmware previously.
      Impact:
               Selective OEM Network adapters.


Version 1.0.20 (May 30, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ29559
               Added the ability to do "First time install" of iSCSI
               boot in the field through 'prg' and 'restorenvram' for
               selective Network adapters.
      Change:
               The 'prg' command can program iSCSI boot firmware
               into the NVRAM.
               The 'restorenvram' command is able to pick up an
               image file that contains the iSCSI boot firmware
               and restore them into the NVRAM of an identical device
               that did not have the iSCSI boot firmware previously.
      Impact:
               Selective Network adapters.


Version 1.0.19 (May 3, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem:
                The 'upgrade' returned error code = 2 and could
                not upgrade the boot code.
      Cause:
                The FWUPG checked the keyword against an uninitialized
                variable and returned the error.
      Change:
                The uninitialized variable is now assigned the input
                keyword before it is checked.
      Impact:
                All Network adapters.


Version 1.0.18 (May 1, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ27416
               Added a '-noreset' option in 'upgrade' command and a
               new 'reset' command in Command Line Mode.
      Change:
               Implemented code for the new features.
               The '-noreset' option in 'upgrade' command wil request
               the FWUPG not to reset the NIC after upgrade is complete.
               The 'reset' command will request the FWUPG to reset
               the selected NIC.
               Both features are valid only in Command Line Mode.
      Impact:
               All NetXtreme adapters II.


Version 1.0.17 (April 30, 2007)
---------------------------------

   Fixes:
   =====
   1. Problem:  CQ29198
                The 'restorenvram' command restored the NVRAM content
                even the 'idmatch' option was not spelled correctly.
      Cause:
                The 'restorenvram' command restored the NVRAM content
                by using the default setting if the 'idmatch' option
                was spelled wrong or absent.  Actually, the FWUPG will
                restore the NVRAM content with the default setting if
                any option keyword is not spelled correctly.
      Change:
                The 'restorenvram' command will not restore the NVRAM
                content if any option keyword is spelled wrong.  An
                error message is displayed to user.
      Impact:
                All Network adapters.


Version 1.0.16 (April 18, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request:   CQ29156
                 Support PXE-CLP and PXE-iSCSI image file in 'upgrade'
                 command.
      Change:
                 Added the requested feature to the 'upgrade' command.
      Impact:
                 All Network adapters.


Version 1.0.15 (April 13, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request:   CQ29002
                 Added 'idmatch' option in 'restore' command.
                 The image file is restored only if all 4 IDs in the
                 image file match to those in the device.
      Change:
                 Added the requested feature to the 'restore' command.
      Impact:
                 All Network adapters.

    Fixes:
    =====
    1. Problem:  CQ28237
                 winfwnx2 displays wrong ipmi version.
       Cause:
                 The old version format caused confusion to the user. 
       Change:
                 The version is now displayed in the new version format.
       Impact:
                 All Network adapters.


Version 1.0.14 (March 14, 2007)
---------------------------------

   Enhancements:
   =============
   1. Request:   CQ27345
                 Added capability to upgrade iSCSI boot firmware.
      Change:
                 Added the requested capability to the 'upgrade' command.
      Impact:
                 All Network adapters.

   2. Request:   CQ28267
                 Clarify the error message when the drivers are out of date.
      Change:    
                 Additional information was added in the message to request
                 the user to update the drivers by using the Driver Installer
                 Program.
      Impact:
                 All Network adapters.


Version 1.0.13 (October 24, 2006)
---------------------------------

   Fixes:
   =====
   1. Problem:   CQ27222
                 "restorenvram" fails on 5708S B2 with ram size of 1Mb. 
      Cause:
                 The algorithm to detect whether the dump image was for
                 fiber type of device was incorrect.
      Change:    
                 Modified the related routine to determine media type
                 by the specified device id.
      Impact:
                 'restorenvram' should allow any NetXtremeII fiber  
                 devices to restore its own image using the dump file 
                 previously generated by the 'dumpnvram' command.


Version 1.0.12 (October 12, 2006)
---------------------------------

   Enhancements:
   =============
   1. Request:  
                 To require administrator privilege to run this utility
                 for Windows Vista or later.
      Change:
                 Not to run the application when user is under non-
                 administrator privilege mode.
      Impact:
                 Windows Vista or later.

   2. Request:   CQ24703, CQ24810 
                 To allow user to enable/disable management firmware.
      Change:
                 Added the requested capability to the 'cfg' command.
      Impact:
                 'cfg -ipmi 1' command to enable ipmi firmware and
                 'cfg -ipmi 0' command to disable ipmi firmware.
                 'cfg -ump 1' command to enable ump firmware and
                 'cfg -ump 0' command to disable ump firmware.
                 Readme.txt was updated to document this change.

   3. Request:   CQ24810 
                 To allow user to enable/disable PXE.
      Change:
                 Added the requested capability to the 'cfg' command.
      Impact:
                 'cfg -mba 1' command to enable pxe firmware and
                 'cfg -mba 0' command to disable pxe firmware.
                 Readme.txt was updated to document this change.

   4. Request:  
                 To properly display help information for every command
                 followed by '?' or 'help'.
      Change:
                 Added the requested capability.
      Impact:
                 Help information display for every supported command.

   Fixes:
   =====
   1. Problem:   CQ26650
                 WinFwNx2: Text redirection did not work. This was
                 only observed on WinFwNx2. 
      Cause:
                 The stdout was not flushed out. 
      Change:    
                 Modified the related output routines to flush out the
                 stdout.
      Impact:
                 User should be able to redirect the program output to
                 a file.

   2. Problem:   CQ25929
                 Possible misleading errors for user mistakes. 
      Cause:
                 Error handlings implemented in previous releases. 
      Change:    
                 Enhanced some error handlings to address the 
                 related scenarios.
      Impact:
                 Use case scenario around the reported cases.

   3. Problem:   CQ26128  
                 FwUpg utility's help description is not user friendly.
      Cause:
                 No usage scenarios or examples were shown in 
                 Readme.txt. 
      Change:
                 Modified Readme.txt to update "Command Usage" section.
                 In addition, "Examples" section section was added.
      Impact:
                 "Command Usage" and "Examples" sections in Readme.txt.


Version 1.0.11 (July 21, 2006)
-------------------------------
 
   Fixes:
   =====
   1. Problem:   Cont00025995
                 xdiag allows partial upgrade on IPMI firmware
      Cause:
                 The overall NVRAM size calculation did not 
                 take the IPMI_CFG block into account 
                 (if that block already exists, it will be 
                 included into the calculation). 
                 As a result, the upgrade process still went 
                 through even though the NVRAM cannot fit the IPMI_CFG. 
                 By the time IPMI_CFG is being programmed, xdiag 
                 finally detected the short of storage space. 
      Change:    
                 The fix is to include the IPMI_CFG block calculation. 
                 This is related to CQ#25996. 
      Impact:
                 Use case scenario around the bug.


Version 1.0.10 (July 20, 2006)
-------------------------------
 
   Fixes:
   =====
   1. Problem:   Cont00025872
                 XDiag: BC1 updates while BC2 does not update if NVRAM 
                 runs out of space for BC2 on Fiber 5708B1 ST M45PE10
      Cause:
                 The xdiag upgrades one image at a time, and it does not 
                 check for the overall size for NVRAM storage availability 
                 before starting the upgrade. As a result, it is possible 
                 that the NVRAM runs out of storage after upgrading 
                 one image and has no room for the second one. 
      Change:    
                 A feature is added to determine the overall size 
                 before commiting to the upgrade.
      Impact:
                 Use case scenario around the bug.
                 
                 
   2. Problem:   Cont00025955
                 Unable to upgrade/install iSCSI Boot firmware using 
                 xDiag v1.4.7
      Cause:
                 The iSCSI boot image has a component that is not used 
                 by Network products. So, it is not considered a 
                 recognizable image. Seeing this, xdiag decide to abort 
                 the whole upgrade process. 
      Change:    
                 The fix is to skip any unrecognizable images.
      Impact:
                 Use case scenario around the bug.
                 
                 
Version 1.0.9 (July 17, 2006)
-------------------------------
 
   Fixes:
   =====
   1. Problem:   Cont00025893
                 "Winfwnx2 -all [command]" gives error "Adapter not found" 
                 when two Teton cards are in System
      Cause:
                 We were checking for the validity of the adapter handle
                 being valid in all scenarios. In this particular bug case,
                 the user wanted to upgrade with the "-all" option. In this
                 scenario, we don't need to have the adapter handle to be
                 valid. 
      Change:    
                 Skipping checking the validity of the adapter handle if 
                 the user attempted an updated with "-all" option.
      Impact:
                 Use case around the bug. 


Version 1.0.8 (July 14, 2006)
-------------------------------
 
   Fixes:
   =====
   1. Problem:   CQ25626
                 Actions occurred on a non-specified device without 
                 warning if an unsupported device is specified.
      Cause:
                 If there was only one qualified NIC present, the code 
                 should have ensured that the specified adapter 
                 actually matched the qualified NIC before proceeding 
                 with any operation. 
      Change:    
                 Corrected the related function to do further 
                 validations.
      Impact:
                 No requested operation should be performed on an 
                 unqualified NIC.
                 Readme.txt was updated to include new messages.
                 
                 
Version 1.0.7 (July 11, 2006)
-------------------------------

   Fixes:
   =====
   1. Problem:   ( Cont00025750 )
                 Winfwnx2: unable to upgrade UMP FW through "-all"
      Cause:
                 We detect the validity of the UMP firmware image
                 by checking to see if we can obtain the UMP 
                 firmware version. This code relies on a valid
                 device being the active selection. Prior to the 
                 fix, the active device selection was not set.
      Change:    
                 Setting the first device as the currently 
                 active device to extract the UMP version info
                 out of the firmware image file.
      Impact:
                 Use case scenario around the bug.
                 
   2. Problem:   ( Cont00025762 )
                 Winfwnx2: Mistyping parameter after -all results 
                 in no error
      Cause:
                 The code was returning the right error code but just
                 was not echoing the error message.
      Change:
                 We now echo the correct error message for the 
                 errorcode in the scenario mentioned in the bug.
      Impact:
                 Use case scenario around the bug.                 
                 
                 
Version 1.0.6 (July 06, 2006)
-------------------------------

   Fixes:
   =====
   1. Problem:   ( Cont00025621 )
                 Winfwnx2:  Unable to use additional flags when 
                 upgrading iSCSI Boot
      Cause:
                 The options should not have been listed in the
                 readme.txt and help.
      Change:    
                 Removed the unneeded options from both help 
                 and readme.txt.
      Impact:
                 Help and readme.txt information.
                 
   2. Problem:   ( Cont00025626 )
                 Actions occur on a non-specified device, without 
                 warning if an unsupported device is specified.
      Cause:
                 If there was only one NIC present that is supported
                 for the upgrade/restore operation, the code did not
                 bother to check if the supplied NIC info was valid
                 or not. It just picked the NIC and programmed in to
                 it.
      Change:    
                 We now check to see if a invalid MAC/service name
                 was specified and report error.
      Impact:
                 Scenario around the bug.  
                 
   3. Problem:   ( Cont00025615 )
                 Winfwnx2 1.0.5: Incorrect version (1.0.4 shown) and 
                 upgrading same or lower version FW in non-interactive 
                 mode w/o "-F" gives a wrong error
      Cause:
                 The code was not setup to capture the return code
                 in this scenario properly. Hence, it gave the wrong
                 unknown error code message.
      Change:    
                 We now capture the error code properly in such a 
                 scenario and report the same to the user. 
      Impact:
                 Scenario around the bug.  
                 
   4. Problem:   ( Cont00025708 )
                 Winfwnx2: Able to load/unload ISCSI via restorenvram 
                 images on NICs
      Cause:
                 Prior to the change, the code was checking for the absence
                 of any one of the following directory entries to detect the 
                 absence of the ISCSI_BOOT both in the file and in NVRAM.
                 CODE_IMAGE_TYPE_ISCSI_BOOT,
                 CODE_IMAGE_TYPE_ISCSI_BOOT_CFG &
                 CODE_IMAGE_TYPE_ISCSI_BOOT_CPRG. 
                 The problem in doing this is that, it is possible that
                 one of the directory entry is missing in the NVRAM and
                 still has the ISCSI_BOOT support (say if 
                 CODE_IMAGE_TYPE_ISCSI_BOOT_CPRG is missing as in the bug
                 scenario) while the file that we are about to restore does
                 not have any/all of the above three directory entires. 
      Change:    
                 We now check for mis-matches on the individual directory 
                 entries and report only mis-matches and don't worry about
                 presence or absence state of the indivdual directory entries. 
      Impact:
                 ISCSI/IPMI directory entry mis-match with 
                 'upgrade/restorenvram' commands.    
                 
   5. Problem:   ( Cont00025622 )
                 winfwnx2 -all upgrade/restorenvram... gives bad/incorrect errors 
                 although successfully goes through
      Cause:
                 Prior to the change, the code was not checking for NVRAM size 
                 mismatch before the restore operation.
      Change:    
                 We now catch NVRAM/file size mismatch before we let the 
                 restore operation go through.
      Impact:
                 Use case scenarios around the bug.
                 
                 
Version 1.0.5 (June 28, 2006)
-------------------------------
     
   Fixes:
   =====
   1. Problem:   ( Cont00025487 )
                 "winfwnx2 -all upgrade -bc fwFile nvramImage" 
                 results in only 1 backup image for multiple NICs
      Cause:
                 This is a new enhancement.
      Change:    
                 We now dump with the MAC address appended at 
                 the end in case of multiple NICs getting upgraded.
      Impact:
                 Use case around the bug scenario.
                 
   2. Problem:   ( Cont00025383 )
                 Winfwnx2: restorenvram <image> gives 
                 "nvram checksum failed" on same model devices, 
                 on different model devices, it allows the restore
      Cause:
                 The variable which captures the return error code
                 was not getting initialized before moving on to the
                 other applicable NICs. 
      Change:    
                 We not only now filter out the irrelevant devices, but
                 also initialize the variable which captures the 
                 errorcode before moving on to the other applicable
                 NICs during the restorenvram command operation.
      Impact:
                 Use case around the bug scenario.    
                 
   3. Problem:   ( Cont00025412 )
                 winfwnx2: shouldn't be able to install pxe, iscsi, ipmi, ump 
                 if not orginally on card.  Only should be able to 
                 up/downgrade versions
      Cause:
                 Prior to the change, the code was not setup to capture
                 the install scenarios. 
      Change:    
                 We now allow only upgrades and not installs.
      Impact:
                 'Upgrade' & 'restorenvram' commands.                                
                 
                 
Version 1.0.4 (June 15, 2006)
-------------------------------
     
   Fixes:
   =====
   1. Problem:   ( Cont00025143 )
                 Winfwnx2: "exit" quits the program when only 
                 "q" should quit
      Cause:
                 "exit" command was not blocked.
      Change:    
                 We block it now.
      Impact:
                 Use case around the bug scenario.
                 
   2. Problem:   ( Cont00024861 )
                 Winfwnx2: Attempting to access an unsupported 
                 adapter causes "initialization failure"
      Cause:
                 We returned an error code of adapter not found
                 from the initialization routine. This was wrongly 
                 interpreted as initialization failure by the 
                 command processor.
      Change:    
                 We now exit with the appropriate error code/message.
      Impact:
                 Use case around the bug scenario.  
                 
   3. Problem:   ( Cont00025154 )
                 Winfwnx2: '-all' allows more than 'upgrade' and 
                 'restorenvram' commands
      Cause:
                 Prior to this change, all commands were allowed
                 to run with the "-all" option.
      Change:    
                 We now allow only upgrade and restorenvram commands
                 to work with "-all" option.
      Impact:
                 Use case around the bug scenario.    
                 
   4. Problem:   ( Cont00024603 )
                 WinFwnx2 - upgrading iscsi 1.3.1 & 1.3.2 
                 give incorrect versions
      Cause:
                 We were swapping the input/original buffer before
                 writing to NVRAM. This left the in-memory input
                 buffer in a corrupted state and so subsequent
                 ISCSI-boot check/upgrades were operating on 
                 an incorrect buffer information.
      Change:    
                 We now make a copy and operate on the copied
                 buffer before we write to the NVRAM a chunck
                 of information. This way, the original buffer
                 information integrity is preserved.
      Impact:
                 Use case around the bug scenario.   
                 
   5. Problem:   ( Cont00025029 )
                 WinFWnx2 1.0.3, xdiag 1.4.2: Unable to install ISCSI
      Cause:
                 The bug and the fix were inherited from the code
                 that is shared with xdiag.
      Change:    
                 The bug and the fix were inherited from the code
                 that is shared with xdiag.
      Impact:
                 Use case around the bug scenario.                                                            
   
   
Version 1.0.3 (May 21, 2006)
-------------------------------
     
   Fixes:
   =====
   1. Request:   ( Cont00024910 )
                 WinFwnx2 1.0.2 - "-w" command gives program error 
                 when should give command information
      Cause:
                 Prior to this fix, we reported improper command 
                 usage which doesn't seem wrong. But to be consistent
                 with WinFwUpg.exe, we now put up the command 
                 usage information if "-w" command was invoked 
                 without any parameter.
      Change:    
                 we now put up the command 
                 usage information if "-w" command was invoked 
                 without any parameter.
      Impact:
                 -w command behavior.
                 
   2. Request:   ( Cont00024858 )
                 WinFWnx2 1.0.2: No <savefile> parameter for 
                 "upgrade" gives no file exist error
      Cause:
                 Prior to this change, the code was assuming that
                 the last parameter was <savefile> and the second
                 last parameter was the upgrade <filename>. This 
                 is how it was documented in the command help 
                 information as well. With this logic, if the "upgrade" 
                 command was invoked as specified in the bug report, 
                 the code would take the "-bc" option for the upgrade 
                 <filename>. Hence it reported the the upgrade file
                 was missing. Although I wouldn't call this a bug, 
                 just to be consistent with WinFWUpg, I am addressing
                 this to match the WinFWUpg.exe behavior.
      Change:    
                 The code still assumes that the upgrade <filename> preceeds
                 the <savefile>. But enhanced the command line parameter
                 parsing mechanism to catch the case when the mandatory
                 upgrade <filename> and/or <savefile> parameters are missing.
      Impact:
                 "upgrade" command behavior.
                 
   3. Request:   ( Cont00024863 )
                 Need to Separate Instructions for FW Upgrade Utility 
                 Usage from Release Notes to Separate Readme.txt file
      Cause:
                 Prior to the fix, the readme.txt information was part 
                 of release.txt.
      Change:    
                 Extracted the readme information from releast.txt to
                 a separate readme.txt file.
      Impact:
                 release.txt/readme.txt.    
                 
   4. Request:   ( Cont00024722 )
                 WinFWinX2 - using wrong FW file gives wrong error code
      Cause:
                 Prior to this, the code was not setup right to capture 
                 incorrect firmware files. 
      Change:    
                 The tool shares some implementation with XDIAG. Recently
                 XDIAG code was updated to detect/capture such 
                 incorrect firmware file usages with the "upgrade" command.
                 The tool inherits the fixes from XDIAG. With the fix,
                 the rool now reports Code 26 which says "Incorrect NVRAM 
                 file format". This errocode seems more logical than 
                 errorcode "35" that was mentioned in the bug report.
      Impact:
                 upgrade command.         
                 
   5. Request:   ( Cont00024797 )
                 WinFWnx2: upload bad ump firmware exits program
      Cause:
                 Prior to this, the code was not setup right to capture 
                 incorrect firmware files. 
      Change:    
                 The tool shares some implementation with XDIAG. Recently
                 XDIAG code was updated to detect/capture such 
                 incorrect firmware file usages with the "upgrade" command.
                 The tool inherits the fixes from XDIAG. With the fix,
                 the rool now reports Code 26 which says "Incorrect NVRAM 
                 file format". 
      Impact:
                 upgrade command.  
                 
   6. Request:   ( Cont00024856 )
                 WinFWnx2: using corrupt MBA FW upgrades fine with 
                 no apparent errors in chksum
      Cause:
                 Prior to this, the code was not setup right to capture 
                 incorrect firmware files. 
      Change:    
                 The tool shares some implementation with XDIAG. Recently
                 XDIAG code was updated to detect/capture such 
                 incorrect firmware file usages with the "upgrade" command.
                 The tool inherits the fixes from XDIAG. With the fix,
                 the rool now reports Code 26 which says "Incorrect NVRAM 
                 file format" when tried the upgrade command on the 
                 firmware file that was attached with bug report. 
      Impact:
                 upgrade command.    
                 
   7. Request:   ( Cont00024745 )
                 Unclear message about chip reset is displayed 
                 twice in a row after flashing.
      Cause:
                 Prior to this, a redundant message was displayed. 
      Change:    
                 This is a shared code with xdiag, and it has been updated 
                 to eliminate the redundant message. Also, a different 
                 message is used for the FWUpg utility using 
                 #ifdef to separate it from the xdiag message. 
      Impact:
                 upgrade command.                                                                        
                 
                 
Version 1.0.2 (May 15, 2006)
-------------------------------
     
   Enhancement:
   ===========
   1.  Change:
                 Improved the log command to capture all
                 command runs as well as their output.
       Impact:
                 All commands with logging turned on.
                
   2.  Change:
                 Made some changes to speed up the response time
                 on some of the commands by reading more than 
                 the requested bytes (caching it until the first 
                 write operation) to save time on subsequent
                 read operations.
       Impact:
                 All read/write operations/commands.
                 
   Fixes:
   =====
   1. Request:   ( Cont00024747 )
                 "reset" command is allowed, undocumented 
                 and does not function.
      Cause:
                 The reset command was required to trigger a driver
                 reset at the end of wol (-w) command as there was some
                 code sharing with DOS. 
      Change:    
                 Removed the undocumented 'reset' command from
                 the list of allowed commands.
      Impact:
                 -w command behavior.
                 
   2. Request:   ( Cont00024720 )
                 Command line switches are order specific.
      Cause:
                 We leveraged most of the validation code with
                 DOS as there is some code sharing between DOS and
                 Windows firmware upgrade tool.
      Change:    
                 We now do additional validation in the Windows 
                 firmware upgrade tool. We also now allow switch -F and
                 other options as part of the upgrade command. But,
                 we are still limited to how much we can allow the 
                 shuffling of the command line switches. The command
                 still assumes that the last parameter of the upgrade
                 command is the <savefile> and the second last 
                 parameter to be the upgrade <filename>.
      Impact:
                 upgrade command.
                 
   3. Request:   ( Cont00024719 )
                 Error message given when bootcode image name or 
                 path is incorrect should be changed.
      Cause:
                 Tried to leverage on the existing error codes/strings.
      Change:    
                 Added few additional error codes/strings to put up a
                 more meaningful error message to the user.
      Impact:
                 upgrade/restorenvram commands.
                 
   4. Request:   ( Cont00024749 )
                 "verify" option for "restorenvram" command writes to adapter.
      Cause:
                 One of the earlier version of MRD had the verify 
                 option specified. There was a typo in the implementation
                 which lead to the "restorenvram" command writing 
                 stuff to NVRAM when "verify" option was used.
      Change:    
                 Fixed the typo in the code and also removed the "verify"
                 option from the "restorenvram" command to match MRD 
                 specification.
      Impact:
                 restorenvram command help.
                 
   4. Request:   ( Cont00024794 )
                 FW Upgrade Utility for Teton Does Not Default to an 
                 Adapter When Multiple Adapters are Present
      Cause:
                 The code was not setup to make the zeroth device as 
                 the default selection when more than one supported 
                 NIC is present on the system.
      Change:    
                 Selecting the zeroth device as default in all the 
                 scenarios.
      Impact:
                 Tool startup.
                 

Version 1.0.1 (April 20, 2006)
-------------------------------
     
     - First release.
     - Need BMAPI version 7.5.6.0 or above.
     - Need driver bxvbdx.sys version 2.8.3 or above.

 in command
               line mode.
      Change:
               The FwUpg tool can process the '-l2t' option in command line
               mode and complete the operation.
      Impact:
               'upgrade -l2t' command on BCM57710 NIC in command line mode.


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

   Fixes:
   =====
   1. Problem: 
               With correct MBA file, command line nvram upgrade call
			   with "-all" option would fail.
      Cause:
               The file/device MBA filtering was not done correctly.
      Change:
               Seperated the logic of validating the MBA file versus
			   validating the file against the device.
      Impact:
               MBA upgrade on NX2 family of devices.

   2. Problem: CQ41050
               The FwUpg tool allows WOL enabling in port 3 & 4 of the
               BCM5709 4-port adapter.
      Cause:
               The FwUpg tool did not check the condition for WOL enabling
               of the port.
      Change:
               The FwUpg tool will will check the condition before enabling
               WOL capability of the port.
      Impact:
               Enabling WOL capability of the BCM5709 4-port NIC.


Version 1.0.62 (May 23, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ41425
               Added support to upgrade iSCSI boot with IPv6.
      Change:
               Added support to upgrade iSCSI boot with IPv6.
      Impact:
               'upgrade -ib|-ib_ipv6|-ib_ipv4n6' command.


Version 1.0.61 (May 19, 2009)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ39424
               Added support to add iSCSI bootcode for a selected
               BCM57710 NIC.
      Change:
               Added support to add iSCSI bootcode for a selected
               BCM57710 NIC.
      Impact:
               'prg -ib' command for a selected BCM57710 NIC.

   2. Request: CQ39660
               Added and update UEFI driver from MBA binary file.
      Change:
               The requested feature is implemented.
      Impact:
               'upgrade -mba' command.

   3. Request: CQ39988
               Added the ability to display version for UEFI driver
               and FCODE components.
      Change:
               The requested feature is implemented.
      Impact:
               'dir' command.

   Fixes:
   =====
   1. Problem: CQ39074
               The NCSI upgrade failed with segmentation fault for BCM5709
               on PPC64 system.
      Cause:
               The 64-bit pointer was not handled correctly when upgrading
               the NCSI firmware.
      Change:
               The 64-bit pointer is handled correctly when upgrading
               the NCSI firmware.
      Impact:
               'upgrade -ncsi' command for NCSI firmware for BCM5709 adapters
               on the PPC64 system.

   2. Problem: CQ39075
               The CRC check failed for BCM5709 on PPC64 system.
      Cause:
               The Big-Endian variable was not handled correctly when
               processing the 'crc' command.
      Change:
               The Big-Endian variable is now handle correctly when
               processing the 'crc' command.
      Impact:
               'crc' command for BCM5709 on PPC64 system.

   3. Problem: CQ40134
               Failed to upgrade to new NCSI binary file v2.0 or later.
      Cause:
               The new NCSI binary file has a different format that was
               not processed correctly by FwUpg tool.
      Change:
               The FwUpg tool will process the old and new format of the
               NCSI binary file correctly.
      Impact:
               'upgrade -ncsi' command for BCM5709 NIC.

   4. Problem: CQ37882
               The FwUpg tool downgrded IPMI v1.05 for BCM5708 without "-F"
               option.
      Cause:
               The IPMI v1.05 binary file used a different header and caused
               the version validation to fail.
      Change:
               The FwUpg tool will detect the different header and make an
               adjustment to retrieve the version.
      Impact:
               "upgrade -ipmi" that uses IPMI v1.05 for BCM5708 NIC.

   5. Problem: CQ40998
               The BACS failed to display the external PHY firmware version
               after using FwUpg tool to upgrade the bootcode.
      Cause:
               The upgrade function did not work correctly and corrupt the
               bootcode.
      Change:
               The FwUpg tool will upgrade the bootcode correctly and the
               external PHY firmware version can be returned correctly.
      Impact:
               "upgrade -bc" command for BCM57710 NIC.

   6. Problem: CQ40999
               The FwUpg tool failed to display the external PHY firmware
               version for adapter with BCM8727 PHY.
      Cause:
               The FwUpg tool did not recognize the BCM8727 PHY.
      Change:
               The FwUpg tool can now recognize the BCM8727 PHY and display
               the external PHY firmware version correctly.
      Impact:
               "phy -ver" command on adapter with BCM8727 PHY.


Version 1.0.60 (Mar 12, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ39853
               The 'upgrade -mba' caused segmentation fault when upgrading
               the combined MBA firmware file in 64-bit Linux system for
               BCM57710/57711/57712 adapters.
      Cause:
               The 64-bit pointer was not handled correctly when upgrading
               the combined MBA firmware.
      Change:
               The 64-bit pointer is handled correctly when upgrading
               the combined MBA firmware.
      Impact:
               'upgrade -mba' command for combined MBA firmware for
               BCM57710/57711/57712 adapters.


Version 1.0.59 (Feb 18, 2009)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ39013
               The FWUPG tool did not check the PHY firmware image
               file against the PHY device to be upgraded.
      Cause:
               The FWUPG tool did not check the PHY firmware image
               file against the PHY device to be upgraded.
      Change:
               The FWUPG tool will check the header in the PHY firmware
               image file against the PHY device before upgrading
               the PHY firmware.
      Impact:
               'phy -upg' command for all adapters.

    Note: New PHY firmware image file with header has to be used.


Version 1.0.58 (Dec 19, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ28499
               Added support to the old format of M-Key/U-Key
               block checksum.
      Change:
               Added support to the old format of M-Key/U-Key
               block checksum.
      Impact:
               'crc' and 'restore' command for BCM5706-based
               adapters with old format of M-Key/U-Key.


Version 1.0.57 (Dec 15, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request:
               FWUPG will validate the BMAPI and driver versions for
               the "phy" command.
      Change:
               FWUPG will validate the BMAPI and driver versions for
               the "phy" command.
      Impact:
               The 'phy' command.  The BMAPI has to be v7.15.8 or later.
               The VBD driver has to be v4.8.9 or later.


Version 1.0.56 (Dec 02, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ36353
               Added support to upgrade external PHY firmware
               for BCM57710/57711.
      Change:
               Added support to upgrade external PHY firmware
               for BCM57710/57711.
      Impact:
               New 'phy' command to upgrade external PHY firmware.


Version 1.0.55 (Oct 08, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ35469/CQ37498
               Added support to program iSCSI firmware into the
               NVRAM for some selected adapters.
      Change:
               Added support to program iSCSI firmware into the
               NVRAM for some selected adapters.
      Impact:
               'prg -ib' command for some selected adapters.

   Fixes:
   =====
   1. Problem: CQ37719
               The FWUPG tool displayed an "Invalid checksum in RV field"
               error message when executing the "cfg -wol 1" command.
      Cause:
               The checksum of VPD-R was not set correctly and the error
               message was displayed when the checksum error was detected.
      Change:
               The checksum of VPD-R is set correctly.  There will be no
               checksum error when executing the "cfg -wol 1" command.
      Impact:
               'cfg' command for all adapters.

   2. Problem: CQ37734
               The FWUPG tool did not display the iSCSI boot version string
               correctly in the PPC64 machine.
      Cause:
               The FWUPG tool did not handle the iSCSI boot version string
               correctly in the PPC64 machine.
      Change:
               The FWUPG tool handles the iSCSI boot version string correctly
               in the PPC64 machine now.
      Impact:
               'dir' command to display iSCSI boot version for all adapters.

   3. Problem: CQ36701
               The FWUPG tool did not check the version of I_B_CPRG firmware
               before upgrading it.
      Cause:
               The FWUPG tool did not check the version of I_B_CPRG firmware
               before upgrading it.
      Change:
               The FWUPG tool will check the version of I_B_CPRG firmware
               before upgrading it.
      Impact:
               'upgrade -ib -c -p' command for BCM57710 adapters.


Version 1.0.54 (Oct 03, 2008)
---------------------------------

   Enhancements:
   =============
   1. Request: CQ36354
               Added support to upgrade L2 firmware for BCM57710.
      Change:
               Added support to upgrade L2 firmware for BCM57710.
      Impact:
               BCM57710-based adapters.

   2. Request: CQ37091
               Remove support for upgrading IPMI/UMP for BCM57710.
      Change:
               Remove support for upgrading IPMI/UMP for BCM57710.
      Impact:
               BCM57710-based adapter.

   Fixes:
   =====
   1. Problem: CQ37255
               The FWUPG tool displayed garbage value with 'cfg' command
               without any parameter.
      Cause:
               The FWUPG tool did not check for this error condition.
      Change:
               The FWUPG tool checks for this error condition and will
               display the correct error message.
      Impact:
               'cfg' command for all adapters.

   2. Problem: CQ36967
               The FWUPG tool return wrong exit code when downgrading
               firmware without '-F' option for BCM57710.
      Cause:
               The FWUPG tool did not return the exit code correctly
               when detecting this error condition.
      Change:
               The FWUPG tool will return the correct exit code when
               detecting this error condition.
      Impact:
               'upgrade' command for all adapters.


Version 1.0.53 (Aug 01, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem:
               The "upgrade -ib -p" command does not work in the
               command line mode.
      Cause:
               The "upgrade -ib -p" command was not correctly
               processed in the command line mode.
      Change:
               The "upgrade -ib -p" command is now processed
               correctly in the command line mode.
      Impact:
               The "upgrade -ib" command in command line mode
               for all Network NICs.


Version 1.0.52 (Jul 29, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ36543
               The "upgrade -ib" command does not upgrade the iSCSI
               Configration Program from the iSCSI image file.
      Cause:
               The "upgrade -ib" command was originally designed to
               upgrade the iSCSI boot code only.
      Change:
               The "upgrade -ib" command will have additional options
               "-c" and "-p" to upgrade the iSCSI Configuration and
               the iSCSI Configuration Program if they exist.
      Impact:
               The "upgrade -ib" command for all Network adapters.


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

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


Version 1.0.50 (Jul 08, 2008)
---------------------------------

   Fixes:
   =====
   1. Problem: CQ36233
               The "upgrade -bc" command does no
