****************************************************************
| |
| Tape LTO 6 firmware update |
| |
| |
| (C) Copyright International Business Machines Corporation |
| 2000-2012 . All rights reserved. |
| |
| US Government Users Restricted Rights -- Use, duplication |
| or disclosure restricted by GSA ADP Schedule Contract with |
| IBM Corp. |
| |
| Note: Before using this information and the product it |
| supports, read the general information under "NOTICES AND |
| TRADEMARKS" in this document. |
| |
| Updated: 10/29/2012 |
| |
****************************************************************

Change History

ver 1.0

Initial Release of LTO 6 firmware update.
This firmware update will change the firmware of your LTO 6 tape drive to the latest
available, unless it is already at the latest level.

- IBM HH LTO 6 SAS drive (35P0994) @ C9T5

ibm_fw_tape_lto6-1_0_linux_32-64_chg

_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD31H
Package Build Date : 03/14/2013
Package Version : 2.05

FPGA component information:
CPU Board FPGA Version : 72.3.9.0
Memory Expansion Board FPGA Version : 68.3.5.0

Iflash Version : 1.12.22
_______________________________________________________________________________



Problem(s) Fixed:
-

Enhancements:
- Updated documentation and flash delivery package.

Limitations:
-

Dependencies:

_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD31G
Package Build Date : 03/07/2013
Package Version : 2.05

FPGA component information:
CPU Board FPGA Version : 72.3.9.0
Memory Expansion Board FPGA Version : 68.3.5.0

Iflash Version : 1.12.20
_______________________________________________________________________________


Problem(s) Fixed:
- Corrects system behavior for IMM force update to match expected
behavior

Enhancements:
-

Limitations:
-

Dependencies:

_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD31E
Package Build Date : 11/09/2012
Package Version : 2.04

FPGA component information:
CPU Board FPGA Version : 72.3.7.0
Memory Expansion Board FPGA Version : 68.3.5.0

Iflash Version : 1.12.20
_______________________________________________________________________________


Problem(s) Fixed:
-

Enhancements:
- Updated documentation and flash delivery package.

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD31A
Package Build Date : 05/16/2012
Package Version : 2.04

FPGA component information:
CPU Board FPGA Version : 72.3.7.0
Memory Expansion Board FPGA Version : 68.3.5.0

Iflash Version : 1.12.16
_______________________________________________________________________________


Problem(s) Fixed:
- Fixed an issue with MAX5 that would result in DSA IMM I2C test
failures when certain DIMMs are installed.

Enhancements:
-

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD30U
Package Build Date : 03/29/2012
Package Version : 2.04

FPGA component information:
CPU Board FPGA Version : 72.3.6.0
Memory Expansion Board FPGA Version : 68.3.4.0

Iflash Version : 1.12.16
_______________________________________________________________________________


Problem(s) Fixed:
-

Enhancements:
- Updated documentation and flash delivery package.

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD30R
Package Build Date : 02/01/2012
Package Version : 2.03

FPGA component information:
CPU Board FPGA Version : 72.3.6.0
Memory Expansion Board FPGA Version : 68.3.4.0

Iflash Version : 1.12.13
_______________________________________________________________________________


Problem(s) Fixed:
-

Enhancements:
- Updated documentation and flash delivery package.

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD30Q
Package Build Date : 12/09/2011
Package Version : 2.03

FPGA component information:
CPU Board FPGA Version : 72.3.6.0
Memory Expansion Board FPGA Version : 68.3.4.0

Iflash Version : 1.12.12
_______________________________________________________________________________

Problem(s) Fixed:
- Fixed an issue with 2-node HX5 only, which can cause powercycling
and log entries such as:
Group 4, (processor 1-2) (Critical Int CPU) bus uncorrectable error
Processor 1, interconnect (CPU 1 Int Link) critical
PCI express bus 0, (Planar PCIe Err) bus uncorrectable error

Enhancements:
- Updated flash delivery package.

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD30O
Package Build Date : 09/19/2011
Package Version : 2.02

FPGA component information:
CPU Board FPGA Version : 72.3.5.0
Memory Expansion Board FPGA Version : 68.3.4.0

Iflash Version : 1.12.11
_______________________________________________________________________________

Problem(s) Fixed:
-

Enhancements:
- Updated documentation and flash delivery package.

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD30L
Package Build Date : 06/12/2011
Package Version : 2.01

FPGA component information:
CPU Board FPGA Version : 72.3.5.0
Memory Expansion Board FPGA Version : 68.3.4.0

Iflash Version : 1.12.07
_______________________________________________________________________________

Problem(s) Fixed:
-

Enhancements:
- Support added for new machine types

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD30J
Package Build Date : 04/12/2011
Package Version : 2.00

FPGA component information:
CPU Board FPGA Version : 72.3.5.0
Memory Expansion Board FPGA Version : 68.3.4.0

Iflash Version : 1.12.05
_______________________________________________________________________________

Problem(s) Fixed:
- Fixed erroneous memory over-temperature errors on memory expansion
- Fixed issue with ABR and power-cycling

Enhancements:
- Support added for new machine types

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD22M
Package Build Date : 11/21/2010
Package Version : 1.02

FPGA component information:
CPU Board FPGA : Version 72.2.6.0
Memory Expansion Board FPGA : Version 68.2.34.0

Iflash : Version 1.11.02
_______________________________________________________________________________

Problem(s) Fixed:
- Fixed a 'Sub-chassis 1, voltage (MEU 12V down) non-recoverable'
fault if powered off then quickly back on through the AMM

- Fixed a failure to read DIMM temperatures, and error handling,
when a single CPU is installed

Enhancements:
-

Limitations:
-

Dependencies:


_______________________________________________________________________________
IBM HX5/MAX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD22K
Package Build Date : 10/08/2010
Package Version : 1.01

FPGA component information:
CPU Board FPGA : Version 72.02.04.00
Memory Expansion Board FPGA : Version 68.02.34.00

Iflash : Version 1.10.11
_______________________________________________________________________________

Problem(s) Fixed:
- Fixed Wake on LAN issue, failure to wake from an expansion card
- Fixed issue with fatal error handling (e.g. DIMMs not being disabled)

Enhancements:
- Support added for MAX5 memory expansion unit

Limitations:
-

Dependencies:
-


_______________________________________________________________________________
IBM HX5 FPGA Flash Update Package
Change History

Packaging Information:
Package Build ID : HIUD16L
Package Build Date : 06/24/2010
Package Version : 1.00

FPGA component information:
CPU Board FPGA : Version 72.01.02.00

Iflash : Version 1.10.05
_______________________________________________________________________________

Initial Release

ibm_fw_fpga_hiud31h-2_05_anyos_chg

Dynamic System Analysis (DSA) Preboot Change History

Version 9.32, Build ID DSYTA9C
o New System Support:
o New Operating System support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
Refer to readme
o Functional change:
o Dependencies:
o Special usage:
- IMMv1 & IMMv2 system 2013 R1 LFC

Version 9.27, Build ID DSYTA7
o New System Support:
o New Operating System support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
Refer to readme
o Functional change:
o Dependencies:
o Special usage:
- IMMv1 system 2012 4Q-LFC

Version 9.26, Build ID DSYTA6G
o New System Support:
o New Operating System support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
DSA Performance Optimization
o Limitations:
Refer to readme
o Functional change:
o Dependencies:
o Special usage:
- 2012 ToolsCenter 12C

Version 9.21, Build ID DSYTA1U
o New System Support:
o New Operating System support:
o New server options support:
o Problem(s) Fixed:
1.Recovered LSI Rawdata: "MegaCli -FwTermLog -Dsply -aALL"
o Enhancement:
o Limitations:
Refer to readme
o Functional change:
o Dependencies:
o Special usage:
- 2012 ToolsCenter 12B Plus

Version 9.20, Build ID DSYTA0R
o New System Support:
x3530 M4 (7160)
x3630 M4 (7158)
x3750 M4 (8722, 8733)
HS23E (8038, 8039)
Flex System x220 Compute Node (7906, 2585)
o New Operating System support:
vSphere Hypervisor 5.0u1 with IBM customization
o New server options support:
o Problem(s) Fixed:
1. PMR 05819,YL2,760
An error occured during the execution of DSA on Windows,
DSA exits with an error at the eventlog plugin.

o Enhancement:
o Limitations:
Refer to readme
o Functional change:
1. Add HW remote presence key collection for High volume systems.
o Dependencies:
o Special usage:
- 2012 ToolsCenter 12B

Version 9.07, Build ID DSYT9CA
o New System Support:
x3750 M4 (8722, 8733)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 9.06, Build ID DSYT9BC
o New System Support:
Flex System x220 Compute Node (7906)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 9.05, Build ID DSYT9AA
o New System Support:
x3630 M4 (7158)
x3530 M4 (7160)
x3100 M4 Refresh1 (2582)
x3250 M4 Refresh1 (2583)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 9.04, Build ID DSYT99E
o New System Support:
Flex System x240 Compute Node (8737, 8738, 7863)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:

Version 9.03, Build ID DSYT98I
o New System Support:
HS23E (8038, 8039)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:

Version 9.02, Build ID DSYT97C
o New System Support:
iDataPlex dx360 M4 server/2U chassis (7912/7913)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Functional change:

Version 9.01, Build ID DSYT96D
o New System Support:
x3500 M4 (7383)
x3550 M4 (7914)
x3650 M4 (7915)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:
o Special usage:

Version 9.00, Build ID DSYT95W
o New System Support:
BladeCenter HS23 (7875)
BladeCenter HX5 (7873, 1910)
Flex System x240 Compute Node (8737, 8738, 7863)
Flex System Manager Node (8735)
x3500 M4 (7383)
x3550 M4 (7914)
x3630 M4 (7158)
x3650 M4 (7915)
x3690 X5 (7192, 7147)
x3850 X5 / x3950 X5 (7143, 7191)
o New server options support:
o Problem(s) Fixed:
1. PMR 24817,8QG,000, PMR 30680,499,000
After kicking off DSA on one of the management nodes (x3650 M2) of
SONAS 1.2(RHEL5 based), the node became unresponsive and dropped
out of the cluster.

2. PMR 53575,000,834, PMR 05961,YL4,760
After running DSA, when using linux dump command on a DDS5 usb internal
tape drive attached in x3650M2 backup speed becomes very slowly or failed.

3. PMR 26905,095,866
Running DSA 4.0 as well as DSA 3.4 on x3850 X5 the server is freezing,
users have to reboot the server.

4. DSA 4.00 and previous version segmentation fault issue

5. PMR 05148,6M4,760
DSA v4 unexpectedly create IMM virtual switch

6. PMR 15086,OTH,760
DSA 9.00 with --no-imm-lan option does not work correctly
on RHEL5.3. The USB port state is changed during the execution of DSA.

o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
1. Add GUI and CLI menu for Features on Demand (FoD) Activation Key Management
o Special usage:

Version 4.02, Build ID DSYT92I
o New System Support:
iDataPlex Direct Water Cooled dx360 M4 server
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 4.01, Build ID DSYT92H
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:
- 2011 4Q lifecycle

Version 4.00, Build ID DSYT91S
o New System Support:
o New server options support:
o Problem(s) Fixed:
1. PMR 15065,OTR,760
On Unisys ES7000 or x3850 X5, the Memory Card number with failed DIMM
can not be reported in IPMI Eventlog if the Memory Card is bigger than 4.

o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
1. Added > 1TB memory test support
o Special usage:
- 2011 ToolsCenter 11D

Version 3.48, Build ID DSYT89PUS
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:
- 2011 3Q lifecycle

Version 3.47, Build ID DSYT89LUS
o New System Support:
x3100 M4 (2582)
x3250 M4 (2583)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 3.46, Build ID DSYT89GUS
o New System Support:
System x iDataPlex dx360 M3 (6391)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 3.45, Build ID DSYT89EUS
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:
- x3850 X5 / x3950 X5 (7143, 7191) EXA scaling

Version 3.43, Build ID DSYT87HUS
o New System Support:
BladeCenter HX5 (7873,1910)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 3.43, Build ID DSYT87FUS
o New System Support:
x3850 X5 / x3950 X5 (7143, 7191)
x3690 X5 (7192, 7147)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 3.40, Build ID DSYT85T
o New System Support:
BladeCenter HS22 (1911)
x3650 M3 (5454)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 3.30, Build ID DSYT80S
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
1. Correct a problem with LSI MegaRAID reporting for IBM Service
o Special usage:

Version 3.20, Build ID DSYT75X
o New System Support:
x3630 M3 (7377)
x3690 X5 (7148, 7149)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
- If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831
installed, you will need one of the following:
- uEFI GYE133A or greater for x3200 M3 and x3250 M3
- uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3
- uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3
o Functional change:
1. Add LSI Hard Disk Drive (HDD) diagnostic back for both the onboard SAS chip and ServeRAID
o Special usage:

Verion 3.20, Build ID DSYT75U
o New System Support:
x3755 M3 (7164)
o New server options support:
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Verion 3.10, Build ID DSYT70X
o New System Support:
x3400 M3(7378, 7379)
x3500 M3(7380)
x3550 M3 (7944, 4254)
x3620 M3 (7376)
x3650 M3 (7945, 4255)
x3690 X5 (7148, 7149)
x3850 X5 Standard Single-node and Multi-node models(7145, 7146)
x3950 X5 Specially configured Database Engine models (7145, 7146)
iDataplex dx360 M3 (6391)
HS22V (7871,1949)
HX5 (7872, 1909)
o New server options support:
Emulex 10Gb/s Fibre Channel over Ethernet Dual Channel Converged Network Adapter(LP21002)
Emulex PCI-e Gen2.0 Dual Port 10Gb NIC (49Y4250)
6Gb SSD HBA (46M0912)
6Gb SAS HBA (46M0907)
Intel QuadPort Ethernet Server Adapter
CFFh Intel Ethernet Daughter Card
FCoE SRIOV Key (Ethernet)
iSCSI Key (Ethernet)
Secure Encryption HBA for 8Gb FC eHBA Emulex
Brocade 4Gb FC HBA(59Y1992, 59Y1998)
Emulex 2-Port 10Gb Multi-function IO Adapter (CFFh) (49Y4235)
Brocade 10Gb Dual-port CNA (42C1820)
Broadcom NetXtreme II 1000 Express Quad port Ethernet Adapter (49Y4220)
Broadcom NetXtreme II 1000 Express Dual Port Ethernet Adapter (42C1780)
MAX5 Memory Expansion Unit
o Problem(s) Fixed:
o Enhancement:
o Limitations:
o Dependencies:
o Functional change:
1. Add a new option --disable-imm-lan to take down IMM USB Over Lan
interface when DSA complete.
2. Added ServeRAID data collection
o Limitations:
- The following function has been temporarily removed from DSA
Preboot for both the onboard SAS chip and ServeRAID:
- LSI Hard Disk Drive (HDD) diagnostic
o Dependencies:
- If you have ServeRAID (M1015) SAS/SATA Controller, 46M0831
installed, you will need one of the following:
- uEFI GYE133A or greater for x3200 M3 and x3250 M3
- uEFI Y4E145B or greater for x3400 M2, x3400 M3, x3500 M2 and x3500 M3
- uEFI D6E145C or greater for x3550 M2, x3550 M3, x3650 M2 and x3650 M3
o Special usage:

Version 3.02.56, Build ID DSYT56e
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
- The following systems are supported when BoMC downloads the
corresponding system enablement pack:
HS22V (7871,1949)
x3550 M3 (7944,4254)
x3650 M3 (7945,4255)
x3400 M3 (7378,7379)
x3500 M3 (7839)
dx360 M3 (6391)
o Limitations:
- No HDD diagnostics available
- To ensure quality and stability of the DSA code, we have
reverted some display functionality of RAID information to
what was shown in previous versions of DSA. This affects RAID
display on the following adapters:
Megaraid 8480
Serveraid MR10i
Serveraid MR10is
Serveraid MR10m
Serveraid MR10k
Serveraid M1015
Serveraid M5014
Serveraid M5015
On these adapters, the RAID information is generated from the
output of separate command line tools and the format may not
match other output in DSA. Dependencies:
o Dependencies:
o Functional change:
o Special usage:

Version 3.00, Build ID: DSYT55a
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
- Added support for Machine Types 7327, 7328, 4251, 4252, 4261
o Limitations:
- No HDD diagnostics available
o Dependencies:
o Functional change:
o Special usage:

Version 1.16, Y4YT19AUS
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
- Added support for Machine Types 7839, 7836, 7837
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 1.15, TMYT20AUS
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
- Added support for Machine Types 7321, 6380, 7323
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 1.14, D6YT37AUS
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
- Added support for Machine Types 7946, 4198, 7947, 4199
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 1.13, P9YT48AUS
o New System Support:
o New server options support:
o Problem(s) Fixed:
o Enhancement:
- Added support for Machine Types 7870, 1936, 7809
o Limitations:
o Dependencies:
o Functional change:
o Special usage:

Version 1.00
- Initial release

(C) Copyright International Business Machines Corporation 2008 - 2012.
All rights reserved.
ibm_fw_dsa_dsyta9c-9_32_anyos_anycpu_chg

IBM System HX5/MAX5 uEFI Flash Update
Version 1.79 (BuildID HIE179A)
Change History

Version 1.79 - BuildID: HIE179A
-----------------------------------------------------
Problem(s) Fixed:

Enhancements:
- Add notification and recovery option when UEFI detects GPT corruption during POST. Please refer to RETAIN Tip H21166 for details.
- Add IPV6 PXE support.
- Optimized Memory Single Bit Thresholds.

Limitations:

Dependencies:
- IMM YUOOF7A (Version 1.40) or later is required.
- FPGA HIUD31H (Version 2.05) or later is required.


Version 1.77 - BuildID: HIE177A
-----------------------------------------------------
Problem(s) Fixed:
- Limits C-states to avoid CPU VRD failures. Please refer to RETAIN Tip H207008 at the following link: http://www.ibm.com/systems/support/supportsite.wss/docdisplay?brandind=5000008&lndocid=MIGR-5091926
- Fix incorrect memory size report in F1 setup/OS when unusable DIMM was detected and isolated.
- Fix disk data corruption with LUNS greater than 2TB for QLogic HBA Cards.
- Fix F1 setup storage option missing issue for QLogic HBA card.
- Fix initial values selected in the "Custom" operating mode are not the same as the previously selected preset operating mode.

Enhancements:
- Add _WDG ACPI method support for SRIOV.
- Add PCI-SIG resizable BAR capability support.
- Support 16GB or higher quad-ranks DIMM with restricted memory speed on MAX5.

Limitations:

Dependencies:
- IMM YUOOE9B (Version 1.35) or later is required.
- FPGA HIUD31E (Version 2.04) or later is required.


Version 1.75 - BuildID: HIE175B
---------------------------------------
Problem(s) Fixed:
- Resolve OS or POST hang following a corrected machine check event.
- Don't enable secondary video adapters in pre-boot environment
to prevent Legacy VGA I/O conflict in Windows.
- Fix boot fail when using WOL.
- Addressed Intel errata BP47 and BA131 with title
"A Load May Appear to be Ordered Before an Earlier Locked Instruction".

Enhancements:
- Add Setup Option to select MM Config Base (1GB/2GB(default)/3GB).
- Optimize PCI Resource Allocation for Onboard Devices to make more
Legacy I/O and MMIO space available to Adapters.
- Add setup option to set VLAN ID.
- Add infinite boot loop option in F1 SETUP for legacy boot.
- Update microcode for Intel Xeon E7 series processors to M05206F2_00000036.
- Update microcode for Intel Xeon 7500 series processors to M05206E6_00000009.

Limitations:

Dependencies:
- IMM YUOOE3C (Version 1.33) or later is required.
- FPGA HIUD31A (Version 2.04) or later is required.


Version 1.73 - BuildID: HIE173B
---------------------------------------
Problem(s) Fixed:

- Fix uEFI.UEFIRomDisable setting for secondary nodes.
- Fix for BOFM MAC not applied to virtual devices, or when in BPE4.
- Reset 3x Boot fail count upon any successful boot with user settings.
- Fix PCI Slot usage for secondary nodes in SMBIOS Type 9 structures.
- Make PCI Slot instance unique across nodes in SMBIOS Type 9 structures.
- Restrict Legacy VGA to add-in video adapters behind Legacy I/O Hub.
- Select first scanned from available add-in video adapters as Legacy VGA.
- Fix VMWare Boot fail after installing it in UEFI mode.
- Don't load Setup Defaults upon BPE4 configuration change.
- Fix Processor Details in UEFI F1 Setup for CPUs with non-zero PBSP.
- Fix planar MAC in AMM VPD, when BPE4 is attached.
- Fix system hang due to unhandled correctable SMI link event.

Enhancements:

- Differentiate between QPI Link Width Reduction to Half vs Quarter Width.
- Add support for Netlist DIMMs in SMBIOS Type 17 structures.
- Add support for more than 255 PFs in Legacy MPS table.
- Update microcode for Intel Xeon E7 series processors to M05206F2_00000034.
- Add Setup Option to make 3x Boot fail configurable as Nx Boot fail.
- Sync uEFI.RomOrder with the available devices in hardware configuration.

Limitations:

Dependencies:

- IMM YUOOD4G (Version 1.32) or later is required.
- FPGA HIUD30R (Version 2.03) or later is required.


Version 1.70 - BuildID: HIE170B
---------------------------------------
Problem(s) Fixed:

- Fix false Three 3x Boot fail following replacement of battery.
- Fix IMM MAC Address display in F1 IMM page.
- Fix uEFI.UEFIRomDisable setting for 2nd node.

Enhancements:

- Add BOFM 4.2 support.
- Don't check for Legacy Option ROM Errors, when it is Disabled.
- Update to SMBIOS 2.7 for extended DIMM size and Address space support.
- F1 Network page update: categorized & consistent MAC notation.
- Support Directory Assisted Snoop with Intel Xeon E7 series processors.
- Describe I/O Affinity based on Setup Option of Non-Pooled (default) vs Pooled.
- Add Setup Option to enable MMIO allocation above 4GB for large configuration.
- Include MD5 checksum into firmware update package to prevent corrupted update.
- Update microcode for Intel Xeon E7 series processors to M05206F2_00000032.
- Improve Software Algorithms for Memory Robustness.
- Limit boot attempts, when no bootable devices are found.
- Add support for more than 2.2 TB disks with GPT.
- Add Setup Option to disable the native control of PCI Express features from OS.

Limitations:

Dependencies:

- IMM YUOOC7E (Version 1.30) or later is required.
- FPGA HIUD30O (Version 2.02) or later is required.


Version 1.60 - BuildID: HIE160B
---------------------------------------
IMPORTANT: IMM firmware YUOOB7C (Version 1.28) and FPGA firmware HIUD30L (Version
2.01) or later must be used in conjunction with this UEFI release. Please make sure
the current IMM firmware level is Version 1.28 or later before you update the UEFI
firmware.

Problem(s) Fixed:

- The system would boot with memory errors when memory mirroring was enabled.
- After a three times boot failure, scrolling the setup screens would leave
garbled characters at the bottom of the screen.
- Windows PE 32bit would boot without any PCI devices configured including
USB keyboard and mouse.
- When changing the iSCSI attempt on an installed Windows 2008 R2 SP1
server from no CHAP to Mutual CHAP, Windows fails to boot with a 0x7b.
- WHEA corrected error events are being logged without corresponding IMM
events.

Enhancements:
- This release supports Machine Type 7872 or 1909 with Intel Xeon 7500
or 6500 series processors, as well as, supports Machine Type 7873 and 1910
with Intel Xeon E7 series processors.
- Added support for UEFI PXE boot in IPv6 environment.
- Updated microcode for Intel Xeon E7 series processors to M05206F2_00000030.
- Updated Intel Memory and QPI Reference Code to Version 2.11.

Limitations:

- The disable controls for PCI slots 1 and 2 are reversed in this release.
- Internet Protocol Version 6 (IPv6) is disabled by default. Use the
System Settings' Operating Mode configuration screen to enable IPv6.
- After upgrading to this release internet Small Computer System Interface
(iSCSI) devices configured to be bootable will no longer be bootable.
Use the UEFI F1 Setup to reconfigure the iSCSI devices to work around
this issue.

Dependencies:

- IMM YUOOB7C (Version 1.28) or later is required.
- FPGA HIUD30L (Version 2.01) or later is required.


Version 1.40 - BuildID: HIE142B
---------------------------------------
Version 1.40 is for HX5 Machine Type 7873 and 1910 with Intel Xeon E7 series
processors.

IMPORTANT: IMM firmware YUOOA6A (Version 1.26) and FPGA firmware HIUD30J (Version
2.00) or later must be used in conjunction with this UEFI release. Please make sure
the current IMM firmware level is Version 1.26 or later before you update the UEFI
firmware.

Problem(s) Fixed:

- Microsoft Windows truncated memory dump file in EFI boot mode because the
number of memory regions in EFI memory map was exceeding the limit of Windows.
The problem was caused by fragmentation of EFI memory regions.
- After three consecutive UEFI boot failures, UEFI setup settings were changed
to default settings.
- Corrected memory error WHEA events were incorrectly logged in the Windows
system event log.
- Fixed detection of DIMM replacement and automatic reenabling of disabled DIMM.

Enhancements:

- Added error reporting to inform when the legacy option ROM space is not enough
to execute the option ROMs of all PCI adapters during legacy boot.
- Updated Broadcom firmware to Version T6.2.4.1.
- Added Extended APIC (X2APIC) support and a setup menu to enable or disable the
Extended APIC.
- Added Non-planar PXE option for legacy option ROMs to allow customers to disable
PXE for non-planar NICs and fit more legacy option ROMs in limited 128K space.

Limitations:

- This release does not support Machine Type 7872 or 1909 with Intel Xeon 7500 or
6500 series processors yet, but supports only Machine Type 7873 and 1910 with
Intel Xeon E7 series processors.

Dependencies:
- IMM YUOOA6A (Version 1.26) or later is required.
- FPGA HIUD30J (Version 2.00) or later is required.


Version 1.31 - BuildID: HIE130B
---------------------------------------
Problem(s) Fixed:

- Fixed issue with system generating NMI/Bus errors when using Qlogic CIOv and BOFM.

Enhancements:

Limitations:

Dependencies:


Version 1.30 - BuildID: HIE130A
---------------------------------------
Problem(s) Fixed:

- VMWare 4.0 ESXi fails to install with Version 1.25
- Fixed a potential POST (Power-on-Self-Test) hang which might occur during
recalibrating system power before OS starts.
- Memory patrol scrub option was not functioning. The problem was corrected
by updating Intel processor microcode and RAS code.
- Redundant Bit Steering feature was not working for DIMMs greater than single
rank in MAX5 memory expansion unit.
- Red Hat Enterprise Linux 6 (RHEL6) installation could not be continued
due to a video problem with EFI console output.
- Disable propagation of Intel VT-d faults as fatal errors to avoid guest
VM to cause the entire system to crash.

Enhancements:

- Enabled BPE4 support.
- Updated Broadcom firmware to T6.0.4.2.

Limitations:

Dependencies:


Version 1.25 - BuildID: HIE121E
---------------------------------------
Problem(s) Fixed:

- Fixed issue with setting boot options using Advanced Setup Utility(ASU).
Existing options would get pushed down the Start Options list instead of
start options only showing new list.
- Fixed a potential problem with unexpected QPI inband resets when QPI link is
running at 6.4GT/s.

Enhancements:

- Enabled MAX5 memory expansion.
- Added "Halt On Severe Error" setup option in Operating Modes setup
menu which can prevent the system from booting into OS and shows
POST Event Viewer if POST detects a severe error that caused an unexpected
reboot.

Limitations:

Dependencies:


Version 1.00 - BuildID: HIE106F
---------------------------------------
Problem(s) Fixed:

Initial release.

Enhancements:

Limitations:

Dependencies:

ibm_fw_uefi_hie179a-1_79_anyos_i386_chg

IBM ServeRAID MR10ie (CIOv) SAS Controller Firmware Update

Adapter Supported: Blade ServeRAID-MR10ie (CIOv) (46C7167)


Version 11.0.1-0046 - Suggested
-------------------
Enhancements: (Refer to Retain Tip H204756)
- Dual Band Charging
- Limited Band Charging

Version 11.0.1-0045 - Suggested
-------------------
Fixes:
- Adjust BBU thresholds to alleviate potentially unwanted messages. For further
details, please refer to Retain Tip H202008

Version 11.0.1-0042 - Critical
-------------------
Enhancements:
Adjust various battery parameters and alerts to improve product
- Reword the battery ‘Prefail‚ and ‘Fail‚ Alerts and all places it is documented
- Add visibility of ‘battery nearing end of usable life‚ condition to CLI and MSM
- Adjust parameters used to calculate battery capacity amount for Early Warning
and EOL alerts

Fixes:
- Fixed issue where While correcting massive UNC sectors, I/O will be
interrupted causing OS becomes unusable
- Fixed issue where SPD Data can get Corrupted on Boot causing the following
message on boot the message displayed is "Check SDRAM Connection".
- Fixed issue where firmware has Incompleted Writes During Power Fail and Recovery
causing the following message on boot "Controller cache discarded due to
memory/battery problems

Version 11.0.1-0040 (Install Package 02) - Critical
-------------------
Fixes:
- Package version number updated.
Note: No change to the firmware version is still 11.0.1-0040.

Version 11.0.1-0040.01 - Critical
-------------------
Fixes:
- Fixed a packaging issue where the drives are no longer recognized in Blade HS12
with a IBM ServeRAID MR10ie.
Note: No change to the firmware.

Version 11.0.1-0040 - Critical
-------------------
Fixes:
- Fixed an issue that was contributing to early fallout with
battery packs.
- Fixed an issue that was causing a loss of battery capacity.
- Fixed an issue where the gas gauge was reporting capacity of
65000+mAh and then marking battery as SOH bad.

Version 11.0.1-0039 - Critical
-------------------
Fixes:
- Fixed issue where multiple reboots were required after a new battery was
inserted in a controller.
- Fixed issue where T95: VT#00560-T95386=Battery cannot support data retention
for more than 59 hours. Please replace the battery. When battery logic generates
the event MR_EVT_BBU_REPLACEMENT_NEEDED_SOH_NOT_OPTIMAL, the FW prints the error,
T95: EVT#00538-T95: 386=Unknown ARG type=24, code=182.

- Changed post message from

RAID ADAPTER
Memory Error !!!
Please check the SDRAM connection.
If problems persist contact Tech Support.
Press Any Key to Continue…

to

Check the SDRAM connection, if applicable, or replace the controller."

Version 11.0.1-0036 - Critical
-------------------
Enhancements
- BBU AEN enhancements

Fixes:
- Fixed issue where firwmare fault could occur when a hot spare drive responds
with Sense 0x02 for Write/Verify.
- Fixed issue where a firwmare fault could occur when consecutive Medium
Errors are found in Degraded SATA RAID5, 6 state
- Fixed issue where the Battery Unqualified Relearn Counter was not being reset
after a battery is replaced.
- Display message, "Detected new battery, so resetting learn cycle counter," and
reset 'learn cycle' counter When new battery is added to the ServeRAID MR10ie

Version 11.0.1-0030 - Critical
-------------------
Fixes:
- Leaving array size field blank during array creation to resolve issue
where raid level would change but array size did not change with the level.
Retain tip H196863.
- Fixed issue where the Cursor movement is not proper while entering
Security Key/PassPhrase in EFI WebBIOS environment
- Fixed issue where the Visibility of webbios version doing controller
selection is not there
- Address compatabilty issue with uEFI WebBIOS in the x3850 x5 and HS22 x5
- Fixed issue where a fatal FW Error happens during Consistency Check
operation while a patrol read is in progress.

Version 11.0.1-0024 - Critical
-------------------
NOTE TO SERVICE - H196421, H196426, H196374
Fixes:
- Fixed issue with Firmware Hang (Fatal Error) when drive responds with
Sense 0x02 for Test Unit Ready Command.
- Fixed an issue where the ServeRAID-MR10ie (CIOv) battery fault
indicator never clears
- Added limit to quantity of consecutive relearn cycles to cache
battery unit
- Fixed issue where the Pass phrase can not be entered on the ServeRAID
MR10is controller
- Fixed issue where the user cannot enter the uEFI WebBIOS or system
will hang on boot

Version 11.0.1-0014 - Critical
-------------------
NOTE TO SERVICE - Reference RETAIN #N/A
Fixes:
- Addressed an issue where, during I/O and manual copyback on a degraded RAID
6 virtual drive with medium errors, incorrect data could be created on the
drive.
- Fixed an issue where, on the ServeRAID 10ie (CIOv), a new or changed battery
installation was not detected on the iBBU.
- Fixed an issue where SATA drives may not be detected at POST when attached
to an expander.
- Addressed an issue where the controller may hang if a medium error occurs
during a rebuild.
- Fixed an issue where cache data could be lost during a reset after the
express link is dropped.
- Addressed an issue where a consistency check doesn't regenerate parity after
hitting a double media error.
- Fixed an issue where the uEFI WebBIOS can hang if the user presses the right
mouse button when user input is not required.
- Addressed an issue where an invalid memory or battery error is reported on
boot, but does not reappear on a subsequent boot.

Version 11.0.1-0012 - Suggested
-------------------
NOTE TO SERVICE - Reference RETAIN #N/A
Fixes:
- Fixed an issue where, rarely, cached data may be lost on system shutdown or
reboot.

Version 11.0.1-0008 - Critical
-------------------
NOTE TO SERVICE - Reference RETAIN #H194224, H194505, H194171
Fixes:
- Fixed an issue which could result in incorrect data on the drives after
heavy I/O. (Retain tip H194224)
- Fixed an issue where, if medium errors are experienced while a background
operation is running, incorrect data could be written to the drives. (Retain
tip H194505)
- Changed the warning message that appears when the card goes in to temporary
write through mode. (Retain tip H194171)
- Fixed an error where erroneous Bad Battery messages were displayed even
after a Learn Cycle was performed.
- Fixed an issue that resulted in SERRs on a ServeRAID-MR10M controller.
- Improved the handling of bad cable scenarios which could cause system hangs.

Functionality:
- Added support for UEFI based systems.
- Added support for Solid State Drives (SSDs).
- Added tape support for the ServeRAID 10ie (CIOv) controller.
- Added the ability to handle SGPIO and SES signalling on a per-port basis to
handle configurations with both direct attached and expander attached drives
on a single controller.
- Added a field to show hard drive model names in WebBIOS.


Version 9.0.1-0041
------------------
- Initial release
ibm_fw_sraidmr_10ie-11_0_1-0046_linux_32-64_chg

IBM Online SAS/SATA Hard Disk Drive Update Program

Version 1.12.01 Build ID: SAS_11201

NOTE TO SERVICE - Reference RETAIN #H207740

*******************************************

Version 1.12.01
Critical Release

This package includes new updates to drives with product ID strings of:

SAS 3.5"

- VPCA300900EST1, VPCA450900EST1, VPCA600900EST1 to A3C4,
Corrects firmware bug that may cause data corruption.
For further information, please refer to Retain Tip H207740.

===============================================================

Version 1.12
(Critical)

Added Support for SAS Controllers M5115 and H1135

SAS 3.5"
Product ID FW

IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST373455SS BA2D
IBM-ESXSST3146855SS BA2D
IBM-ESXSST3300655SS BA2D
IBM-ESXSST373355SS BA38
IBM-ESXSST3146755SS BA38
IBM-ESXSST3300555SS BA38
IBM-ESXSST3146356SS BA4D
IBM-ESXSST3300656SS BA4D
IBM-ESXSST3450856SS BA4D
IBM-ESXSST3300657SS BA5A
IBM-ESXSST3450857SS BA5A
IBM-ESXSST3600057SS BA5A
IBM-ESXSST3750630SS BC1I
IBM-ESXSST31000640SS BC1I
IBM-ESXSST31000424SS BC2C
IBM-ESXSST32000444SS BC2C
IBM-ESXSST33000650SS BC3D
IBM-ESXSST1000NM0001 BC48
IBM-ESXSST2000NM0001 BC48
IBM-ESXSVPCA300900EST1 A3C2
IBM-ESXSVPCA600900EST1 A3C2
IBM-ESXSVPBA073C3ETS11 A496
IBM-ESXSVPBA146C3ETS11 A496
IBM-ESXSVPBA300C3ETS11 A496
IBM-ESXSVPBPA300C3EST1 A529
IBM-ESXSVPA036C3-ETS10 A650
IBM-ESXSVPA073C3-ETS10 A650
IBM-ESXSVPA146C3-ETS10 A650
IBM-ESXSHUS723020ALS64 J26C
IBM-ESXSHUS723030ALS64 J26C
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSMAU3036RC S902
IBM-ESXSMAU3073RC S902
IBM-ESXSMAU3147RC S902
IBM-ESXSMBA3073RC SA0A
IBM-ESXSMBA3147RC SA0A
IBM-ESXSMBA3300RC SA0A
IBM-ESXSMAX3036RC T907
IBM-ESXSMAX3073RC T907
IBM-ESXSMAX3147RC T907

SAS 2.5"
Product ID FW

IBM-ESXSST936701SS B51D
IBM-ESXSST973401SS B51D
IBM-ESXSST936701SS B51D
IBM-ESXSST973401SS B51D
IBM-ESXSST973402SS B52B
IBM-ESXSST9146802SS B52B
IBM-ESXSST9300603SS B53E
IBM-ESXSST9146803SS B53E
IBM-ESXSST9600204SS B549
IBM-ESXSST9300605SS B55C
IBM-ESXSST9600205SS B55C
IBM-ESXSST9900805SS B55C
IBM-ESXSST936751SS B617
IBM-ESXSST973451SS B617
IBM-ESXSST973452SS B62C
IBM-ESXSST9146852SS B62C
IBM-ESXSST9146853SS B63A
IBM-ESXSST9300653SS B63A
IBM-ESXSST9500430SS BD14
IBM-ESXSST9500620SS BD2C
IBM-ESXSST91000640SS BD2C
IBM-ESXSST9300503SS E536
IBM-ESXSST9300505SS E555
IBM-ESXSST9600105SS E555
IBM-ESXSST9900705SS E555
IBM-ESXSST9146752SS E625
IBM-ESXSST9146753SS E635
IBM-ESXSCBRBA073C3ETS0 C49C
IBM-ESXSCBRBA146C3ETS0 C49C
IBM-ESXSCBRCA146C3ETS0 C610
IBM-ESXSCBRCA300C3ETS0 C610
IBM-ESXSHUC106030CSS60 D3A6
IBM-ESXSHUC106060CSS60 D3A6
IBM-ESXSMAV2036RC S116
IBM-ESXSMAV2073RC S116
IBM-ESXSMBB2073RC SB07
IBM-ESXSMBB2147RC SB07
IBM-ESXSMBD2147RC SB1A
IBM-ESXSMBD2300RC SB1A
IBM-ESXSMBF2300RC SB2B
IBM-ESXSMBF2600RC SB2B
IBM-ESXSMBC2073RC SC06
IBM-ESXSMBE2073RC SC17
IBM-ESXSMBE2147RC SC17
IBM-ESXSMK1401GRRB SC27
IBM-ESXSMK3001GRRB SC27
IBM-ESXSMAY2036RC T107
IBM-ESXSMAY2073RC T107
IBM-ESXSWD9001BKHG-23D ZA31
IBM-ESXSWD6001BKHG-23D ZA31
IBM-ESXSWD3001BKHG-23D ZA31

SATA 3.5"
Product ID FW

WD2003FYYS-23T8B0 01.00D04
WD802ABYS-23B7A0 02.03B05
WD2502ABYS-23B7A0 02.03B08
WD1602ABYS-23B7A0 02.03B07
WD2003FYYS-23W0B0 WA34
WDC WD1003FBYX-23Y7B0 WB33
WD5003ABYX-23 WC34
ST380819AS 3.05
ST3160828AS 3.05
ST340212AS 3.05
ST3160023AS 3.48
ST380013AS 3.48
ST340014AS 3.48
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB15
ST3500320NS BB15
ST3750330NS BB15
ST31000340NS BB15
ST3500514NS BB2A
ST31000524NS BB2A
ST32000644NS BB2A
ST33000650NS BB38
ST1000NM0011 BB47
ST2000NM0011 BB47
ST500NM0011 BB47
HUA721050KLA330 GK6OABDA
HUA721075KLA330 GK8OABDA
HUA721010KLA330 GKAOABDA
HUA722020ALA330 JKAOA3IA
HDS721025CLA382 JP1OA54C
HUA722050CLA330 JP2OA3GB
HUA722010CLA330 JP4OA3GB
HDS725050KLA360 K2AOAT3A
HUA723020ALA640 MK7OA900
HUA723030ALA640 MKAOA900
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
Hitachi HDT725025VLA3 V5DOA7CA

SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V10
ST9160511NS BE1A
ST9500530NS BE1A
ST9250610NS BE25
ST9500620NS BE25
ST91000640NS BE25

SSD
Product ID FW

TX21B10200GE1IBM PRO6SP36
TX21B10400GE1IBM PRO6SP36
TX21B10100GE8IBM PRO6SP36
TE22D10100GE8IBM PRO6SR36
SG9XCS1B50GMIBM SA03SB6F
SG9XCS1F200GEIBM SA03SB6F
SG9XCS2D200GEIBM SA03SE6H
GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
MTFDDAA512MAR-1K1AB MA52
MTFDDAK128MAR-1J1AA MA52
MTFDDAK256MAR-1K1AA MA52
MTFDDAK064MAR-1J1AA MA52
MTFDDAK512MAR-1K1AA MA52
MTFDDAA064MAR-1K1AB MA52
MTFDDAA128MAR-1K1AB MA52
MTFDDAA256MAR-1K1AB MA52
STEC M8PSB1 0409
STEC MACH8 IOPS 2804
STEC M8PSB2 T4 SM06
STEC M8PSB1 T4 SM16

SAS 3.5"

- ST3300657SS, ST3450857SS, ST3600057SS to BA5A
VPCA300900EST1, VPCA600900EST1 to A3C2
Additions to VPD information used by manufacturing

- ST3750630SS, ST31000640SS to BC1I
ST31000424SS, ST32000444SS to BC2C
Mode Page change to address performance issues under certain system configurations

- ST33000650SS to BC3D
ST1000NM0001, ST2000NM0001 to BC48
Protection Information Fix - see Retain Tip H206140

- HUS723020ALS64, HUS723030ALS64 to J26C
Initial Code Release

SAS 2.5"

- ST9300603SS, ST9146803SS to B53E
ST9600204SS to B549
Additions to VPD information used by manufacturing

- ST9300605SS, ST9600205SS, ST9900805SS to B55C
ST9146853SS, ST9300653SS to B63A
ST9500620SS, ST91000640SS to BD2C
ST9300505SS to E555
ST9146753SS to E635
Protection Information Fix - see Retain Tip H206140

- ST9600105SS, ST9900705SS to E555
Inital Code Release

- HUC106030CSS60, HUC106060CSS60 to D3A6
Performance improvements, critical fixes for Protection Information (PI)
operation - see Retain Tip H206140

- MK1401GRRB, MK3001GRRB to SC27
Additions to VPD information used by manufacturing

- WD9001BKHG-23D, WD6001BKHG-23D, WD3001BKHG-23D to ZA31
Initial Code Release

SATA 3.5"

- WD2502ABYS-23B7A0 to 02.03B08
WD1602ABYS-23B7A0 to 02.03B07
Critical fix to address premature drive failures.

- ST3500514NS, ST31000524NS, ST32000644NS to BB2A
ST33000650NS to BB38
ST1000NM0011, ST2000NM0011, ST500NM0011 to BB47
Fixes a potential, but rare data corruption issue which requires
a background reallocation that exceeds the error recovery timer.

- HUA723020ALA640 to MK70A900
HUA723030ALA640 to MKA0A900
Initial Code Release

SATA 2.5"

- ST9160511NS, ST9500530NS to BE1A
ST9250610NS, ST9500620NS, ST91000640NS to BE25
Fixes a potential, but rare data corruption issue which requires
a background reallocation that exceeds the error recovery timer.

SSD

- TX21B10200GE1IBM, TX21B10400GE1IBM, TX21B10100GE8IBM to PRO6SP36
TE22D10100GE8IBM to PRO6SR36
Initial Code Release

- MTFDDAK128MAR-1J1AA, MTFDDAK256MAR-1K1AA to MA52
Initial Code Release

- MTFDDAA512MAR-1K1AB, MTFDDAK064MAR-1J1AA, MTFDDAK512MAR-1K1AA,
MTFDDAA064MAR-1K1AB, MTFDDAA128MAR-1K1AB, MTFDDAA256MAR-1K1AB to MA52
Fixes SMART attribute 190 (Current Temp) which caused warning messages
with some versions of Linux

- STEC MACH8 IOPS to 2804
STEC M8PSB2 T4 to SM06
Additions to VPD information used by manufacturing
Fixes potential drive failure if power loss occurs during firmware update.

*******************************************

Version 1.11.01
(Non-Critical)
- Fixed issue where hard disk drives may not be detected in
configurations with multiple Emulex adapters.

See Verion 1.11 for Hard Disk Drive support, firmware levels,
and respective change History.

Version 1.11
(Critical)

SAS 3.5"
Product ID FW

IBM-ESXSVPCA300900EST1 A3C0
IBM-ESXSVPCA600900EST1 A3C0
IBM-ESXSVPBA073C3ETS11 A496
IBM-ESXSVPBA146C3ETS11 A496
IBM-ESXSVPBA300C3ETS11 A496
IBM-ESXSVPBPA300C3EST1 A529
IBM-ESXSVPA036C3-ETS10 A650
IBM-ESXSVPA073C3-ETS10 A650
IBM-ESXSVPA146C3-ETS10 A650
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST373455SS BA2D
IBM-ESXSST3146855SS BA2D
IBM-ESXSST3300655SS BA2D
IBM-ESXSST373355SS BA38
IBM-ESXSST3146755SS BA38
IBM-ESXSST3300555SS BA38
IBM-ESXSST3146356SS BA4D
IBM-ESXSST3300656SS BA4D
IBM-ESXSST3450856SS BA4D
IBM-ESXSST3300657SS BA59
IBM-ESXSST3450857SS BA59
IBM-ESXSST3600057SS BA59
IBM-ESXSST3750630SS BC1H
IBM-ESXSST31000640SS BC1H
IBM-ESXSST31000424SS BC2B
IBM-ESXSST32000444SS BC2B
IBM-ESXSST33000650SS BC3A
IBM-ESXSST1000NM0001 BC44
IBM-ESXSST2000NM0001 BC44
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSMAU3036RC S902
IBM-ESXSMAU3073RC S902
IBM-ESXSMAU3147RC S902
IBM-ESXSMBA3073RC SA0A
IBM-ESXSMBA3147RC SA0A
IBM-ESXSMBA3300RC SA0A
IBM-ESXSMAX3036RC T907
IBM-ESXSMAX3073RC T907
IBM-ESXSMAX3147RC T907

SAS 2.5"
Product ID FW

IBM-ESXSST936701SS B51D
IBM-ESXSSTLFF_SATA3401SS B51D
IBM-ESXSST936701SS B51D
IBM-ESXSSTLFF_SATA3401SS B51D
IBM-ESXSSTLFF_SATA3402SS B52B
IBM-ESXSST9146802SS B52B
IBM-ESXSST9300603SS B53C
IBM-ESXSST9146803SS B53C
IBM-ESXSST9600204SS B548
IBM-ESXSST9300605SS B559
IBM-ESXSST9600205SS B559
IBM-ESXSST9900805SS B559
IBM-ESXSST936751SS B617
IBM-ESXSSTLFF_SATA3451SS B617
IBM-ESXSSTLFF_SATA3452SS B62C
IBM-ESXSST9146852SS B62C
IBM-ESXSST9146853SS B637
IBM-ESXSST9300653SS B637
IBM-ESXSST9500430SS BD14
IBM-ESXSST9500620SS BD29
IBM-ESXSST91000640SS BD29
IBM-ESXSCBRBA073C3ETS0 C49C
IBM-ESXSCBRBA146C3ETS0 C49C
IBM-ESXSCBRCA146C3ETS0 C610
IBM-ESXSCBRCA300C3ETS0 C610
IBM-ESXSHUC106030CSS60 D390
IBM-ESXSHUC106060CSS60 D390
IBM-ESXSST9300503SS E536
IBM-ESXSST9300505SS E553
IBM-ESXSST9146752SS E625
IBM-ESXSST9146753SS E633
IBM-ESXSMAV2036RC S116
IBM-ESXSMAV2073RC S116
IBM-ESXSMBB2073RC SB07
IBM-ESXSMBB2147RC SB07
IBM-ESXSMBD2147RC SB1A
IBM-ESXSMBD2300RC SB1A
IBM-ESXSMBF2300RC SB28
IBM-ESXSMBF2600RC SB28
IBM-ESXSMBC2073RC SC06
IBM-ESXSMBE2073RC SC17
IBM-ESXSMBE2147RC SC17
IBM-ESXSMK1401GRRB SC23
IBM-ESXSMK3001GRRB SC23
IBM-ESXSMAY2036RC T107
IBM-ESXSMAY2073RC T107

SATA 3.5"
Product ID FW

ST340212AS 3.05
ST380819AS 3.05
ST3160828AS 3.05
ST340014AS 3.48
ST380013AS 3.48
ST3160023AS 3.48
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB15
ST3500320NS BB15
ST3750330NS BB15
ST31000340NS BB15
ST3500514NS BB29
ST31000524NS BB29
ST32000644NS BB29
ST33000650NS BB36
ST1000NM0011 BB46
ST2000NM0011 BB46
ST500NM0011 BB46
HUA721050KLA330 GK6OABDA
HUA721075KLA330 GK8OABDA
HUA721010KLA330 GKAOABDA
HUA722020ALA330 JKAOA3GA
HDS721025CLA382 JP1OA3GE
HUA722050CLA330 JP2OA3GB
HUA722010CLA330 JP4OA3GB
HDS725050KLA360 K2AOAT3A
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
Hitachi HDT725025VLA3 V5DOA7CA
WD2003FYYS-23W0B0 WA32
WDC WD1003FBYX-23Y7B0 WB31
WD5003ABYX-23 WC31
WD2003FYYS-23T8B0 01.00D04
WD802ABYS-23B7A0 02.03B05
WDC WD2502ABYS-23B7A0 02.03B06
WD2502ABYS-23B7A0 02.03B07
WD1602ABYS-23B7A0 02.03B07

SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V10
ST9160511NS BE19
ST9500530NS BE19
ST9250610NS BE24
ST9500620NS BE24
ST91000640NS BE24

SATA 2.5" SSD
Product ID FW

GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
STEC MACH8 IOPS 2765
STEC M8PSB2 T4 SM05
SG9XCS2D200GEIBM SA03SE6C
MTFDDAK128MAR-1JAAB MA44
MTFDDAK256MAR-1JAAB MA44

SATA 1.8" SSD
Product ID FW

STEC M8PSB1 0409
STEC M8PSB1 T4 SM16
SG9XCS1B50GMIBM SA03SB6C
SG9XCS1F200GEIBM SA03SB6C


SAS 3.5"

- ST33000650SS to BC3A
ST1000NM0001, ST2000NM0001 to BC44
Additions and corrections to VPD information used by manufacturing

SAS 2.5"

- ST9300605SS, ST9600205SS, ST9900805SS to B559
ST9146853SS, ST9300653SS to B637
ST9500620SS, ST91000640SS to BD29
ST9300505SS to E553
SST9146753SS to E633
HUC106030CSS60, HUC106060CSS60 to D390
Additions and corrections to VPD information used by manufacturing

- MK1401GRRB, MK3001GRRB to SC23
Fixes a pottential data corruption bug if there is an
unexpected power loss.

SATA 3.5"

- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15
ST3500514NS, ST31000524NS, ST32000644NS to BB29
ST33000650NS to BB36
ST1000NM0011, ST2000NM0011, ST500NM0011 to BB46

SATA SSD

- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB6C
SG9XCS2D200GEIBM to SA03SE6C
Fix for potential hang during an unexpected power cycle

MTFDDAK128MAR-1JAAB, MTFDDAK256MAR-1JAAB to MA44
Initial Release

===========================================
Version 1.10
(Critical)

SAS 3.5"
Product ID FW

IBM-ESXSVPCA300900EST1 A3C0
IBM-ESXSVPCA600900EST1 A3C0
IBM-ESXSVPBA073C3ETS11 A496
IBM-ESXSVPBA146C3ETS11 A496
IBM-ESXSVPBA300C3ETS11 A496
IBM-ESXSVPBPA300C3EST1 A529
IBM-ESXSVPA036C3-ETS10 A650
IBM-ESXSVPA073C3-ETS10 A650
IBM-ESXSVPA146C3-ETS10 A650
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST373455SS BA2D
IBM-ESXSST3146855SS BA2D
IBM-ESXSST3300655SS BA2D
IBM-ESXSST373355SS BA38
IBM-ESXSST3146755SS BA38
IBM-ESXSST3300555SS BA38
IBM-ESXSST3146356SS BA4C
IBM-ESXSST3300656SS BA4C
IBM-ESXSST3450856SS BA4C
IBM-ESXSST3300657SS BA58
IBM-ESXSST3450857SS BA58
IBM-ESXSST3600057SS BA58
IBM-ESXSST3750630SS BC1H
IBM-ESXSST31000640SS BC1H
IBM-ESXSST31000424SS BC2B
IBM-ESXSST32000444SS BC2B
IBM-ESXSST33000650SS BC37
IBM-ESXSST1000NM0001 BC42
IBM-ESXSST2000NM0001 BC42
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSMAU3036RC S902
IBM-ESXSMAU3073RC S902
IBM-ESXSMAU3147RC S902
IBM-ESXSMBA3073RC SA0A
IBM-ESXSMBA3147RC SA0A
IBM-ESXSMBA3300RC SA0A
IBM-ESXSMAX3036RC T907
IBM-ESXSMAX3073RC T907
IBM-ESXSMAX3147RC T907

SAS 2.5" (SFF)
Product ID FW

IBM-ESXSST936701SS B51D
IBM-ESXSST973401SS B51D
IBM-ESXSST936701SS B51D
IBM-ESXSST973401SS B51D
IBM-ESXSST973402SS B52B
IBM-ESXSST9146802SS B52B
IBM-ESXSST9300603SS B53C
IBM-ESXSST9146803SS B53C
IBM-ESXSST9600204SS B548
IBM-ESXSST9300605SS B556
IBM-ESXSST9600205SS B556
IBM-ESXSST9900805SS B556
IBM-ESXSST936751SS B617
IBM-ESXSST973451SS B617
IBM-ESXSST973452SS B62C
IBM-ESXSST9146852SS B62C
IBM-ESXSST9146853SS B635
IBM-ESXSST9300653SS B635
IBM-ESXSST9500430SS BD14
IBM-ESXSST9500620SS BD26
IBM-ESXSST91000640SS BD26
IBM-ESXSCBRBA073C3ETS0 C49C
IBM-ESXSCBRBA146C3ETS0 C49C
IBM-ESXSCBRCA146C3ETS0 C610
IBM-ESXSCBRCA300C3ETS0 C610
IBM-ESXSHUC106030CSS60 D340
IBM-ESXSHUC106060CSS60 D340
IBM-ESXSST9300503SS E536
IBM-ESXSST9300505SS E552
IBM-ESXSST9146752SS E625
IBM-ESXSST9146753SS E632
IBM-ESXSMAV2036RC S116
IBM-ESXSMAV2073RC S116
IBM-ESXSMBB2073RC SB07
IBM-ESXSMBB2147RC SB07
IBM-ESXSMBD2147RC SB1A
IBM-ESXSMBD2300RC SB1A
IBM-ESXSMBF2300RC SB28
IBM-ESXSMBF2600RC SB28
IBM-ESXSMBC2073RC SC06
IBM-ESXSMBE2073RC SC17
IBM-ESXSMBE2147RC SC17
IBM-ESXSMAY2036RC T107
IBM-ESXSMAY2073RC T107

SATA 3.5"
Product ID FW

ST340212AS 3.05
ST380819AS 3.05
ST3160828AS 3.05
ST340014AS 3.48
ST380013AS 3.48
ST3160023AS 3.48
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB15
ST3500320NS BB15
ST3750330NS BB15
ST31000340NS BB15
ST3500514NS BB29
ST31000524NS BB29
ST32000644NS BB29
ST33000650NS BB34
ST1000NM0011 BB45
ST2000NM0011 BB45
ST500NM0011 BB45
HUA721050KLA330 GK6OABDA
HUA721075KLA330 GK8OABDA
HUA721010KLA330 GKAOABDA
HUA722020ALA330 JKAOA3GA
HDS721025CLA382 JP1OA3GE
HUA722050CLA330 JP2OA3GB
HUA722010CLA330 JP4OA3GB
HDS725050KLA360 K2AOAT3A
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
Hitachi HDT725025VLA3 V5DOA7CA
WD2003FYYS-23W0B0 WA32
WDC WD1003FBYX-23Y7B0 WB31
WD5003ABYX-23 WC31
WD2003FYYS-23T8B0 01.00D04
WD802ABYS-23B7A0 02.03B05
WDC WD2502ABYS-23B7A0 02.03B06
WD2502ABYS-23B7A0 02.03B07
WD1602ABYS-23B7A0 02.03B07

SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V10
ST9160511NS BE19
ST9500530NS BE19
ST9250610NS BE24
ST9500620NS BE24
ST91000640NS BE24

SATA 2.5" SSD
Product ID FW

GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
STEC MACH8 IOPS 2765
STEC M8PSB2 T4 SM05
SG9XCS2D200GEIBM SA03SE6C

SATA 1.8" SSD
Product ID FW

STEC M8PSB1 0409
STEC M8PSB1 T4 SM16
SG9XCS1B50GMIBM SA03SB6C
SG9XCS1F200GEIBM SA03SB6C

This package includes new updates to drives with product ID strings of:

SAS 3.5"

- VPCA300900EST1, VPCA600900EST1 to A3C0
Correction to VPD information used by manufacturing

- ST31000424SS, ST32000444SS to BC2B
Fixes to improve robustness from certain read errors due to encroachment

- ST33000650SS to BC37
Fixes to improve overall robustness.

- ST1000NM0001, ST2000NM0001 to BC42
Inital Release

SAS 2.5" (SFF)

- ST9300605SS, ST9600205SS, ST9900805SS to B556
- ST9146853SS, ST9300653SS to B635
Fixes to improve overall robustness.

ST9300505SS to E552
ST9146753SS to E632
Initial Release

- ST9500620SS, ST91000640SS to BD26
Improve general robustness and added support for DPICZ

- HUC106030CSS60, HUC106060CSS60 to D340
Improve general robustness

- MBF2300RC, MBF2600RC to SB28
Improves performance in certain benchmarks

SATA 3.5"

- ST33000650NS to BB34
Fixes to improve overall robustness.

- ST1000NM0011, ST2000NM0011, ST500NM0011 to BB45
Initial Release

- ST3500514NS, ST31000524NS, ST32000644NS to BB29
Fixes for intermittent drive hangs

- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB15
Added enhancement for improved robustness


SATA 2.5"

- ST9250610NS, ST9500620NS, ST91000640NS to BE24
Initial Release

- ST9160511NS, ST9500530NS to BE19
Fixes for overall robustness.


SATA 2.5" SSD

- STEC MACH8 IOPS to 2765
STEC M8PSB2 T4 to SM05
Fixes potential drive lock up during cold or warm boots
Fixes issues with RHEL 6.x installation

- SG9XCS2D200GEIBM to SA03SE6C
Fixes default drive VPD information for manufacturing,
the default LED behavior on certain systems and
fixes issues with client install thru VMWare 5.x

SATA 1.8" SSD

- STEC M8PSB1 to 0409
STEC M8PSB1 T4 to SM16
Fixes potential drive lock up during cold or warm boots
Fixes issues with RHEL 6.x installation

- SG9XCS1B50GMIBM to SA03SB6C
SASG9XCS1F200GEIBM to SA03SB6C
Fixes potential drive lock up during cold or warm boots and
the default LED behavior on certain systems and
fixes issues with client install thru VMWare 5.x

===========================================
Version 1.09
(Critical)

SAS 3.5"
Product ID FW

IBM-ESXSVPCA300900EST1 A3B8
IBM-ESXSVPCA450900EST1 A3B8
IBM-ESXSVPCA600900EST1 A3B8
IBM-ESXSVPBA073C3ETS11 A496
IBM-ESXSVPBA146C3ETS11 A496
IBM-ESXSVPBA300C3ETS11 A496
IBM-ESXSVPBPA300C3EST1 A529
IBM-ESXSVPA036C3-ETS10 A650
IBM-ESXSVPA073C3-ETS10 A650
IBM-ESXSVPA146C3-ETS10 A650
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST336754SS BA1A
IBM-ESXSST373454SS BA1A
IBM-ESXSST3146854SS BA1A
IBM-ESXSST373455SS BA2D
IBM-ESXSST3146855SS BA2D
IBM-ESXSST3300655SS BA2D
IBM-ESXSST373355SS BA38
IBM-ESXSST3146755SS BA38
IBM-ESXSST3300555SS BA38
IBM-ESXSST3146356SS BA4C
IBM-ESXSST3300656SS BA4C
IBM-ESXSST3450856SS BA4C
IBM-ESXSST3300657SS BA58
IBM-ESXSST3450857SS BA58
IBM-ESXSST3600057SS BA58
IBM-ESXSST3750630SS BC1H
IBM-ESXSST31000640SS BC1H
IBM-ESXSST31000424SS BC28
IBM-ESXSST32000444SS BC28
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSGNA073C3ESTT0Z BH0J
IBM-ESXSGNA146C3ESTT0Z BH0J
IBM-ESXSGNA300C3ESTT0Z BH0J
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSBBA036C3ESTT0Z BH0K
IBM-ESXSBBA073C3ESTT0Z BH0K
IBM-ESXSBBA146C3ESTT0Z BH0K
IBM-ESXSMAU3036RC S902
IBM-ESXSMAU3073RC S902
IBM-ESXSMAU3147RC S902
IBM-ESXSMBA3073RC SA0A
IBM-ESXSMBA3147RC SA0A
IBM-ESXSMBA3300RC SA0A
IBM-ESXSMAX3036RC T907
IBM-ESXSMAX3073RC T907
IBM-ESXSMAX3147RC T907

SAS 2.5" (SFF)
Product ID FW

IBM-ESXSST936701SS B51D
IBM-ESXSST973401SS B51D
IBM-ESXSST936701SS B51D
IBM-ESXSST973401SS B51D
IBM-ESXSST973402SS B52B
IBM-ESXSST9146802SS B52B
IBM-ESXSST9300603SS B53C
IBM-ESXSST9146803SS B53C
IBM-ESXSST9600204SS B548
IBM-ESXSST936751SS B617
IBM-ESXSST973451SS B617
IBM-ESXSST973452SS B62C
IBM-ESXSST9146852SS B62C
IBM-ESXSST9500430SS BD14
IBM-ESXSST9500620SS BD22
IBM-ESXSST91000640SS BD22
IBM-ESXSCBRBA073C3ETS0 C49C
IBM-ESXSCBRBA146C3ETS0 C49C
IBM-ESXSCBRCA146C3ETS0 C610
IBM-ESXSCBRCA300C3ETS0 C610
IBM-ESXSHUC106030CSS60 D2F8
IBM-ESXSHUC106060CSS60 D2F8
IBM-ESXSST9300503SS E536
IBM-ESXSST9146752SS E625
IBM-ESXSMAV2036RC S116
IBM-ESXSMAV2073RC S116
IBM-ESXSMBB2073RC SB07
IBM-ESXSMBB2147RC SB07
IBM-ESXSMBD2147RC SB1A
IBM-ESXSMBD2300RC SB1A
IBM-ESXSMBC2073RC SC06
IBM-ESXSMBE2073RC SC17
IBM-ESXSMBE2147RC SC17
IBM-ESXSMBF2300RC SB28
IBM-ESXSMBF2600RC SB28


IBM-ESXSMAY2036RC T107
IBM-ESXSMAY2073RC T107

SATA 3.5"
Product ID FW

ST340212AS 3.05
ST380819AS 3.05
ST3160828AS 3.05
ST340014AS 3.48
ST380013AS 3.48
ST3160023AS 3.48
WD2003FYYS-23T8B0 01.00D04
WD802ABYS-23B7A0 02.03B05
WDC WD2502ABYS-23B7A0 02.03B06
WD2502ABYS-23B7A0 02.03B07
WD1602ABYS-23B7A0 02.03B07
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB14
ST3500320NS BB14
ST3750330NS BB14
ST31000340NS BB14
ST3500514NS BB28
ST31000524NS BB28
ST32000644NS BB28
HUA721050KLA330 GK6OABDA
HUA721075KLA330 GK8OABDA
HUA721010KLA330 GKAOABDA
HUA722020ALA330 JKAOA3GA
HDS721025CLA382 JP1OA3GE
HUA722050CLA330 JP2OA3GB
HUA722010CLA330 JP4OA3GB
HDS725050KLA360 K2AOAT3A
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
Hitachi HDT725025VLA3 V5DOA7CA
WD2003FYYS-23T8B0 01.00D04
WD802ABYS-23B7A0 02.03B05
WD2502ABYS-23B7A0 02.03B07
WD1602ABYS-23B7A0 02.03B07
WD2003FYYS-23W0B0 WA32
WDC WD1003FBYX-23Y7B0 WB31
WD5003ABYX-23 WC31

SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V10
ST9160511NS BE18
ST9500530NS BE18
ST9250610NS BE21
ST9500620NS BE21
ST91000640NS BE21

SATA 2.5" SSD
Product ID FW

GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
STEC MACH8 IOPS 2732
STEC M8PSB2 T4 SM04

SATA 1.8" SSD
Product ID FW

STEC M8PSB1 0408
STEC M8PSB1 T4 SM15
SG9XCS1B50GMIBM SA03SB63
SG9XCS1F200GEIBM SA03SB63


This package includes new updates to drives with product ID strings of:

SAS 3.5"

- ST31000424SS, ST32000444SS to BC28
Added enhancement for improved RV robustness

- MBE2073RC, MBE2147RC to SC17
- MBA3073RC, MBA3147RC, MBA3300RC to SA0A
Added VPD changes for manufacturing

SAS 2.5" (SFF)

- ST9300603SS, ST9146803SS to B53C
ST9600204SS to B548
SST973452SS, ST9146852SS to B62C
CBRCA146C3ETS0, CBRCA300C3ETS0 to C610
Added fixes for overall drive robustness

- MBD2147RC, MBD2300RC to SB1A
Added VPD changes for manufacturing
Addresses issues seen with DSA HDD Diagnostic test.

- MBF2300RC, MBF2600RC to SB25
Addresses issues seen with DSA HDD Diagnostic test.

- ST9500620SS, ST91000640SS to BD22
HUC106030CSS60, HUC106060CSS60 to D2F8
Inital Release

SATA 3.5"

- WD2502ABYS-23B7A0 , WD1602ABYS-23B7A0 to 02.03B07
Addresses firmware issues that may cause a drive to be marked defunct
prematurely under certain application workloads.

- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB14
ST3500514NS, ST31000524NS, ST32000644NS to BB28
Added enhancement for improved robustness

- WD5003ABYX-23 to WC31
Initial Release

SATA 2.5"

- WD3000BLFS-23YBU0 to 04.04V10
(Critical)
Addresses firmware issues that may cause a drive to be marked defunct
prematurely under certain application workloads.


- ST9250610NS, ST9500620NS, ST91000640NS to BE21
Initial Release

SATA 2.5" SSD

- STEC MAC8 IOPS to 2732
STEC M8PSB2 T4 to SM04
Addresses an issue installing RHEL 6.0 onto this drive.

SATA 1.8" SSD

- SG9XCS1B50GMIBM, SG9XCS1F200GEIBM to SA03SB63
Addresses rare issue where the drive may not being seen on
power up.

- STEC M8PSB1 to 0408
STEC M8PSB1 T4 to SM15
Addresses an issue installing RHEL 6.0 onto this drive.

===============================================================

Version 1.08.01
(Critical)

SAS 3.5"
Product ID FW

VPCA300900EST1 A3B8
VPCA450900EST A3B8
VPCA600900EST1 A3B8
VPBA073C3ETS11 A496
VPBA146C3ETS11 A496
VPBA300C3ETS11 A496
VPBPA300C3EST1 A529
VPA036C3-ETS10 A650
VPA073C3-ETS10 A650
VPA146C3-ETS10 A650
ST336754SS BA1A
ST373454SS BA1A
ST3146854SS BA1A
ST336754SS BA1A
ST373454SS BA1A
ST3146854SS BA1A
ST373455SS BA2D
ST3146855SS BA2D
ST3300655SS BA2D
ST373355SS BA38
ST3146755SS BA38
ST3300555SS BA38
ST3146356SS BA4C
ST3300656SS BA4C
ST3450856SS BA4C
ST3300657SS BA58
ST3450757SS BA58
ST3600057SS BA58
ST3750630SS BC1G
ST31000640SS BC1G
ST31000424SS BC26
ST32000444SS BC26
GNA073C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA300C3ESTT0Z BH0J
GNA073C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA300C3ESTT0Z BH0J
BBA036C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA146C3ESTT0Z BH0K
BBA036C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA146C3ESTT0Z BH0K
MAU3036RC S902
MAU3073RC S902
MAU3147RC S902
MBA3073RC SA08
MBA3147RC SA08
MBA3300RC SA08
MAX3036RC T907
MAX3073RC T907
MAX3147RC T907


SAS 2.5" (SFF)
Product ID FW

ST936701SS B51D
ST973401SS B51D
ST936701SS B51D
ST973401SS B51D
ST973402SS B52B
ST9146802SS B52B
ST9300603SS B53B
ST9146803SS B53B
ST9600204SS B546
ST936751SS B617
ST973451SS B617
ST973452SS B629
ST9146852SS B629
ST9500430SS BD14
CBRCA146C3ETS0 C370
CBRCA300C3ETS0 C370
CBRBA073C3ETS0 C49C
CBRBA146C3ETS0 C49C
ST9300503SS E536
ST9146752SS E625
MAV2036RC S116
MAV2073RC S116
MBB2073RC SB07
MBB2147RC SB07
MBD2147RC SB19
MBD2300RC SB19
MBC2073RC SC06
MBE2073RC SC16
MBE2147RC SC16
MAY2036RC T107
MAY2073RC T107


SATA 3.5"
Product ID FW

ST340212AS 3.05
ST380819AS 3.05
ST3160828AS 3.05
ST340014AS 3.48
ST380013AS 3.48
ST3160023AS 3.48
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB13
ST3500320NS BB13
ST3750330NS BB13
ST31000340NS BB13
ST3500514NS BB26
ST31000524NS BB26
ST32000644NS BB26
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
Hitachi HDT725025VLA3 V5DOA7CA
HUA721050KLA330 GK6OABDA
HUA721075KLA330 GK8OABDA
HUA721010KLA330 GKAOABDA
HUA722020ALA330 JKAOA3GA
HUA722050CLA330 JP2OA3GB
HUA722010CLA330 JP4OA3GB
HDS725050KLA360 K2AOAT3A
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
WDC WD2502ABYS-23B7A0 02.03B07
WD2502ABYS-23B7A0 02.03B07
WD802ABYS-23B7A0 02.03B05
WD1602ABYS-23B7A0 02.03B05
WD2003FYYS-23T8B0 01.00D04
WD2003FYYS-23W0B0 WA32
WDC WD1003FBYX-23Y7B0 WB31

SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V09
ST9160511NS BE18
ST9500530NS BE18


SATA 2.5" SSD
Product ID FW

GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
STEC MACH8 IOPS 2582

SATA 1.8" SSD
Product ID FW

STEC M8PSB1 0405


This package includes new updates to drives with product ID strings of:

SATA 3.5"

- WDC WD2502ABYS-23B7A0 and WD2502ABYS-23B7A0 to 02.03B07
Added enhanced background function to prevent premature
failure of the drive.

===============================================================

Version 1.08.00
(Critical)


SAS 3.5"

- ST373455SS, ST3146855SS, ST3300655SS to BA2D
- ST373355SS, ST3146755SS, ST3300555SS to BA38
- ST3146356SS, ST3300656SS, ST3450856SS to BA4C
- ST3300657SS, ST3450757SS, ST3600057SS to BA58
- ST3750630SS, ST31000640SS to BC1G
- ST31000424SS, ST32000444SS to BC26
(All Above Critical)
These codes addresses a rare potential for data corruption.
For this issue to occur, the drive write cache must be enabled.
For further information, please refer to retain tip H197382.

- MBA3073RC, MBA3147RC, MBA3300RC to SA08
This code corrects a firmware bug that may cause the drive to not
come ready on a cold boot.

SAS 2.5" (SFF)

- ST973402SS, ST9146802SS to B52B
- ST936751SS, ST973451SS to B617
- ST9600204SS to B546
- ST973452SS, ST9146852SS to B629
- ST9300503SS to E536
- ST9146752SS to E625
- ST9500430SS to BD14
(All Above Critical)
These codes addresses a rare potential for data corruption.
For this issue to occur, the drive write cache must be enabled.
For further information, please refer to retain tip H197382.

SATA 3.5"

- ST3500514NS, ST31000524NS, ST32000644NS to BB26

- WD2003FYYS-23W0B0 to WA32
- WDC WD1003FBYX-23Y7B0 to WB31
Initial release


SATA 2.5" SSD

- STEC MACH8 IOPS to 2582 (Critical)
Corrects firmware bug that may cause data corruption.
For further information, please refer to retain tip H197650.

SATA 1.8" SSD

- STEC M8PSB1 to 0405 (Critical)
Corrects firmware bug that may cause data corruption.
For further information, please refer to retain tip H197650.


===============================================================

Version 1.07.01
(Critical)

Added support for the following controllers:

- ServeRaid B5015 SSD Controller (46M0969)
- IBM 6Gb SSD HBA (68Y7362)

The following is a list of drives and the firmware that they will be
checked for and updated to as necessary.


SAS 3.5"
Product ID FW

VPCA300900EST1 A3B8
VPCA450900EST A3B8
VPCA600900EST1 A3B8
VPBA073C3ETS11 A496
VPBA146C3ETS11 A496
VPBA300C3ETS11 A496
VPBPA300C3EST1 A529
VPA036C3-ETS10 A650
VPA073C3-ETS10 A650
VPA146C3-ETS10 A650
ST336754SS BA1A
ST373454SS BA1A
ST3146854SS BA1A
ST336754SS BA1A
ST373454SS BA1A
ST3146854SS BA1A
ST373455SS BA2A
ST3146855SS BA2A
ST3300655SS BA2A
ST373355SS BA36
ST3146755SS BA36
ST3300555SS BA36
ST3146356SS BA4A
ST3300656SS BA4A
ST3450856SS BA4A
ST3300657SS BA56
ST3450757SS BA56
ST3600057SS BA56
ST3750630SS BC1E
ST31000640SS BC1E
ST31000424SS BC21
ST32000444SS BC21
GNA073C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA300C3ESTT0Z BH0J
GNA073C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA300C3ESTT0Z BH0J
BBA036C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA146C3ESTT0Z BH0K
BBA036C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA146C3ESTT0Z BH0K
MAU3036RC S902
MAU3073RC S902
MAU3147RC S902
MBA3073RC SA07
MBA3147RC SA07
MBA3300RC SA07
MAX3036RC T907
MAX3073RC T907
MAX3147RC T907


SAS 2.5" (SFF)
Product ID FW

ST936701SS B51D
ST973401SS B51D
ST936701SS B51D
ST973401SS B51D
ST973402SS B52A
ST9146802SS B52A
ST9300603SS B53A
ST9146803SS B53A
ST9600204SS B544
ST936751SS B616
ST973451SS B616
ST973452SS B626
ST9146852SS B626
ST9500430SS BD13
CBRCA146C3ETS0 C370
CBRCA300C3ETS0 C370
CBRBA073C3ETS0 C49C
CBRBA146C3ETS0 C49C
ST9300503SS E534
ST9146752SS E623
MAV2036RC S116
MAV2073RC S116
MBB2073RC SB07
MBB2147RC SB07
MBD2147RC SB19
MBD2300RC SB19
MBC2073RC SC06
MBE2073RC SC16
MBE2147RC SC16
MAY2036RC T107
MAY2073RC T107


SATA 3.5"
Product ID FW

ST340212AS 3.05
ST380819AS 3.05
ST3160828AS 3.05
ST340014AS 3.48
ST380013AS 3.48
ST3160023AS 3.48
WD2003FYYS-23T8B0 01.00D04
WDC WD2502ABYS-23B7A0 02.03B05
WD2502ABYS-23B7A0 02.03B05
WD802ABYS-23B7A0 02.03B05
WD1602ABYS-23B7A0 02.03B05
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB13
ST3500320NS BB13
ST3750330NS BB13
ST31000340NS BB13
ST3500514NS BB26
ST31000524NS BB26
ST32000644NS BB26
HUA721050KLA330 GK6OABDA
HUA721075KLA330 GK8OABDA
HUA721010KLA330 GKAOABDA
HUA722020ALA330 JKAOA3GA
HUA722050CLA330 JP2OA3GB
HUA722010CLA330 JP4OA3GB
HDS725050KLA360 K2AOAT3A
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
Hitachi HDT725025VLA3 V5DOA7CA


SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V09
ST9160511NS BE18
ST9500530NS BE18


SATA 2.5" SSD
Product ID FW

GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
STEC MACH8 IOPS 2366

SATA 1.8" SSD
Product ID FW

STEC M8PSB1 0404


This package includes new updates to drives with product ID strings of:

SAS 3.5"

- VPCA300900EST1, VPCA450900EST, VPCA600900EST1 to A3B8
Initial Release

- VPBPA300C3EST1 to A529
Initial Release

- ST3300657SS, ST3450757SS, ST3600057SS to BA56
(Critical)
Performance improvements under certain workloads.
Corrects a firmware bug that may cause the drive to not
come ready on a warm or cold reboot.

- ST31000424SS, ST32000444SS to BC21
Initial Release


SAS 2.5" (SFF)

- ST9300603SS, ST9146803SS to B53A
(Critical)
Performance improvements under certain workloads.
Corrects a firmware bug that may cause the drive to not
come ready on a warm or cold reboot.

- ST9600204SS to B544
(Critical)
Corrects a firmware bug that may cause the drive to not
come ready on a warm or cold reboot.

- ST973452SS, ST9146852SS to B626
Performance improvements under certain workloads.

- ST9500430SS to BD13
Performance improvements under certain workloads

- ST9300503SS to E534 and ST9146752SS to E623
Performance improvements under certain workloads.

- MBD2147RC, MBD2300RC to SB19 (Critical) Retain Tip H196899
MBE2073RC, MBE2147RC to SC16 (Critical) Retain Tip H196899
Corrects a firmware bug that erroneously reported medium
errors which may cause the drive to report PFA alerts and
in some cases be marked offline

SATA 3.5"

- WDC WD2502ABYS-23B7A0, WD2502ABYS-23B7A0, WD802ABYS-23B7A0,
WD1602ABYS-23B7A0 to 02.03B05 (Critical)
Corrects a firmware bug that may cause the drive to not
come ready on a warm or cold reboot.


- ST3500514NS, ST31000524NS, ST32000544NS to BB26 (Critical)
This code addresses a rare potential for data corruption.
For this issue to occur, the drive write cache must be enabled.
For further information, please refer to retain tip H197382.

- ST3250310NS, ST3500320NS, ST3750330NS, ST31000340NS to BB13
(Critical)
This code addresses a rare potential for data corruption.
For this issue to occur, the drive write cache must be enabled.
For further information, please refer to retain tip H197382.

- HUA722020ALA330 to JKAOA3GA
HUA722050CLA330 to JP2OA3GB
HUA722010CLA330 to JP4OA3GB
Initial Release

SATA 2.5"

- WD3000BLFS-23YBU0 to 04.04V09
(Critical)
This code corrects an additional issue where the drive may be
marked defunct.

- ST9160511NS, ST9500530NS to BE18 (Critical)
This code addresses a rare potential for data corruption.
For this issue to occur, the drive write cache must be enabled.
For further information, please refer to retain tip H197382.
Also improves performance under certain workloads.


SATA 2.5" SSD

- STEC MACH8 IOPS to 2366 (critical)
Corrects firmware bug that may cause degraded performance
and in some cases the drive may not come ready after a warm or
old boot.

SATA 1.8" SSD

- STEC M8PSB1 to 0404
Turns the default for write cache off

*******************************************

Version 1.06
(Critical)


Added support for the following controllers:

- IBM ServeRAID BR10il SAS controller v2 (49Y4731)
- IBM ServeRAID M1015 SAS controller (46M0831)
- IBM ServeRAID M5015 SAS controller (46M0829)
- IBM ServeRAID M5014 SAS controller (46M0916)

The following is a list of drives and the firmware that they will be
checked for and updated to as necessary.


SAS 3.5"
Product ID FW

VPBA073C3ETS11 A496
VPBA146C3ETS11 A496
VPBA300C3ETS11 A496
VPA036C3-ETS10 A650
VPA073C3-ETS10 A650
VPA146C3-ETS10 A650
ST336754SS BA1A
ST373454SS BA1A
ST3146854SS BA1A
ST336754SS BA1A
ST373454SS BA1A
ST3146854SS BA1A
ST373455SS BA2A
ST3146855SS BA2A
ST3300655SS BA2A
ST373355SS BA36
ST3146755SS BA36
ST3300555SS BA36
ST3146356SS BA4A
ST3300656SS BA4A
ST3450856SS BA4A
ST3300657SS BA52
ST3450757SS BA52
ST3600057SS BA52
ST3750630SS BC1E
ST31000640SS BC1E
GNA073C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA300C3ESTT0Z BH0J
GNA073C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA300C3ESTT0Z BH0J
BBA036C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA146C3ESTT0Z BH0K
BBA036C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA146C3ESTT0Z BH0K
MAU3036RC S902
MAU3073RC S902
MAU3147RC S902
MBA3073RC SA07
MBA3147RC SA07
MBA3300RC SA07
MAX3036RC T907
MAX3073RC T907
MAX3147RC T907

SAS 2.5" (SFF)
Product ID FW

ST936701SS B51D
ST973401SS B51D
ST936701SS B51D
ST973401SS B51D
ST973402SS B52A
ST9146802SS B52A
ST9300603SS B536
ST9146803SS B536
ST936751SS B616
ST973451SS B616
ST973452SS B624
ST9146852SS B624
ST9500430SS BD11
CBRCA146C3ETS0 C370
CBRCA300C3ETS0 C370
CBRBA073C3ETS0 C49C
CBRBA146C3ETS0 C49C
ST9300503SS E532
ST9146752SS E621
MAV2036RC S116
MAV2073RC S116
MBB2073RC SB07
MBB2147RC SB07
MBD2147RC SB17
MBD2300RC SB17
MBC2073RC SC06
MBE2073RC SC14
MBE2147RC SC14
MAY2036RC T107
MAY2073RC T107

SATA 3.5"
Product ID FW

ST340212AS 3.05
ST380819AS 3.05
ST3160828AS 3.05
ST340014AS 3.48
ST380013AS 3.48
ST3160023AS 3.48
WD2003FYYS-23T8B0 01.00D04
WDC WD2502ABYS-23B7A0 02.03B04
WD2502ABYS-23B7A0 02.03B04
ST3500641NS 3.AES
ST3250620NS 3.AEV
ST3500630NS 3.AEV
ST3750640NS 3.AEV
ST3250621NS 4AEV
ST3500631NS 4AEV
ST3750641NS 4AEV
ST3250310NS BB12
ST3500320NS BB12
ST3750330NS BB12
ST31000340NS BB12
HUA721050KLA330 GK6OAB4A
HUA721075KLA330 GK8OAB4A
HUA721010KLA330 GKAOAB4A
HDS725050KLA360 K2AOAT3A
Hitachi HDS721680PLA3 P21OABCA
Hitachi HDS721616PLA3 P22OABCA
HDS728040PLA320 PF1OA6EA
HDS728080PLA380 PF2OA6EA
HDT722516DLA380 V43OA9JA
HDT722525DLA380 V44OA9JA
Hitachi HDT725025VLA3 V5DOA7CA

SATA 2.5"
Product ID FW

WD3000BLFS-23YBU0 04.04V08
ST9160511NS BE16
ST9500530NS BE16


SATA 2.5" SSD
Product ID FW

GBRL0015XVECCM 4.17
GBRL0031XVECCM 4.17
GBRL0015XVEUCM 4.17
GBRLB015XVECCM 4.26
GBRLB031XVECCM 4.26
GBRLB015XVEUCM 4.26
STEC MACH8 IOPS 2269


This package includes new updates to drives with product ID strings of:

SAS 3.5"
--------------

- ST373455SS, ST3146855SS, ST3300655SS to BA2A
ST373355SS, ST3146755SS, ST3300555SS to BA36
(Critical)
This code addresses a rare potential for data corruption. For this issue
to occur, the drive write cache must be enabled. When a write is issued
while the drive write cache is enabled and a read-verify is performed
immediately afterwards, undetected data corruption can occur. For further
information, please refer to retain tip H194632.

- ST3750630SS, ST31000640SS to BC1E
ST3146356SS, ST3300656SS, ST3450856SS to BA4A
This code address an issue where the drive may report an erroneous
hardware error to the controller.

- MBA3073RC, MBA3147RC, MBA3300RC to SA07
This code improves sequential write performance under certain workloads
when write cache is turned on.

- ST3300657SS, ST3450757SS, ST3600057SS to BA52
NOTE: This is the first code release to be included in the hard drive
update package.

SAS 2.5" (SFF)

- ST973402SS, ST9146802SS to B52A
ST936751SS, ST973451SS to B616
(Critical)
These codes addresses a rare potential for data corruption. For this issue
to occur, the drive write cache must be enabled. When a write is issued
while the drive write cache is enabled and a read-verify is performed
immediately afterwards, undetected data corruption can occur. For further
information, please refer to retain tip H194632.

- MBB2073RC, MBB2147RC to SB07
MBD2147RC, MBD2300RC to SB17
MBE2073RC, MBE2147RC to SC14
CBRCA146C3ETS0, CBRCA300C3ETS0 to C370
This code improves sequential write performance under certain workloads
when write cache is turned on.

- ST9500430SS to BD11
This is the first code release to be included in the hard drive
update package.

SATA 3.5"

- WD2003FYYS-23T8B0 to 01.00D04
This is the first code releases to be included in the hard drive
update package.

SATA 2.5"

- WD3000BLFS-23YBU0 to 04.04V08
(Critical)
This code corrects an issue where the drive may generate a false PFA alert.
It also corrects an issue where the drive may be marked defunct

- ST9160511NS, ST9500530NS to BE16
This is the first code releases to be included in the hard drive
update package.

*******************************************

Version 1.05

The following is a list of drives and the firmware that they will be
checked for and updated to as necessary.

Product ID FW

ST973401SS B51D
ST936701SS B51D
ST9146802SS B52A
ST973402SS B52A
ST9300603SS B536
ST9146803SS B536
ST973451SS B616
ST936751SS B616
ST973452SS B624
ST9146852SS B624
CBRBA146C3ETS0 C49B
CBRBA073C3ETS0 C49B
MAV2073RC S116
MAV2036RC S116
MBB2147RC SB05
MBB2073RC SB05
MBD2300RC SB14
MBD2147RC SB14
MBC2073RC SC04
MAY2073RC T107
MAY2036RC T107

SAS 3.5"
VPBA300C3ETS11 A496
VPBA146C3ETS11 A496
VPBA073C3ETS11 A496
VPA146C3-ETS10 A650
VPA073C3-ETS10 A650
VPA036C3-ETS10 A650
ST3146854SS BA1A
ST373454SS BA1A
ST336754SS BA1A
ST3300655SS BA29
ST3146855SS BA29
ST373455SS BA29
ST3300555SS BA35
ST3146755SS BA35
ST373355SS BA35
ST3450856SS BA49
ST3300656SS BA49
ST3146356SS BA49
ST31000640SS BC1D
ST3750630SS BC1D
GNA300C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA073C3ESTT0Z BH0J
BBA146C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA036C3ESTT0Z BH0K
MAU3147RC S902
MAU3073RC S902
MAU3036RC S902
MBA3300RC SA06
MBA3147RC SA06
MBA3073RC SA06
MAX3147RC T907
MAX3073RC T907
MAX3036RC T907

SATA 2.5"
WD3000BLFS-23YBU0 43 04.04V05
WD1500BLFS-23YBU0 43 04.04V05

SATA 3.5"
ST3160828AS 39M 3.05
ST3160828AS 39 3.05
ST380819AS 39M 3.05
ST380819AS 39 3.05
ST340212AS 39M 3.05
ST340212AS 39 3.05
ST3160023AS 3.48
ST380013AS 3.48
ST340014AS 3.48
WDC WD2502ABYS-23B7A0 02.03B04
ST3500641NS 39M4517 39M 3.AES
ST3500641NS 39M 3.AES
ST3500641NS 39 3.AES
ST3750640NS 43W 3.AEV
ST3750640NS 43 3.AEV
ST3500630NS 39M 3.AEV
ST3500630NS 39 3.AEV
ST3250620NS 39M 3.AEV
ST3250620NS 39 3.AEV
ST3750641NS 43 4AEV
ST3500631NS 39 4AEV
ST3250621NS 39 4AEV
ST31000340NS 43 BB12
ST3750330NS 43 BB12
ST3500320NS 39 BB12
ST3250310NS 39 BB12
HUA721050KLA330 39 GK6OAB4A
HUA721075KLA330 43 GK8OAB4A
HUA721010KLA330 43 GKAOAB4A
HDS725050KLA360 39 K2AOAT3A
Hitachi HDS721680PLA380 P21OABCA
Hitachi HDS721616PLA380 P22OABCA
HDS728040PLA320 39 PF1OA6EA
HDS728080PLA380 39 PF2OA6EA
HDT722516DLA380 39 V43OA9JA
HDT722525DLA380 39 V44OA9JA
Hitachi HDT725025VLA380 V5DOA7CA

SATA 2.5" SSD
STEC MACH8 IOPS 43 2269
GBRL0031XVECCM 43 4.17
GBRL0015XVEUCM 43 4.17
GBRL0015XVECCM 43 4.17
GBRLB031XVECCM 43 4.26
GBRLB015XVEUCM 43 4.26
GBRLB015XVECCM 43 4.26



This package includes new updates to drives with product ID strings of:

SAS 2.5" (SFF)
--------------
ST9xxxx51SS to B616
ST9xxxx02SS to B52A
- This code improves the robustness of write cache operations.

ST9xxxx52SS to B624
ST9xxxx03SS to B536
- This code improves the robustness of write cache operations and sequential
write performance when write cache is enabled.
NOTE: This is the first code for the ST9xxxx52SS and ST9xxxx02SS drives to be
included in a hard drive update package. It is an update from the code
that is shipped with the drive.

MBD2xxxRC to SB14
- Initial release

SAS 3.5"
--------
ST3xxxxx6SS to BA49
ST3750630SS to BC1D
- This code improves the robustness of write cache operations.

SATA 2.5"
---------
WD3000xxxxx to 04.04V05
- Adjusted PHY setting for better signal quality margin.

SATA 2.5" SSD
--------------
STEC MACH8 IOPS to 2269
GBRL0xxxxx to 4.17
GBRLBxxxxx to 4.26
- The new firmware will correct a rare data error condition in the drives
where invalid data may be passed to the system without any error condition
flagged.

Due to the severity of this potential issue, IBM strongly recommends
applying this firmware as soon as possible.

For further information, please refer to retain tip H195663.

NOTE: This is the first code for the GBRLBxxxxx drives to be included in a
hard drive update package. It is an update from the code that is
shipped with the drive.


*******************************************

Version 1.04

The following is a list of drives and the firmware that they will be
checked for and updated as necessary.

Product ID FW

SAS 2.5" (SFF)
ST973401SS B51D
ST936701SS B51D
ST9146802SS B529
ST973402SS B529
ST973451SS B615
ST936751SS B615
CBRBA146C3ETS0 C49B
CBRBA073C3ETS0 C49B
MAV2073RC S116
MAV2036RC S116
MBB2147RC SB05
MBB2073RC SB05
MBC2073RC SC04
MAY2073RC T107
MAY2036RC T107

SAS 3.5"
VPBA300C3ETS11 A496
VPBA146C3ETS11 A496
VPBA073C3ETS11 A496
VPA146C3-ETS10 A650
VPA073C3-ETS10 A650
VPA036C3-ETS10 A650
ST3146854SS BA1A
ST373454SS BA1A
ST336754SS BA1A
ST3300655SS BA29
ST3146855SS BA29
ST373455SS BA29
ST3300555SS BA35
ST3146755SS BA35
ST373355SS BA35
ST3450856SS BA48
ST3300656SS BA48
ST3146356SS BA48
ST31000640SS BC1A
ST3750630SS BC1A
GNA300C3ESTT0Z BH0J
GNA146C3ESTT0Z BH0J
GNA073C3ESTT0Z BH0J
BBA146C3ESTT0Z BH0K
BBA073C3ESTT0Z BH0K
BBA036C3ESTT0Z BH0K
MAU3147RC S902
MAU3073RC S902
MAU3036RC S902
MBA3300RC SA06
MBA3147RC SA06
MBA3073RC SA06
MAX3147RC T907
MAX3073RC T907
MAX3036RC T907

SATA 2.5"
WD3000BLFS-23YBU0 43 04.04V04

SATA 3.5"
ST3160828AS 39M 3.05
ST3160828AS 39 3.05
ST380819AS 39M 3.05
ST380819AS 39 3.05
ST340212AS 39M 3.05
ST340212AS 39 3.05
ST3160023AS 3.48
ST380013AS 3.48
ST340014AS 3.48
WDC WD2502ABYS-23B7A0 02.03B04
ST3500641NS 39M4517 39M 3.AES
ST3500641NS 39M 3.AES
ST3500641NS 39 3.AES
ST3750640NS 43W 3.AEV
ST3750640NS 43 3.AEV
ST3500630NS 39M 3.AEV
ST3500630NS 39 3.AEV
ST3250620NS 39M 3.AEV
ST3250620NS 39 3.AEV
ST3750641NS 43 4AEV
ST3500631NS 39 4AEV
ST3250621NS 39 4AEV
ST31000340NS 43 BB12
ST3750330NS 43 BB12
ST3500320NS 39 BB12
ST3250310NS 39 BB12
HUA721050KLA330 39 GK6OAB4A
HUA721075KLA330 43 GK8OAB4A
HUA721010KLA330 43 GKAOAB4A
HDS725050KLA360 39 K2AOAT3A
Hitachi HDS721680PLA380 P21OABCA
Hitachi HDS721616PLA380 P22OABCA
HDS728040PLA320 39 PF1OA6EA
HDS728080PLA380 39 PF2OA6EA
HDT722516DLA380 39 V43OA9JA
HDT722525DLA380 39 V44OA9JA
Hitachi HDT725025VLA380 V5DOA7CA

SATA 2.5" SSD
STEC MACH8 IOPS 43 2103
GBRL0015XVECCM 43 4.14
GBRL0031XVECCM 43 4.14
GBRL0015XVEUCM 43 4.14


This package includes new updates to drives with product ID strings of:

SAS 2.5" (SFF)
--------------
CBRBAxxxxxx to C49B
- Modified VPD for JSxx Blades

MBBxxxxxx to SB05
- Fixed a performance issue when synchronizing or rebuilding an array when
used in a LSI 1064 based SAS controller.

MBC2073RC to SC04
- Fixed a performance issue when synchronizing or rebuilding an array when
used in a LSI 1064 based SAS controller.

SAS 3.5"
--------
MBAxxxxxx to SA06
- Fixed a performance issue when synchronizing or rebuilding an array when
used in a LSI 1064 based SAS controller.

ST3xxxxx6SS to BA48
- This code addresses a rare potential for data corruption. For this issue
to occur, the drive write cache must be enabled. When a write is issued
while the drive write cache is enabled and a read-verify is performed
immediately afterwards, undetected data corruption can occur. For further
information, please refer to retain tip H194632.

ST3750630SS to BC1A
- This code addresses a rare potential for data corruption. For this issue
to occur, the drive write cache must be enabled. When a write is issued
while the drive write cache is enabled and a read-verify is performed
immediately afterwards, undetected data corruption can occur. For further
information, please refer to retain tip H194632.
- Fixes a hang condition during failover operation on a BladeCenter-S
chassis with an RSSM controller.

BBAxxxxxx to BH0K
- Fixed an issue where a drive may prematurely report a PFA trip.

GNAxxxxxx to BH0J
- Fixed an issue where a drive may prematurely report a PFA trip.

SATA 3.5"
---------
ST31000340NS, ST370330NS, ST3250310NS, ST3500320NS to BB12
- This code addresses a rare potential for data corruption. For this issue
to occur, the drive write cache must be enabled. When a write is issued
while the drive write cache is enabled and a read-verify is performed
immediately afterwards, undetected data corruption can occur. For further
information, please refer to retain tip H194632.
- This code addresses a rare potential for data loss. After a power cycle,
the drive will no longer be available and becomes unresponsive. Data will
become inaccessible due to the drive not responding. For further
information, please refer to retain tip H194623.

WDC WD2502ABYSxxxxx to 02.03B04
- Fixed incorrect VPD data.

SATA 2.5"
---------
WD3000xxxxx to 04.04V04
- Fixed a Critical issue - IBM recommends a backup of the data on the drive
before attempting to update the firmware. This is a fix for an issue
where data required for spin up of the drive may be overwritten, rendering
the drive inoperable on a subsequent warm or cold system reboot.
- Fixed a bug with an internal timer that may cause a drive to go offline
when used in a non-RAID environment.

SATA 2.5" SSD
-------------
STEC MACH8 IOPS to 2103
- Initial Release


*******************************************

Version 1.03

Added the capability to update SAS and SATA drives online under Windows or
Linux. This capability is only supported if the drives are attached to one
of the following SAS adapters:
- IBM ServeRAID MR10k SAS Controller
- IBM ServeRAID MR10i SAS Controller
- IBM ServeRAID MR10M SAS Controller
- IBM ServeRAID MR10il SAS Controller
- IBM ServeRAID MR10is SAS Controller
- MegaRAID 8480 SAS Controller
- IBM ServeRAID BR10i SAS Controller
- IBM ServeRAID BR10il SAS/SATA Controller
- IBM SAS HBA
- IBM SAS Expansion Card (CFFv) for IBM BladeCenter
- IBM SAS Connectivity Card (CFFv) for IBM BladeCenter
- Onboard LSI 1064 SAS controller (2MB only)
- Onboard LSI 1068 SAS controller
- Onboard LSI 1078 SAS controller

This package includes new updates to drives with product ID strings of:

SAS 2.5" (SFF)
--------------
ST9146802SS, ST973402SS to B529
- Added support for JS2x Blades in a BladeCenter-S chassis.
- Picked up the latest network roll of firmware fixes to address some
unexpected system hangs.

ST936751SS, ST973451SS to B615
- Added support for JS2x Blades in a BladeCenter-S chassis.
- Picked up the latest network roll of firmware fixes to address some
unexpected system hangs.

CBRBAxxxxxx to C495
- Initial release

MBBxxxxxx to SB04
- Initial release

MBC2073RC to SC03
- Initial release

SAS 3.5"
--------
VPBAxxxxxx to A496
- Added support for JS2x Blades in a BladeCenter-S chassis.

ST3146855SS, ST3300655SS, ST373455SS to BA29
- Added support for JS2x Blades in a BladeCenter-S chassis.
- Picked up the latest network roll of firmware fixes to address some
unexpected system hangs.

ST3450856SS to BA47
- IBM was notified by our vendor that there is a defect in a level of
firmware used in the IBM 450GB 15K SAS 3.5" HS HDD (PN 41Y8454) in option
42D0519, which under certain conditions may lead to data being written or
read back incorrectly on the drive. IBM has worked closely with the
vendor to identify the problem and developed a firmware fix to resolve the
problem. Customers should upgrade to firmware level BA47.

MBAxxxxxx to SA05
- Initial release

ST3750630SS to BC17
- Initial release

SATA 3.5"
---------
ST3250620NS, ST3500630NS, ST3750640NS to 3.AEV
- Initial release

ST3250621NS, ST3500631NS, ST3750641NS to 4AEV
- Initial release

ST31000340NS, ST3750330NS, ST3250310NS, ST3500320NS to BB10
- Initial release

HUA721050KLA330, HUA721075KLA330, HUA721010KLA330, to AB4A
- Initial Release

SATA 2.5" SSD
-------------
GBRL001xxx, GBRL0031xxx to 4.14
- Corrects intermittent hangs during operations.

*******************************************
ibm_fw_hdd_sas-1_12_01_linux_32-64_chg

BladeCenter HS22/HS22V UEFI Flash Update
Version 1.20 (BuildID P9E159A)
Change History

Version 1.20 - BuildID: P9E159A - Critical
-------------------------------------------------
Problem(s) Fixed:
- Updated README for new year 2013

Enhancements:
- Added confirmation message for Reset System option
- Intel Memory Reference Code Release 2.50
- Improved handling of memory in high stress application/usage


Version 1.19 - BuildID: P9E158A - Critical
-------------------------------------------------
Problem(s) Fixed:
- Fixed DIMM manufacturer for Netlist show unknow in pDSA
- Fixed BladeCenter Open Fabric Manager (BOFM) Mac address problems
- Fixed BladeCenter Open Fabric Manager (BOFM) not applied intermittently
- Fixed TPM Logo for Windows 2012
- Fixed intermittent problem booting pDSA image

Enhancements:

Version 1.18 - BuildID: P9E157A - Critical
-------------------------------------------------
Problem(s) Fixed:
- Limited Admin Access within F1

Enhancements:
- Intel Memory Reference Code Release 2.40
- Added Limit Boot Attempts ported

Version 1.17 - BuildID: P9E156C - Critical
-------------------------------------------------
Problem(s) Fixed:

Enhancements:
- Upgraded SMBIOS type 9 and type 41 to version 2.6.
- Added SMBIOS type 11 structure to support slot group/bus/device/function information.
- Intel Microcode Update SRV_P_108

Version 1.16 - BuildID: P9E155B - Critical
-------------------------------------------------
Problem(s) Fixed:
- The second MAC address for the onboard NIC's reported by the AMM may
be incorrect when BPE4's, BGE's or any other expansion device is
connected to the Blade.

Version 1.15 - BuildID: P9E155A - Critical
-------------------------------------------------
Problem(s) Fixed:
- Fixed Corrupted iSCSI Attempt List issue
- Fixed iSCSI boot issue
- Address a potential issue relating to direct device assignment
in Intel Virtual Technology application
- Fixed Recalibrating System Power issue with Broadcom 10Gb
Ethernet CFFh Expansion Card

Enhancements:
- Error message reported by the iMM for uncorrectable DIMM error
during POST has changed to memory scrub error.
- F1 Network page update: categrized consistent MAC notation
- Added BOFM 4.2 support for Mellanox BladeCenter Ethernet Adapter
- Intel Westmere B_1 Microcode Update SRV_P_100
- Intel Memory Reference Code Release 2.30
- Added CRTM Information at Setup Menu

Version 1.14 - BuildID: P9E153B - Critical
-------------------------------------------------
Problem(s) Fixed:
- Westmere:No LEDs or Logs from CPU Type Mismatch
- Fixed NoSnoop BEST card test for the BGE.
- Fixed a issue with fully populated HS22 with 8 Fusion I/O cards.
- Clarify the HELP text for Load Default Settings in F1 SETUP.
- Clarify the HELP text for several F1 SETUP settings for Memory,
Processors and Operating Modes.

Enhancements:
- Added infinite boot loop option in F1 SETUP for legacy.
- Support for IPv6 in Pre-Boot environment.
- Added Chipset based interrupt round robin scheme feature.
- Added F1 SETUP setting for IPv6 Enable/Disable.

Limitations:
- For IPv6 PXE booting, contact your OS vendor.
- For other IPv6 issue's or restrictions, look on the IBM WEB
site for RETAIN tips.

Version 1.13 - BuildID: P9E151C - Critical
-------------------------------------------------
Problem(s) Fixed:
- Downgrade Memory Reference Code from 2.21 to 2.11 for PSOD issue's.

Version 1.12 - BuildID: P9E151B - - Critical
-------------------------------------------------
Problem(s) Fixed:
- Fixed memory multi-bit error event can't be deasserted after re-enable.
- Fixed IMM Network Settings have not been saved if reset iMM immediately.
- Disable propagation of Intel VT-d faults as fatal errors to avoid guest
VM to cause the entire system to crash.
- Fixed IMM backup flashing behavior is misleading.
- Fixed bus error occurred when BOFM is applied.
- Fixed Firmware progress Hang Error when booting to iSCSI.
- Fixed hang when updating FLASH from version 1.03 or 1.04 directly to
version 1.11.

Enhancements:
- Add Support for Enable/Disable VT-d feature.
- Add support for user setting of 3x BOOT fail parameters.

Version 1.11 - BuildID: P9E150C - Critsit Build
-------------------------------------------------
Problem(s) Fixed:
- Add work-around to address NMI/PCI Error due to VT-d problem.

Version 1.11 - BuildID: P9E150B - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- Fix HS22V 16GB DIMMs SMBIOS test.
- Update VPD extraction from iMM to strip trailing blanks from buildid.
- Fix BOFM only applied to first MAC of combo card in AMM.

Enhancements:
- Add Out-of-band PXE Configuration.
- Renaming of output files to add version information.
- Re-enable disabled DIMM while AC Power Cycle.
- F1 Setup Event Log number change.
- Update Intel Westmere CPU microcode to version 0x00000013.
- Add F1 setup option to Enable/Disable ASPM capability.

Version 1.10 - BuildID: P9E149A - Critical
-------------------------------------------------
Problem(s) Fixed:
- Misc errors in boot order management.
- Modify the Tcontrol for the 130W CPU support.
- Fix PXE settings cannot be saved under uEFI.

Enhancements:
- Add support for 4 BPE4s
- Update Intel Westmere Memory Reference Code to V2.21.
- Update Intel Westmere QPI Reference Code to V1.85.
- Add F1 SETUP selection for IMM IP6 support.
- Add support for vNIC to BoFM
- To correct an IntelR XeonR 5600 series processor's internal circuit
marginality issue, that could cause false memory errors when the
C6-state is enabled.

Version 1.09 - BuildID: P9E148A - Critical
-------------------------------------------------
Problem(s) Fixed:
- prevent boot failure and reset on bogus boot order
- Correct defects in PXE support
- Fixed issue where UEFI SYSTEMS WITH HBA AND > 2 TB LUN MAY HAVE DATA ERRORS
Please refer to RETAIN tip number: H16222 or MIGR-5084554 for additional details

Enhancements:
- Add BPE4 support
- Add support for Westmere memory sparing mode
- Add support for Intel 130W processor

Version 1.08 - BuildID: P9E146C - Critical
-------------------------------------------------
Problem(s) Fixed:
- Update Intel 56xx Processor Microcode to version 0x0000000C
- Fixed issue where the system can hang following a UEFI flash,
due to a numeric configuration setting getting corrupted
when the new UEFI image no longer supports the value.
- Fixed issue where boot order selection is not saved.
- Fixed issue when power applied creates loss of connection to NSSM/RSSM.

Enhancements:
- Allow disabling of Intel 56xx Processor Data Reuse Optimization
feature to improve performance for Enterprise workloads (settable
by Advanced Setup Utility (ASU) only)

Version 1.07 - BuildID: P9E146A - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- legacy iSCSI Boot error when IQN > 72 characters
- Turbo mode does not work in UEFI 132
- Processor Turbo mode does not work in core build 1.32
- UEFI displays "Event Log Cleared" for iMM "SEL Almost Full"

Enhancements:
- Update Intel Framework Code to Release 8.6.4.1.W1.0
- Update Intel Nehalem/Westmere Reference code to P2.50
- Update processor core count settings for Westmere processors
- Add support for Westmere 1.5V Memory Strategy
- Add xSEC support for Westmere processors
- Update FPM parameters for Westmere processors
- Update CLTT settings for HS22V
- Update Intel Westmere Memory Reference Code to V2.11

Version 1.06 - BuildID: P9E132A - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- General
* Hang during legacy PXE boot when MAC address is disabled in PXE configuration
* PXE VLAN settings do not persist across boot cycles
* Improve help text for ondoard device settings
* Early video shuts down during POST
* SAS topology was ignored when it was available
* VPD string content was not consistent across boot system firmware releases
- Memory RAS
* Incorrect DIMM is called out for double bit error in mirrored mode
* 2DPC 8GB Qualified DIMMs display inconsistently in Setup
* SMBIOS Type 17 structure displays 10 memory banks

Enhancements:
- Updrade TianoCore EDK support to version 1.05.05
- Upgrade Broadcom NIC driver support to version T.5.0A.3.1
- Improve reliability of legacy AHCI/SWRAID support
- Setup
* Allow L1 power state to be disabled to improve system performance
* Allow 2DPC support to be enabled from ASU


Version 1.05 - BuildID: P9E131A - Critical
-------------------------------------------------
Problem(s) Fixed:
- General:
* Blade does not read Blade Center bay data correctly
* Advanced Energy Management (AEM) minimum power value is too low
* On-board video fails during some legacy mode operations under UEFI
* Storage daughter card is not properly recognized by system
* On-board storage controller is not disabled when storage daughter
card is installed
- POST:
* Hang during early POST (PEI) initialization
* Hang during POST when power cycling systems
- SMBIOS:
* Invalid change in SMBIOS structure data occurs over AC power cycles
* SMBIOS blade specific information is missing tables
- USB:
* May not be able to boot a fixed disk in a USB enclosure
* Miscellaneous problems when booting from legacy USB devices
- Setup:
* Power restore policy is not reset to default setting properly
* SEL event log display shows incomplete BMC sensor events
* Change Boot Order does not operate correctly
* C-states are exposed to OS when package limit is less than C-state
* Miscellaneous errors/clarifications in help text
* Administrative password dialog accepts 5 letter passwords
* Advanced Setup Utility (ASU) is unable to update iSCSI.MacAddress parameter
- pDSA:
* Unable to boot when a Sandisk USB key is installed
* Memory test only reports the first 256 correctable errors

Enhancements:
- Improve early (PEI) video support for console messages
- Enable early power-on support for IMM (requires future IMM update)
- Improve DIMM SMBUS recovery mechanism to prevent possible bus hangs and loss
of access to DIMM(s) during memory initialization.
- Setup:
* Allow disablement of legacy USB 2.0
* Allow disablement of Broadcom onboard NIC 2
* Add support for controlling UEFI PCI Option ROM execution


Version 1.04 - BuildID: P9E130A - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- Boot Selection/Manager:
* System hangs upon entering 'Start Options'
* Boot list disappeared after deleting a WOL boot item
- Power Management:
* An error in thermal throttling algorithm which reduced system efficiency
* An error in power throttling tables that prevented operation at 100% power
- RAS:
* CRTM error messages had no useful description text
* No indication of booting with a non-production signed CRTM build
* No usable memory causes system to reset and execute POST repeatedly
* Multiple error events were logged for single-bit error injected into the OS
* System reported a 'Failed to boot 3 times' error when a power loss
occurred after a Wake-On-Lan (WOL) boot request
* System was forced to go into setup after a 'Failed to boot 3 times'
error instead of booting with default values.
* When an ABR condition occurred, the backup image failed to display the
'F3' option to switch back to the primary image.
* System Event Log (SEL):
+ Unable to display a full SEL
+ Invalid event descriptions in SEL
+ System hung when attempting to view SEL
+ Empty Extended Service Data records when injecting multi-bit memory errors into OS
- Setup:
* PCIeGenSelection setup menu setting had no effect
* HyperThreading Enable setup menu setting had no effect
* Processor C3/C6 power mode settings were coupled together incorrectly
* When enabling DIMMs, there is no prompt to save settings before exiting
* UEFI network boot dialog did not work properly
* Initial display of 'Adapters and UEFI Drivers' did not auto refresh
* Incorrect Processor options display when setting power performance modes
* iSCSI CHAP password lenghts of 12 caused problems in the Setup browser.
* Incorrect/misleading help text descriptions
* Miscellaneous typographic errors and incorrect/misleading prompts/help text
- Advanced Setup Utility (ASU):
* Display of Devices and Option ROMs contained many unused entries
* iSCSI parameter updates from ASU failed when an IP address setting
specified an invalid value.
* Error when chaining boot sequences in AMM/IMM via ASU
* Firmware update utility could cause corruption of the firmware package
- Miscellaneous:
* ACPI:
+ IBFT table contained erroneous information
+ Processor C-State information was not visible
+ P-States Table (_PSD) reported incorrect/invalid information to the OS
* BOFM
+ Boot performance was poor
+ Failed to map the second port on an LSI storage controller
+ System hung during POST with a BPE3 Expansion unit attached
* Network
+ When booting with iSCSI interface, system would not login to SAN unit
+ A PXE function could respone with a failure when there was no problem
* USB:
+ Legacy USB SMI handler caused system to hang during POST
+ Legacy booting of USB storage device based on Setup settings did not work
+ System failed to recognize and/or boot from some USB storage devices
+ Legacy USB devices were not always stable
* System had no video when booting with multiple add-in video adapters
* Microsoft WLK Test Kit 1: WHEA Test failed

Enhancements:
- Setup:
* Allow user to:
+ Select number of active cores in a CPU package (1/2/4)
+ Select PCIe Gen1/Gen2 configuration per slot (add-in options only)
+ Enable/disable onboard CDROM/DVD device
+ Enable/disable ACPI C2 (CPU C3) state
+ Enable/disable CPU prefetch setting
* Improve 'look and feel'
- Support:
* Real Time OS (RTOS) in System Maintenance Manager (SMM)
* Keyboard/mouse devices on legacy USB 2.0 controller
* BladeCenter Open Fabric Manager (BOFM) on Converged Network Adapter (CNA)
daughter card
* BPE3 Expansion Unit
* Two DIMMs/channel @ 1333 MHz (qualified DIMMs only)

- Update Intel UEFI/PIA Reference Code to version 8.6.4.P1 Thurley 1.0
- Update SMBIOS Type 11 strings with addition descriptive text
- Update memory PFA conform with internal standards

Limitations:
Dependencies:

Version 1.03 - BuildID: P9E126B - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- Correct abnormalities in SOL display when running pre-boot Diagnostics
- Correct errors in the display of SEL error entries
* Incorrect descriptions for IPMI error entries
* Display of SEL full message when SEL is not full
- Errors when PXE booting with a SAS adapter card installed in the system
- Missing help text for Setup IMM configuration
- Correct video display problem when installing SLES 11
- Correct a problem setting Setup PackageCState option via ASU
- Force reservation of SATA/IDE interrupt even if no hard drive is installed
- Add RTOS table to CSM EBDA to support RTOS
- Correct improper handling of an interrupt shared with an IDE device interrupt
- Correct inability to set 'Physical Presence' for TPM updates

- Update the PXE TFTP_GET_FILE_SIZE API interface to return a proper size
value instead of a 'load error' response
- Correct a problem in which WOL boot options could not be configured
- Correct inconsistent text displayed for some SEL messages
- Fix an error reporting prioblem in which PCIe errors in some slots were
not being reported.
- Correct text errors in security information panel displays
- Correct simultaneous display of BDS hot keys and password dialog
- Correct a problem where boot order information from ASU was not being
accepted
- Correct a program exception which occurred during boot option configuration
- Correct a CSM problem in which the network option ROM is being called with
an invalid parameter
- Correct a problem with Legacy option ROMs on Blade Expansion Cards using multiple
busses. Added an option for "Blade Expander Card B2" (bus #2) when a dual bus
card is attached.
- Correct a situation where on-board ethernets 1 & 2 are disabled or enabled together.
The ports cannot be disabled or enabled individually.If one is disabled, then both
will be disabled in h/w. To enable either port, both must be enabled.

Enhancements:
- Update Intel CPU microcode to release 0011
- Update Intel QPI/Memory Reference Code to release 1.05
- Add setup options to support selection of system power profiles
- Add setup option to allow disablement of USB 2.0 support
- Add basic video support during PEI boot phase
- Update memory error handling support for Pre-boot Diagnostics
- Add WHEA error log support

- Improve reliability of memory configuration updates

Limitations:
Dependencies:

Version 1.02 - BuildID: P9E124A - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- FLASH utility (iflash, lflash, wflash) problems which caused:
* an error 15 when updating host system firmware to a previous
level of the firmware.
* the MEM and CNFG error lights to be turned on after an update
- The default setup value for an iSCSI option was invalid
- An SMBIOS table problem which caused the Windows HCT to fail
- Interrupt routing was not valid for VMWARE 4.0
- Erroneous disablement of some DIMM's during POST.
- Sub-optimal setting for chipset control parameters
- USB errors when installing Windows 2003
- Errors when using SOL to view the IMM System Event Log
- Legacy (CSM) iSCSI does not support all defined boot attempts
- Failure to report ACPI/WHEA messages after fatal PCI errors
- Errors when reading DVD media for some drive/media combinations
- Long delay at splash screen during POST when iSCSI DHCP enabled
- missing ACPI IBFT table entry when booting a legacy OS

Enhancements:
- Enable user control of USB-EHCI enabling via ASU
- Improve system security:
* Lock SMRAM for updates after POST
* Update settings for chipset SMRAM control registers
- Improve RAS support:
* Improve DIMM error handling
* Automated disabled DIMM recovery
* Add error messages for PCI option ROM errors
* Improve IMM SEL display presentation
* Enable error reporting for chipset thermal alerts
- Increase available high Post Memory Manager (PMM) space
- Update onboard Broadcom 5709 UEFI driver to level 4.6.35

Limitations:
Dependencies:


Version 1.01 - BuildID: P9E123C - Suggested (Be aware to check the change history for any critical updates)
-------------------------------------------------
Problem(s) Fixed:
- Miscellaneous errors associated with the SMBIOS tables
Type 17 structure bank locator field (memory DIMM location)
Primary/Backup build ID reporting
Miscellaneous typographical/formatting errors
- Typographical/formatting errors in the ACPI IBFT table
- Premature request for POP/PAP password(s) during POST
- Hang problem encountered when processing some PCI errors
- Hang problem which occured with older LSI adapter firmware drivers
- Error reporting/display for some types of globaal error records
- Miscellaneous typographical/formatting errors in Setup
- Reporting of an incorrect wake-up source during POST
- Incorrect display of an LSI RAID popup menu during POST
- Missing system reset after some Setup changes which require a reset
upon exiting Setup
- Improper reporting/display of a type 1E POST error when none existed
- Loss of console video display during POST legacy option ROM installation
- Improper setting of iSCSI parameters remotely via ASU
- Failure to update TPM state display after making a Setup change

Enhancements:
- Updated Intel memory reference code to version 1.03
- Updated memory thermal throttling parameters
- Updated Setup parameters to include processor prefetch settings
- Improved Page-Up/Page-Down processing for the remote console
- Improved iSCSI parameter validation algorithm
- Improved Configuration and FLASH update documentation
- Improved serial port hardware flow control

Limitations:
Dependencies:


Version 1.00 - BuildID: P9E121B (Initial Release)
-------------------------------------------------
Problem(s) Fixed:
Enhancements:
Limitations:
Dependencies:


ibm_fw_uefi_p9e159a-1_20_anyos_i386_chg

===============================================================================
Emulex Firmware Package
===============================================================================

Firmware Version: 4.2.433.3

Problems Fixed:

- Intermittent link status with IBM Virtual Fabric Switch when set to IBM
Virtual Fabric Mode
- The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from
OneCommand Manager. This selection is available in UEFI F1 setup.
- Under high network stress, NMI errors can be seen with x3690 X5 and x3850 X5
- 10GbE ports running at 1GbE speed 10% below wirespeed at certain block sizes.
- Unable to perform PXE boot with LPVID assigned to vNIC interface
- 1Gb ports of HS23 do not handle tagging properly if multichannel mode
enabled (pnic ok). Note: ESX driver patch also required.
- Port flapping link after FW upgrade and "reboot" when connected to 10Gb PTM
module (DAC)

Interoperability Since Previous Release:

- Support for Emulex Virtual Fabric Adapter Advanced (BE2) for IBM
BladeCenter
- Support for Emulex Virtual Fabric Adapter (BE2) for IBM BladeCenter
- Support for Emulex Virtual Fabric Adapter (BE2) for IBM System X

Known Issues:

- All 10Gb KX4 ports must be used with 10Gb switches. They will not link at
1Gb. This applies to HS23 LOM and IBM BladeCenter VFA adapters only.
- IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456

===============================================================================

Firmware Version: 4.2.412.0

Problems Fixed:

- All VFS on Port 1 on optional Card unreachable from outside the host (x3750
M4)
- 'Logical Admin Link' not enabled after applying BOFM in Switch Agnostic mode
- IBM pre-boot Diagnostics NIC physical loopback test fails in Command and
GUI mode
- Multiple cosmetic issues with iSCSI UEFI BIOS
- 10Gb ports do not detect 'Link Down' with some switches
- 1Gb ports on HS23 LOM not able link up with IBM ICPM (FRU part 44W4486) in
BCS chassis
- Performance issues with specific DAC cables and SND top of rack switch

Interoperability Since Previous Release:

- UEFI 2.3.1 Compliance
- Increased VF count in SR-IOV (was 16 VFs per port, is now 32 VFs per port)
- Support for next generation 10GbaseT PHY
- Expose IBM Feature On Demand licensing information in UEFI configuration
utility

Known Issues:

- All 10Gb ports must be used with 10Gb switches. They will not link at 1Gb.
- IPv6 IP address not visible via IMM GUI for IBM Option 90Y6456
- Intermittent link status with IBM Virtual Fabric Switch when set to IBM
Virtual Fabric Mode
- The option to enable/disable SRIOV on HS23 LOM Port 0 is missing from
OneCommand Manager. This selection is available in UEFI F1 setup.

===============================================================================

Firmware Version: 4.1.455.6

Problems Fixed:

- Fixed an issue where ASIC randomly hangs losing network connectivity
when certain commands are sent from the host. Resulting behavior
varies between OS's (Yellow bangs in Windows, PSOD in VMWare)
- PHY Loopback fails on 10G ports
- UE and hang on LOM or Robalo when powering off Janice in UEFI or PXESelect
- Loopback on HS23 now functional in DSAp
- DCBX does not converge with firmware on a FCoE fabric
- Control C Broken on BE2
- 7 second delay in GET_CARD_ATTRIBUTES command
- Emulex VF adapter FCoE link lost on VMware 5.0
- flow control set for 10G Base T phys for autonegotiation
- Dynamic link update is not working with NIC UEFI driver
- Remove unused definitions in UEFI NIC
- Emulex driver expects that the Login Options field be zero
- "map r" displays a iSCSI BLK device when no LUNs presented
- "X/x Exit without save" does not work as expected
- Display proper description as part of EFI Driver Model Related Information
- Intermittent "Configuration changed. reset to apply it now?"
- Garbled output being displayed at the LUN configuration section.
- All Emulex Configuration settings get lost after a reset
- Perform additional checks when no Luns are mapped to the target
- CHAP name only accepts 6 to 10 characters
- Hii ???iSCSI Initiator Configuration??? showing old version screen
- iSCSI name is case sensitive
- iSCSI HII allows user to select first 8 LUNs as bootable.
- iSCSI Boot Enable/Disable option should be port specific
- LUN Configuration shows LUN 0, even if no LUNs presented to initiator.

Interoperability Since Previous Release:

- Support for Emulex Virtual Fabric Adapter Advanced (CFFh, 2+2) for IBM
BladeCenter

===============================================================================

Firmware Version: 4.1.334.47

Problems Fixed:

- NCSI transmit workaround for IBM
- Issues with data reporting when BOFM enabled
- Improved network performance throughput
- Issues with IBM Management network performance
- Logical link status for IBM mezz card shown as 'N/A'
- Serial Over LAN fails when more than one blade installed with a single
switch
- Removed UEFI menu items for unsupported functions on a port
- Issues with diagnositics in virtual NIC/UMC mode
- Issues with MAC and PHY loopback on OneConnect devices
- Several issues with FCoE on some OEM fabric switches

Interoperability Since Previous Release:

- Support for HS23 Virtual Fabric LAN on Motherboard
- Support for VFA III (95Y3762, 95Y3768), 90Y6456
- Support for IBM's Features on Demand (FOD)
- Formal support for SR-IOV

===============================================================================

Firmware Version: 4.0.1062.0

Problems Fixed:

- iLab Tucson - lpfc Device Resets and path failures continue after error
inject.
- Writes do not complete when running LIP test on BE3 port 2
- IPV6 implementations no longer experience an unrecognized routing type
error.
- VLAN tagging is now disabled on the OneConnect UCNA when multichannel is
disabled.
- UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect
10102-based UCNA.
- OneConnect UCNAs no longer send and receive only double-tagged packets
and discard all other packets.
- PHY, MAC, and External loopback tests no longer fail on all platforms.
- Firmware now returns the proper OneConnect UCNA model number.
- IPV6 implementations no longer experience an unrecognized routing type
error.
- Installing Windows 2008 or Windows 2008 R2 on remote iSCSI disks no
longer causes the system to hang.
- Issues no longer occur when resetting a server configured for multipathing
on VMware ESX systems.
- VLAN tagging is now disabled on the OneConnect UCNA when multichannel is
disabled.
- UEFI/BIOS-assigned LPVIDs now function properly on the OneConnect
10102-based UCNA.
- OneConnect UCNAs no longer send and receive only double-tagged packets and
discard all other packets.
- An adapter hardware error no longer occurs when running I/O with LUNs on
x86 platforms.
- Changing from Convergence Enhanced Ethernet (CEE) to Chassis Internal
Network (CIN) and then rebooting no longer fails to link-flap (CIN Fabric
Login (FLOGI) now occurs).
- PHY, MAC, and External loopback tests no longer fail on all platforms.
- Firmware now returns the proper OneConnect UCNA model number.
- DCB settings can now be configured.
- (iSCSISelect) When enabling DHCP for an iSCSI initiator, the Emulex iSCSI
Network Configuration utility now waits approximately 20 seconds to make a
DHCP connection before returning control.
- (FCoE BootBIOS) FCF CEE parameters for Boot from SAN configuration are now
saved properly.

Interoperability Since Previous Release:

- Added support for switch-independent multichannel mode.
- Added support for IBM Virtual Fabric 10Gb RackSwitch firmware 6.8.1.0.
- Added support for IBM Virtual Fabric 10G Switch Module firmware 6.8.1.0.
- Added support for Fibre Channel over Ethernet (FCoE) on rack systems.
- Added support for iSCSI hardware offload on rack systems.
- Added support for Cisco Nexus 5000-series switches.

===============================================================================

Device Driver Version: 2.103.397.3806 (Blade) / 2.103.269.31 (Rack)

- Initial Release

===============================================================================

elx_fw_cna_ibm1206-4_2_433_3-1_linux_32-64_chg

===============================================================================
Emulex FC/FCoE Device Driver for Linux
===============================================================================

Device Driver Version: 8.3.5.86

Problems Fixed:
- Kernel panics with FCoE on HS23 in SLES 11.2 x86_64. Also requires a SLES11.2 kernel update
- FLOGI sent with Class 2 in-order bit set when Class 2 is set as unsupported class of service

Interoperability since previous release:
- RHEL6.3 GA Kernel

Known Issues:
- No known issues

===============================================================================

Linux FC/FCoE Driver Version 8.3.5.74.1p

Problems Fixed:

- Fixed kernel panic after scsi_eh escalation by checking the proper
return status

===============================================================================

Linux FC/FCoE Driver Version 8.3.5.74

Problems Fixed:

- Fixed system crash due to not providing SCSI error-handling host
reset handler
- Debug helper utility routines for dumping various SLI4 queues
- Fix unsol abts xri lookup
- Fixed issues with LPe16000 to LPe16000 discovery
- Fix driver crash during back-to-back ramp events
- Reregister VPI for SLI3 after cable moved to new Saturn port
- Fix log message 2597 displayed when no error is detected
- Fixed FCP LOG for easier Finisar trace correlation
- Fix kernel panic when going into to sleep state
- Fix error message displayed even when not an error
- Fix Read Link status data
- Fix unable to create vports on FCoE SLI4 adapter
- Fix initiator sending flogi after acking flogi from target
- Fix the case where an array controller does not apply FCP
priority rules
- Added support for handling SLI4-port XRI resource-provisioning
profile change
- Change default DA_ID support from disabled to enabled
- Fix bug with driver unload leaving a scsi host for a vport around
- Update copyright date for files modified in 2012
- Fix compilation errors on some kernels due to debugfs
variable definitions.
- Used PCI configure space read to flush PCI function reset
register write
- Fixed system panic when extents enabled with large number of
small blocks
- Fixed system panic during EEH recovery
- Fix resource leak when acc fails for received plogi
- Fix SLI4 driver module load and unload test in a loop crashes
the system
- Fix missing CVL event causing round-robin FCF failover process
to stop
- Fix deadlock during adapter offline request
- Fix same RPI registered multiple times after HBA reset

===============================================================================

Linux FC/FCoE Driver version 8.3.5.66

Problems Fixed:

- Fix SLI4 driver module load and unload test in a loop crashes
the system
- Fix missing CVL event causing round-robin FCF failover process
to stop
- Fix deadlock during adapter offline request
- Fix same RPI registered multiple times after HBA reset
- Fix driver handling of XRI Aborted CQE response
- Fixed port and system failure in handling SLI4 FC port function
reset
- Fix bug with driver not sending a LOGO with vport delete
- Make BA_ACC work on a fully qualified exchange
- Fix for SLI4 Port delivery for BLS ABORT ACC
- Fix KERNEL allocation while lock held
- Incorrect usage of bghm for BlockGuard errors
- Fix warning on i386 system
- Fix ndlp nodelist not empty wait timeout during driver
unloading
- Fix mailbox and vpi memory leaks
- Support character device to take a reference on the driver
- Fix for FDISC failures after firmware reset or link bounce
- Support debugfs for injecting T10 DIF errors
- Fix SLI4 BlockGuard behavior when protection data is generated by
HBA
- Fix for driver using duplicate RPIs after 16Gb/s adapter
port reset
- Fix discovery problem when in pt2pt
- Fixed failure in handling large CQ/EQ identifiers in an IOV
environment
- Fix Locking code raises IRQ twice
- Fix driver not returning when bad ndlp found in abts error event
handling
- Support more driver logs in area of SLI4 port error attention and
reset recovery
- Fix bug with driver returning the wrong ndlp
- Sync up with actual upstream lpfc driver code
- Support SLI4 16Gb FC Adapter support for T10 DIF / BlockGuard
- Merge from upstream: scsi: Fix up files implicitly depending on
module.h inclusion
- Fix driver behavior when receiving an ADISC
- Fixed unbounded firmware revision string from port caused the
system panic
- Fix bug with driver processing dump command type 4 using 16Gb FC
Adapter
- Fix driver does not reset port when reset is needed during
fw_dump
- Fix ELS FDISC failing with local reject / invalid RPI
- Changed SLI4 FC port internal loopback from outer serdes to inner
internal
- Fix REG_RPI fails on SLI4 HBA putting NPort into NPR state
- Fix bug with driver processing an els command using 16Gb FC
Adapter
- Fix NMI seen due to CQE starvation
- Fixed SLI4 FC port obtained link type and number dependent on
link connection
- Fixed SLI4 FC port internal loopback without SFP and external
link/loopback plug
- Fix driver incorrectly building fcpCdb during scsi command prep
- Fixed FCP EQ memory check prevent initialize to single interrupt
vector case
- Fixed SLI4 16Gbit FC port internal and external diagnostic
loopback tests
- Fixed system panic during EEH recovery on SLI4 FC port
- Fix FLOGI fails with invalid RPI (0x04) after connecting to a
arbitrated loop
- Fix ELS SCR failing with local reject / invalid RPI
- Fix SLI4 port failures after firmware reset or dump
- Fix port reset log messages indicate error when no error is seen
- Fixed an issue where HBQ buffers are uninitialized in the
base driver
- Fixed missing shost lock protection on setting/clearing bit in
vport->fc_flag
- Fixed missing hbalock protection on setting/clearing bit in
phba->link_flag
- Fixed illegal state transition during driver unload
- Fixed system crash on SLI4 FC port looopback diagnostic test with
large buffers
- Fixed a potential error path that might try to free DMA memory
not allocated
- Fixed SLI4 FC port Internal and External loopback diagnostic
tests
- Fix a crash while deleting 256 vports
- Fix vport never finished discovery if switch runs out of
resources
- Fix kernel build warnings
- Fix kernel panic when putting board in offline state twice
- Fix memory leak when running hba resets to SLI-4 board
- Fix driver message 3092 and 3116 to KERN_WARNING
- Fix PCI read failure looks like a over temperature event
- Fixed driver event reporting to mgmt on error attention due to
forced dump
- Fix not displaying firmware rev for BE UCNA boards
- Fixed ABTS failure logic not rediscovering targets
- Fix bug with driver not byte swapping extended mailbox data
- Fix premature ndlp cleanup after second target LOGO
- Fix Link pull causes I/O failures
- Support loop for sli4 fc pass-through
- No longer read fcoe parameters if board is not fcoe
- Fix bug with driver passing a wrong count value
- Support restore state and error log when sysfs board_mode attribute
access failed
- Fixed a typo in two of the log messages just introduced
- Support for SLI4_CONFIG non-embedded
COMN_GET_CNTL_ADDL_ATTR pass-through
- Support for SLI4 FC port persistent linkdown through config
region 23
- Fix for ABTS. Do not free original IOCB whenever ABTS fails
- Fixed Linux driver inconsistency in reporting FC host port-state
through OCM
- Return an error if the mbox sysfs is called
- Fix firmware upgrade attempt on unsupported adapter
- Fix incomplete message number 2889
- Fix system crash when ASIC fails to initialize
- Fix virtual fabrics bit set in FLOGI incorrectly
- Fix bug with driver not returning extended mailbox data
- Fix unsupported link speed accepted by SLI4 port
- Incremented minor management version to reflect additional
"protocol" sysfs attribute
- Modify WQ handling to use entry_repost
- Moved link type definitions to apply to all driver streams
- Support a sysfs attribute "protocol" to report SLI4 port link
protocol type
- Support SLI4 INTF_TYPE and SLI_FAMILY as sub-field to the fwrev
sysfs attribute
- Support structure to support T10 DIF in SLI4
- Fix performance slowed due to too many register accesses
- Fixed a warning when converting from simple_strtoul to
strict_strtoul
- Support Initial code to inject T10 DIF errors
- Fixed a possible driver crash when cfg_fcp_eq_count is zero
- Fixed non-embedded COMMON_GET_CNTL_ATTR mbox command failed with
status 0x4
- Fixed null pointer dereference after clearing FCP policy rules
- Changed the way of SLI4 device detecting physical port name
- Fixed FCP policy exchange management rule parsing
- Support check to lpfc_decode_firmware_rev to handle releases that
have an 'X'
- Fixed RPI leaks in ELS protocol handling
- Fix kernel crash during boot with SLI4 card installed
- Fixed NPIV FDISC failure on SLI4 if-type 2 ports
- Fixed driver failed to follow IP reset procedure in SLI4 error
attention handler
- Fix sysfs lists fabric name for port that has been disconnected
from fabric
- Support FCP policy exchange management
- Changed the timeout to 300 seconds for SLI_CONFIG (0x9B) mailbox
command
- Fixed fcp underrun reporting
- Fixed a driver handling IP reset issue when PCI read return error
- Fixed casting problem in calculating tx_words statistics
- Support proper error code return for libdfc calling API to make
proper decisions
- Fix sli4 mailbox status code. Management software has
dependencies
- Fix compiler warning due to uninitialized local variable
- Fix bus reset handler fails with bad failure code
- Made proper error code return for libdfc calling API to make
proper decisions
- Made error log include PCI BAR bitmap from kernel when enable PCI
device failed
- Fixed sysfs API mismatch for building against SLES11 SP2 beta
kernel
- Fixed scsi midlayer queuecommand API mismatch for SLES11 SP2 beta
kernel
- Fixed ctlreg write bug not checking key string and limiting bytes
to write
- Fix default adapter name for the OCe15100
- Fixed incomplete scsi messages displayed
- Fix cable pull failure on interface type 2 SLI-4 adapters
- Fix enable_bg config parameter for SLI4
- Fixed not able to perform firmware reset through sysfs board_mode
attribute
- Fixed not recovering SLI port in handling error attention with RN
bit set
- Fixed two crash cases when unsolicted ELS ECHO_CMD is received
- Fix direct connect does not come up for SLI4 FC ports
- Fixed long wait when firmware reset to a SLI port without
required privilege
- Fix request firmware support for little endian systems
- Fix driver firmware to match new firmware image format
- Fixed SLI4 device firmware reset with SR-IOV virtual functions
- Fix SLI4 CT handling for sequences > 4K
- Fixed handling of unsolicited frames for vports
- Fixed handling of CVL for vports
- Fixed crash when aborting els IOs
- Fix up CT and oxid/rxid for unsol rcv frames
- Fixed mailbox double free panic
- Support fcf priority record selection for fcf failover
- Fixed compiler warning for putting large amount of memory on
stack
- Fixed driver build not building in debugfs even if kernel
CONFIG_DEBUG_FS=y is set
- Fix issue where the FC/FCoE Async Receive CQE did not scale for
16G FC adapters
- FLOGI payload has Multiple N_port_ID set when lpfc_enable_npiv
clear
- Removed unused argument passed to the lpfc_bsg_diag_mode_enter
routine
- Fixed new ASIC device-mgmt BSG pass-through failed multi-buffer
fw download
- Support sysfs logging when writeable parameters are changed
- Used PCI config space capability for sysfs get PF supported SR-
IOV number of VFs
- Support wait for SLI port status register for readyness following
firmware reset
- iDiag added SLI4 device PCI BAR memory mapped reigster access
methods
- Consolidated duplicating macro definitions
- Fixed failure to enable PCIe AER prevent driver initialize and
attach to device
- Modified log messages for T10-PI processing
- iDiag fixed mailbox capture and dump overlapping bitmap macro
definition


elx_dd_fc_ibm1206-8_3_5_86_rhel6_32-64_chg

Integrated Management Module (IMM) Firmware Update
Change History

IMPORTANT: Prerequisite for updating to IMM firmware version 1.30 (yuooc7e)
========== Updating to IMM firmware version 1.30 (yuooc7e) requires the current
IMM firmware version to be 1.10 (yuoo57h), or later. If this prerequisite is not
met before updating to version 1.30 (yuooc7e) the system will not power on
correctly. If the system is not running a minimum of IMM version 1.10 (yuoo57h),
update the IMM before attempting to update to 1.30 (yuooc7e).
This prerequisite was a limitation of IMM version 1.30, and it has been fixed
in IMM version 1.31(yuooc7f). This prerequisite does not apply to IMM version 1.31
or later.

IMPORTANT: Please DO NOT apply the firmware update (yuoo91e, v1.24)
========= if you are using AEM functions in x3620M3 or x3630M3. The
v1.24 firmware will disable the power capping functionality in those two
systems. Please remain on the current IMM version or update the firmware
to v1.25 or newer. Users not using AEM functions can still update to v1.24.

IMPORTANT: Read before using the MAX5
========== This Technical Update supplements the documentation that comes
with the IBM MAX5 for System x. Keep this document with your other MAX5
documentation. Before you attach the MAX5 to the server and try to use it,
you must update the server firmware with the latest level of firmware or
code. If you attach and try to use the MAX5 without updating the server
firmware, you might get unexpected system behavior or the server might
not power on. For special instructions to follow before you attach the MAX5
to the server, go to
http://www.ibm.com/support/entry/portal/docdisplay?lndocid=MIGR-5085756.

IBM maintains pages on the World Wide Web where you can get the latest
technical information and download device drivers and updates. To access
these pages, go to http://www.ibm.com/systems/support/ and follow the
instructions.

IMPORTANT: If you are at IMM firmware versions prior to 1.12 (yuoo67c) and
========== updating IMM firmware in Microsoft Windows, when you update IMM to
versions between 1.14 (YUOO73M) and 1.30 (YUOOC7E), it will take up to 10 minutes
additional wait time; when you update IMM to version 1.30 (YUOOC7E) or later, it
will take up to 20 minutes additional wait time. This is due to the iflash tool
checking the IMM before flashing. During this time the flashing process may appear
hung or unresponsive. The flashing will then complete and there is no functional
impact.

IMPORTANT: Make sure the current IMM firmware level is 1.14 or later
========== before you update the uEFI, FPGA, or DSA Preboot firmware.
The recommended firmware update sequence is IMM followed by UEFI
followed by FPGA followed by DSA Preboot.

IMPORTANT: A firmware change was made in YUOO57H (v1.10) that enforces the
========= requirement for login accounts on the IMM to have passwords that
contain both alpha and numeric characters. If you are updating the IMM firmware
from YUOO56K (v1.09) or earlier, to YUOO57H (v1.10) or newer, prior to updating
the firmware, please ensure that the IMM user account passwords contain
both alpha and numeric characters. If the firmware is updated and the passwords
do not contain both alpha and numeric characters, you may need to reset the IMM
to its default settings using the menus in the UEFI F1 set up display.

IMPORTANT: When updating the IMM firmware from a version earlier than
========= version 1.05 (build YUOO32F) to version 1.05 or newer, the
Remote Alert Recipient Email Addresses and the Daylight Saving
Time setting will revert to the default setting.
Users that utilize these settings will need to set them again
after the update.

IMPORTANT: When updating IMM, uEFI, pDSA, FPGA via any method,
========== please follow firmware update best practice document
(http://www-947.ibm.com/support/entry/portal/docdisplay?brand=
5000020&lndocid=MIGR-5082923) for suggested update sequence and prerequisite.

IMPORTANT: Due to an Intel errata, if your server is running a 32-bit Linux
========== Operating System, C-states may need to be disabled while updating
uEFI, IMM, or DSA Preboot through the Linux command line interface. See
RETAIN TIP H195678 for more information. Updates performed through the AMM,
Bootable Media Creator, or the IMM web or CLI interfaces do not have this
requirement.

IMPORTANT: Updated firmware version numbers might not be visible in SMBIOS
========== tables until after the server is rebooted.

IMPORTANT: After downgrading IMM firmware from version 1.22
========== to an earlier version, the user needs to reset the
IMM to factory default before normal operation.

Version 1.40, YUOOF7A
Problems Fixed:
- Fixed the problem that host OS will be shut down due to wrong overtemp event.
- Fixed the problem that "unsupported software version" could be showed in event logs after updating IMM version 1.30 or newer on x3850/x3950 X5, x3690X5 and HX5
- Fixed the problem that SMTP user name field on IMM web page only allows 16 chars.
- Fixed the problem on HS22 where IMM reports 0 watt power during initialization

Enhancements:
- Enabled IMM to fail over to backup automatically when there is a IMM firmware corruption
- Enhanced IMM web GUI response.
- Added notification when a corrupted GUID Partition Table (GPT) is encountered by UEFI during POST. Please refer to RETAIN Tip H207759 for details.
- Enhanced logging for Power Controls management.

Version 1.39, YUOOF2C
Problems Fixed:
- Fixed the problem on IBM System x3850X5 where SAP HANA configurations can reset in rare cases. More details in RETAIN Tip H207295.

Version 1.38, YUOOF2B
Problems Fixed:
- Fixed the problem on x3850 X5/x3950 X5 where the System Fault LED will be lit when only one PSU is installed.

Version 1.37, YUOOE9C
Problems Fixed:
- Corrected the voltage sensor threshold for HS22 and HS22V system.

Version 1.36, YUOOF2A
Enhancements:
- Improved IMM web page Accessibility

Version 1.35, YUOOE9B
Problems Fixed:
- Fixed the thermal issue for Broadcom quad port ethernet (IBM PN 49Y7948., FRU 49Y7949).
- Fixed the problem that user authentication for LDAP with SSL will fail when Configured Credentials is enabled.
- Updated the thermal profile for NVIDIA M2090 GPU card support in dx360 M3.
- Fixed the problem on HS22 systems where pressing the KVM button too soon (right after Power LED starts blinking slowly) would make the KVM owner unable to be changed.
- Fixed the problem on blade servers where IMM may report the "Unsupported blade/blower combination" error for 130W Westmere CPUs.
- Fixed the problem on x3200 M3 where when power policy is set as "restore" or "always on" in uEFI, enforcing system shutdown during POST will cause automatic system boot-up.
- Fixed the problem about SNMP drops intermittently and SNMP data cannot be accessed in a period of time
- Fixed the problem on x3850 X5/x3950 X5 Multi-Node systems where "redundancy lost" event is not logged in the Primary Node when one of the power supplies in the Secondary Node is lost.
- Optimized CPU power consumption calculation method for x3690 X5.
- Fixed the problem on blade servers where IMM does not automatically recover NCSI.
- Fixed the problem on blade servers that IMM constantly has "Init Failures" and fails to start up.
- Fixed the Readme file problem that some IP addresses of LAN-over-USB instructions are inconsistent.
- Fixed the CMOS Voltage Over Threshold problem on HS22V systems.
- Fixed the problem that SSH login failed when the setting is configured as "Local first then Ldap" or ldap settings are not valid.
- Fixed the problem that the IMM web interface responds too slowly or even fails to respond.

Enhancements:
- Enhanced the entropy (randomness) when generating SSL keys.
- Added secure SMTP authentication support.
- Added I/O board VPD information in IMM web interface
- Added the function of letting Location LED remain on after system power-off.
- Enhanced event Severity reporting of the QPI Link LED on x3850 X5/x3950 X5 so that IBM Director can interpret it correctly.
- Improved IMM version reporting for IBM Director.
- Added a function to keep 110V Power Supply Redundancy by throttling the system for x3850 X5/x3950 X5.
- Usability enhancement: all events will be checked by default on the alert setting web page.
- Enabled ASU to control each sub-category for email alert recipient setting and SNMP alerts setting.
- Added new BCH Midplane (that supports 8Gbit Fibre Channel) support.
- Added the function to capture all IMM logs with one button click.
- Enhanced the DataPower appliance blade support.

Version 1.34, YUOOE3E
Enhancement:
- Add support of the following fusion-io adapters :
1.2TB High IOPS MLC Adapter for IBM System x
2.4TB High IOPS MLC Adapter for IBM System x
365GB High IOPS MLC PCIe Adapter for IBM System x
785GB High IOPS MLC PCIe Adapter for IBM System x

Version 1.33, YUOOE3C
Problems Fixed:
- Fixed the problem that the "Date" header is missing from the IMM SMTP trap.
- Fixed the problem that the "Look Below" LED (CR48) on x3690 X5 Memory Expansion Board may turn on incorrectly when there are no errors detected.
- Fixed the problem on x3850 X5/x3950 X5 where the system information in the IMM configuration file may be truncated and the incomplete system information will cause the HTTP server in IMM run into an unstable state.
- Fixed the problem that the Scalability LED turns off after the IMM on either node of a 2-Node x3850 X5/x3950 X5 is reset.
- Fixed the problem that IMM on x3850 X5/x3950 X5 might fail to start after the IMM firmware is successfully upgraded.
- Fixed the problem where "Comm Errors" may occur when the IMM firmware on HX5 is upgraded.
- Fixed the problem that dx360 M3 may have PCI errors when a NVIDIA M2090 GPU card is installed.
- Fixed the problem that opening the ActiveX remote console closes all open tabs in the same Internet Explorer window.
- Fixed the problem that x3550 M3 may occur ServerRAID BBU over temperature and ServerRAID M5016 over heat issues.

Enhancements:
- Added Internet Explorer 9 support.
- Changed the maximum User's Distinguished Name(DN) for LDAP from 128 bytes to 256 bytes.
- Removed the limitation of 255 memberOf groups for an LDAP user in IMM.
- Enhanced IMM Web session management.
- Added an IMM command line (CLI) command for one time PXE boot option setting.
- Added a new unique error code in AMM and changed the text in AMM and IMM for CMOS battery errors.
- Updated Russia time zone definition to no more daylight saving time.

Version 1.32, YUOOD4G
Problems Fixed:
- Fixed a problem where IMM web interface does not lock out a user if
the same user exhausts login retries and gets locked out through the
SSH interface
- Fixed a problem that caused the IMM to report false critical DIMM
temperature events
- Fixed an intermittent problem where sometimes the Power Supply DC
status LED is not illuminated on the x3550 M2/M3, x3650 M2/M3,
x3620 M3 and x3630 M3
- Fixed a problem that sometimes causes the IMM web interface to shut
down after multiple invalid login attempts
Enhancements:
- Added Service Advisor support on x3850/x3950 X5 and x3690 X5
- Changed the IMM firmware to allow every service port to be Enabled
or Disabled
- Changed the IMM firmware to not disable the network interface when
there is a conflict IP address on the network
- Changed the IMM firmware to permit SSL client certificates to be managed
while the SSL client is enabled

Version 1.31, YUOOC7F
Problems Fixed:
- Fixed the problem that after updating IMM firmware from versions prior
to v1.10(YUOO57H) to v1.30(YUOOC7E) the system won't power on correctly

Version 1.30, YUOOC7E
Problems Fixed:
- Fixed the intermittent Power Supply error on x3550M2/M3 and x3650M2/M3
- Fixed the false alarm message for ArBel Power Supply on x3550M2/M3 and x3650M2/M3
- Fixed the issue that a blade intermittently does not respond to
the system management bus on HX5 and HS22/S22V
- Fixed the duplicate PECI messages issue on x3850/x3950 X5, x3690X5 and HX5
- Fixed the intermittent problem that a user can not login to IMM web
after inventory from IBM Director
- Fixed the problem that SMTP test alert doesn't work
- Fixed the problem that SNMP remote alert doesn't work
- Fixed the intermittent IMM reset problem
- Fixed the SSL vulnerability issue
Enhancements:
- Added 64-bit ActiveX Remote Presence Client support
- Added BGE overweight detection on HS22
- Added support of differentiating memory failures happening
during UEFI POST and during run-time
- Added support of reporting AC restore status on x3850/x3950 X5
- Added the change to include DIMM slot number info in the memory error event message

Version 1.29, YUOOB7F
Problem(s) Fixed:
- Fixed a problem where false memory configuration error messages are
sometimes reported on the x3850/x3950 X5

Version 1.28, YUOOB7C
Problem(s) Fixed:
- Fixed a problem where the IMM sometimes records duplicate event log
entries
- Fixed a problem that caused the DIMM Bank number to not be correctly
reported
- Fixed a problem that prevented the system from powering on when there
is a firmware mismatch
- Fixed a problem that didn't allow a password to be saved if it contains
a & or < character
- Fixed a problem where the IMM VPD sometimes is not available on the web
page
- Fixed a problem where one port on the QLogic 8GB HBA card sometimes
is not recognized
- Fixed a problem that sometimes caused the DVD drive to disappear in
RHEL5 after the IMM is reset
- Fixed a false Power Supply failure message
- Removed the error message pop up when changing the IMM password to default
- Fixed the problem that BBU gets over temp during discharging on x3550 M3
- Corrected a problem where the BOFM address became permanent after BOFM is
disabled on the AMM
- Corrected a system hang when a Multi-Bit memory error occurs with a mixture
of 2GB & 4GB DIMMs installed
- Fixed the problem where the reported DC Power consumed on the dx360 M3
is higher than actual AC input power
- Fixed the MIB mismatch issue
- Fixed the incorrect OID in MIB
Enhancements:
- Added support for 32-bit ActiveX Remote Presence Clients
- Added the ability to change the SMTP port number
- Changed the firmware to completely shut down the telnet sevice when
the telnet max user count is set to 0
- Added support for LDAP Active Directory Application Mode
- Added support for LDAP Authentication Only Mode
- Changed the firmware to report a configuration error if the CPU
installed on the EXA system is not a Westmere CPU
- Changed the firmware to allow the x3690X5 to be powered on sooner
- Changed the firmware to decrease the amount of time that it takes
for the IMM to become ready after it is reset


Version 1.27, YU00A7C
Enhancements:
- Added support for the IBM BladeCenter HX5(MT: 1910,7873)

Version 1.26, YU00A6A
Enhancements:
- Added support for the System x3850/x3950 X5(MT: 7143,7191)
and System x3690 X5(MT: 7147,7192)

Version 1.25, YU0091K
Problem(s) Fixed:
- Fixed a problem that hangs the server when F2 is pressed during POST
to start Diagnostics
- Fixed a problem in the HS22/HS22v that causes the IMM to report an
unexpected throttle condition after the AMM is reset
- Fixed a problem that causes the IMM lose its DHCP assigned IP address
- Improved the monitoring of hard drive status when the server is powered up
- Fixed a problem when using a Japanese keyboard with the remote presence
function
- Fixed a gradual fan speed reduction due to pressure sensor fluctuation on
System x3690 X5, System x3550 M2/3, System x3650 M2/3
- Improved the response to an IO Hub over temperature condition on
System x3690 X5, System x3650 M2/M3, and System x3550 M2/M3
- Fixed a problem that IBM Systems Director needs to re-discover IMM
in order to receive events from IMM after IMM upgrade
Enhancements:
- Added support for a 460W power supply in the System x3620 M3
- Added support for a 675W high efficiency power supply in the
System x3620 M3 and System x3630 M3

Version 1.24, YU0091E
Problem(s) Fixed:
- Fixed a problem where the IMM sometimes incorrectly reports a Pwr Rail
fault or Pwr 240A_A/Pwr 240A_B fault
- Fixed an issue where blade would hang on boot with ABR firmware corruption
message
- Fixed a problem when downgrading IMM firmware from version 1.22 to earlier
levels. The IMM network fails
- Fixed a problem that caused the firmware update using IMM Command Line
Interface to fail on an IPv6 network
- Fixed a problem that caused the IPv6 Link-local address not to be displayed
after resetting the IMM to its defaults
- Fixed a problem where the IMM fails to set SNMP configuration using ASU
- Fixed a problem where IMM cannot set the value 10 for the OSWatchdog value
using ASU
- Fixed a problem where IMM Remote Media would not re-initialize after
network error
- Fixed problem if KCS error bit status may not be clear which may cause KCS
communication stop
- Fixed a problem that IMM web interface hang with Remote Control session
opened
- Fixed a problem that blade unexpected powered on after power off command
Enhancements:
- Added IPv6 configuration support via IMM SNMP interface
- Added support for BladeCenter PCIe Expansion 4 on BladeCenter HX5
- Added support for BladeCenter GPU Expansion on BladeCenter HS22
- Added support for LDAP sub-tree searching with Novell eDirectory 8.7
- Added support for SNMP trap definitions
- Updated fan response and logic for Fusion IO PCIe adapter
- Updated ambient temperature sensor calculation

Version 1.22, YUOO84C
Problem(s) Fixed:
- Fixed a problem where the IMM sometimes incorrectly reports a Processor 2
(CPU 2) internal error
- Fixed a problem where after powering down an HS22, the HS22 powered on
without user request
- Fixed a problem while Log in to IMM might fail if the Host name contains
a dash
- Fixed a problem where the IMM makes some certificate management settings
protected that should not be protected
- Fixed a problem where users can't get the full details of an expansion card
using the IPMI FRU command
- Fixed a problem where IMM would hang after an LDAP login using some German
or French characters
- Fixed a problem with the IMM SMTP client not conforming to RFC821
- Fixed a problem where the email alert setting won't accept a hyphen
- Fixed a problem with the Windows key in the IMM Remote Control feature
- Fixed a problem where IMM login via LDAP authentication fails to acquire
Supervisor authority via Group membership with an OpenLDAP server.
- Fixed a problem where a user with Remote Server Power/Restart Access
authority can't change the power off delay
- Fixed a problem that prevented a Processor Throttled event from being
logged for the x3200 M3 and x3250 M3 models
- Fixed a problem that where a user's permission is always set from the
LDAP account not the local account profile
- Fixed a problem where the CPU2 VCore/CPU2 VDIMM sensors become unreadable
after updating the IMM in the x3500 M3 model
- Fixed problem for DHCP may get time out if using "Shared NIC" mode but without
any LAN cable to be plugged into "Sys Mgmt" port
Enhancement:
- Added IPv6 support
- Added Dynamic DNS support (IPv4 only)
- Added support for BladeCenter PCIe Expansion 4 on BladeCenter HS22
- Added BCH-R3 support

Version 1.21, YUOO75V
Enhancement:
- Added support for BladeCenter Max 5 Memory Expansion Unit (MEU)
- Added feature to report SMI Lane failure for BladeCenter HX5

Version 1.20, YUOO75T
Enhancement:
- Added support for Max 5 Memory Expansion Unit (MEU)for SystemX 3690 X5
- Added support for Max 5 Memory Expansion Unit (MEU)for BladeCenter HX5
- Added feature to show pending firmware level during firmware update process
- Added feature to block power on when multi-node complex has firmware mismatch
Problem(s) Fixed:
- Fixed DASD LED behavior for drives 8-32
- Fixed fan over cooling on SystemX 3690 X5
- Fixed Flash failure due to packet loss
- Fixed Power Cycle events not appearing in SystemX 3690 SEL
- Fixed DIMM throttle behavior in acoustic mode for BladeCenter HX5
- Fixed CPU type checking

Version 1.19, YUOO75X
Enhancement:
- Added support for Max 5 Memory Expansion Unit (MEU)for SystemX 3850/3950 X5
- Added support for 130W CPUs in High Performance Blades
- Added virtual NIC VPD support
- Changed the default value of SerialExitCLIKeySequence to ^[(
- Added TPM Physical Presence Sensor support
- Added AC metering and capping to System x3850/3950 X5
Problem(s) Fixed:
- Fixed server time out authority in web interface
- Fixed non-recoverable events that appeared as warning events in web event log
- Fixed Server State "unknown" status in web interface
- Prevented multiple log entries from being created for the same event
- Fixed IPMI multi-session handling when sessions fail
- Fixed IMM flash failed at 0 percent update progress error
- Fixed Internal Error 255 during FPGA update
- Fixed CPU Overtemp messages on FPGA update.
- Removed unnecessary events for Power Unit sensors
- Fixed failure to log VRD error on voltage fault
- Fixed Power Redundancy Sensor handling for 220V configurations
- Fixed CPU configuration check for System x3850/3950 X5
- Fixed IMM Network ARP
- Fixed flash error "Image transfer timed out - error 15"
- Corrected a problem that caused the system to not automatically power on after
performing an Automatic BIOS Recovery (ABR)

Version 1.18, YUOO75J
Enhancement:
- Added support for the System x3630 M3

Version 1.17, YUOO75H
Enhancement:
- Added support for the System x3690 X5

Version 1.16, YUOO73O
Enhancement:
- Added support for the BladeCenter System HX5


Version 1.14, YUOO73M
Problem(s) Fixed:
- Corrected the MIB file to address a compiling problem
- Fixed a problem when a second CPU might not been recognized by the IMM,
when cycling power on the System x3550
- Fixed a problem where web session may hang after staying on the System
Status web page for a while
- Disabled the interface to the shared network port when the dedicated systems
management network interface is selected.
- Fixed a web page pop-up error message that may occur after upgrading the
IMM from 48d and 57f
- Fixed power/thermal calibration error in the x3620 M3
- Fixed a problem where the IMM may log a CPU Automatically Throttled event
or a Redundancy Lost for a cooling zone event in the log after cycling power
- Fixed a problem where the IMM doesn't send an ambient temperature alert or
IO Hub temperature alert in the x3400 M3 and x3500 M3
- Corrected a remote presence problem that occurs while mounting an ISO image
if the remote client does not have any removable devices.
Enhancement:
- Added a fan control enhancement for performance mode
- Added support for additional types of power supplies
- Improved the accuracy of power readings on 3550 M3,
3650 M3, and 3620 M3


Version 1.14, YUOO73K (released for multinode System x3850 X5 and x3950 X5 only)
Problem(s) Fixed:
- Fixed a problem that caused the IMM not to respond to some IPMI commands
- Corrected a problem with LDAP authentication when role-based security
is enabled
- Corrected a problem which could cause a false CPU error to occur
- Prevented false automatic boot failure recovery events from being reported
Enhancements:
- Added multinode support for System x3850 X5 and System
x3950 X5
- Added support to activate FPGA updates with a warm boot
- Added support for AC power metering and AC power capping on single node
System x3850 X5 and System x3950 X5
- Added support to improve permit early power on support
- Add support to report the version information for updates that have been
flashed but not yet activated
- Added support to report an FPGA firmware mismatch


Version 1.12, YUOO67C
Problems(s) Fixed:
- Adjust the Planar VBAT voltage threshold in HS22
Enhancement:
- Added support for the System x3620 M3
- Added support for DC power supplies in the System x3550 M3 and
System x3650 M3


Version 1.11, YUOO56O
Enhancements:
- Improved ABR handling to prevent invalid ABR behavior


Version 1.10, YUOO57J (released for HS22 only)
Problem(s) Fixes:
- Fixed a problem where the IMM sometimes incorrectly reports a Processor 1
(CPU 1) internal error


Version 1.10, YUOO57H
Problem(s) Fixed:
- Made changes to improve the robustness of firmware update operations.
- Corrected an LDAP authentication problem.
- Corrected a problem where SNMP settings could be lost after updating
the firmware.
- Enable ssh by default.
- Permit the Adavnced Setting Utility to enable or disable ssh.
- Added support for logging a message when the blade CPU is not compatible
with the chassis' blower capacity
- Permit the realtime power management controller firmware to be flashed
to an earlier level.
- Corrected a problem that prevented the remote presence function from
working with network address translation
- Fixed an issue where blades would throttle/hang when chassis power supply is removed
Enhancement:
- Added support for the System x3550 M3, System x3650 M3, System x3500 M3,
System x3400 M3, System x iDataPlex dx360 M3, and the HS22V blade
- Enhanced power measurement and capping capabilities in support of
xSmartEnergy control
- Increased support for the number of DIMMs from 12 to 18


Version 1.09, YUOO56K
Enhancement:
- Added support for the System x3850 X5 and the System x3950 X5


Version 1.08, YUOO48F
Problem(s) Fixed:
- Made changes to improve the robustness of firmware update operations.
Limitations:
Limitations for versions 1.07 and 1.08:
If you are down-leveling the IMM firmware to a version older
than 1.07 and the IMM firmware is currently at version 1.07
or 1.08, you must remove AC power from the server before
performing a server reboot.


Version 1.07, YUOO48E
Prerequisites:
IMPORTANT: This firmware update contains changes to permit servers
========== to be powered on sooner after plugging them into AC power.
Before installing UEFI with firmware that supports the early power on
changes, be sure to update the IMM with this firmware version.
UEFI Firmware with early power on support:
BladeCenter HS22 UEFI Build P9E131A or newer
System x3550 M2 UEFI Build D6E131C or newer
System x3650 M2 UEFI Build D6E131C or newer
System x3200 M3 UEFI Build GYE129A or newer
System x3250 M3 UEFI Build GYE129A or newer
System x3400 M2 UEFI Build Y4E131B or newer
System x3500 M2 UEFI Build Y4E131B or newer
System x iDataplex dx360 M2 UEFI Build TME132A or newer
Problem(s) Fixed:
- Corrected an Ethernet bug that caused network packets to be dropped
- Changed the firmware to improve server performance when the Ethernet
over USB interface is enabled
- Corrected an intermittent problem where some of the IMM interfaces would
not function after flashing the IMM with new firmware
- Corrected a problem where LDAP users in nested groups are not permitted
access to the IMM
- Corrected a problem where the fault LED is not lit on the HS22 server
when a hard drive is removed
- Fixed a problem where the IMM sometimes incorrectly reports faults when
the server is power cycled (for example, a loss of redundancy or a critical
fan fault, or a processor is operating in a Degraded State, etc...)
- Corrected a problem where the server would sometimes hang at checkpoint 'E8'
- Changed the firmware to light the Information LED if the primary UEFI bank
becomes corrupted
- Corrected a problem that prevented the Remote Disk on Card feature
from properly working
- Corrected a problem that prevented an HS22 server with a full configuration
from powering on
- Changed the firmware to send processor information to the Advanced Management
Module for display
- Corrected a problem where faults for fan numbers 2 and 4 for the System
X3200 M3 were swapped
- Corrected a problem where the IMM firmware could corrupt itself over time
Enhancements:
- Changed the firmware to permit servers to be powered on sooner after
plugging them into AC power
- Improved the performance when displaying pages on the web interface
- Added support to permit management traffic over the daughter cards in the
HS22 server


Version 1.06, YUOO39B
Enhancement:
- Added support for Machine Types 4251, 4252, 4261, 7327, 7328


Version 1.05, YUOO32F
Limitations:
Problem(s) Fixed:
- This update package contains updated Management Information Base files
for use when managing the server through the IMM's SNMP interface
- Fixed a problem where user accounts and settings could become lost
- Improved performance when changing settings through the web interface
- Corrected a problem where some configuration settings were lost after
flashing the IMM with new firmware
- Improved the wording of messages in the Chassis Event Log
- Restored the ability to the IMM SNMP interface to add or remove user
accounts and to set the account security level
- Corrected a problem that prevented some configuration settings from being
set through the Advanced Setting Utility (ASU)
- Fixed a problem that prevented a user from specifying an email alert
recipient with a hyphen in the name
- Fixed an IMM flash update problem where the IMM erroneously reports a CPU
Configuration error and/or illuminates the fault LED on the HS22 Blade
Server with no corresponding entry in the Advanced Management Module log
- Fixed an IMM flash update issue which can result in blades never completing
the Discovery state
Enhancement:
- Added support for the BladeCenter PCIe Expansion module 3
- Added support for servers running real-time Linux
- Enhanced the automatic recovery of communication errors in BladeCenter
- Added the ability to configure a hostname for SNMPV3 traps, rather than just
an IP address


Version 1.04, YUOO24I
Problem(s) Fixed:
- This is a critical update for x3550 M2 and x3650 M2.
It corrects a possible problem that can occur when adding options
such as memory, hard drives, and Central Processing Units (CPUs),
and makes the system may become unresponsive.
In some cases the server cannot power on again, or network connectivity
to the Integrated Management Module is not possible. The problem may
also occur when rebooting the IMM while the system is powered on with
certain hardware configurations.
- Replaced the ibm_rndis_server_os.inf and device.cat in the IMM firmware
update package for Windows. The new files are used to workaround a
potential performance issue when the IMM's Ethernet over USB is enabled.
Enhancement:
- Added support for different hard drives
- Added support that enables the Advanced Management Module to display CPU
information for the HS22 blade.


Version 1.03, YUOO23C
Problem(s) Fixed:
- Removed the empty virtual drives that were presented to the
server by default. Virtual drives are now not presented
to the server unless media is present and mounted from
the Remote Control client.
Enhancement:
- Added support for Machine Types 7836, 7837, and 7839


Version 1.02, YUOO19G
Problem(s) Fixed:
- Corrected a problem where a critical fan fault was erroneously logged
when powering off the server


Version 1.01, YUOO19E
Enhancement:
- Added support for Machine Types 7946, 4198, 7947, 4199, 7321, 6380, 7323


Version 1.00, YUOO18D
- Original Release
- Supports Machine Types 7870, 1936


(C) Copyright International Business Machines Corporation 2008 - 2012.
All rights reserved.







ibm_fw_imm_yuoof7a-1_40_anyos_noarch_chg

Broadcom Firmware Update Utility for IBM servers and options using the Broadcom
NetXtreme and NetXtreme II ethernet adapter.

Version 2.1.9b, March 27th, 2013

2.1.9b has been created to pick latest Broadcom linux Bmapi to fix Arcjet reboot issue.
There is no fw code level change between 2.1.9a and 2.1.9b.

This package updates the Broadcom firmware for the following items:

NetXtreme Servers/Workstations
Product Initial Release Current Release Change History File
---------------------------------------------------------------------
1879 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

1880 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

1883 Boot code 3.21 Boot code 3.38 BCM5704s.chg
IPMI code 2.28 IPMI code 2.49 IPMI-BCM5704_5704s.chg

1884 Boot code 3.38 Boot code 3.38 BCM5704s.chg
IPMI code 2.42 IPMI code 2.49 IPMI-BCM5704_5704s.chg

1887 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

1916 Boot code 3.29 Boot code 3.29 BCM5714s.chg
IPMI code 6.21 IPMI code 6.24 IPMI-BCM5780_5780s_5714s_5715s.chg
UMP code 1.21 UMP code 1.21 UMP-BCM5714s.chg

4190 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg
Boot code 2.43 Boot code 2.43 BCM5703.chg

4191 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg
Boot code 2.43 Boot code 2.43 BCM5703.chg

4192 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

4193 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

4194 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg
Boot code 2.43 Boot code 2.43 BCM5703.chg

4347 Boot code 3.61 Boot code 3.65 BCM5721.chg

4348 Boot code 3.61 Boot code 3.65 BCM5721.chg

4362 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4363 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4364 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4365 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4366 Boot code 3.61 Boot code 3.65 BCM5721.chg
IPMI code 6.20 IPMI code 6.25 IPMI-BCM5721.chg

4367 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

4368 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

6216 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6217 Boot code 2.35 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6218 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.26 ASF code 7.20 ASF2.chg

6219 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6221 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6223 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6224 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6225 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6226 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

6227 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6228 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

6388 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

7362 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7364 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7365 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7367 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7942 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg

7969 Boot code 3.13 Boot code 3.29 BCM5780.chg
IPMI code 6.06 IPMI code 6.21 IPMI-BCM5780_5780s_5714s_5715s.chg

7973 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7974 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7975 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7976 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7977 Boot code 3.56 Boot code 3.65 BCM5721.chg
IPMI code 6.17 IPMI code 6.25 IPMI-BCM5721.chg

7981 Boot code 3.38 Boot code 3.38 BCM5704s.chg
IPMI code 2.42 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7984 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7986 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

7992 Boot code 3.13 Boot code 3.29 BCM5780.chg
IPMI code 6.06 IPMI code 6.21 IPMI-BCM5780_5780s_5714s_5715s.chg

8014 Boot code 3.29 Boot code 3.29 BCM5714s.chg
IPMI code 6.21 IPMI code 6.24 IPMI-BCM5780_5780s_5714s_5715s.chg
UMP code 1.21 UMP code 1.21 UMP-BCM5714s.chg

8028 Boot code 3.29 Boot code 3.29 BCM5714s.chg
IPMI code 6.21 IPMI code 6.24 IPMI-BCM5780_5780s_5714s_5715s.chg
UMP code 1.21 UMP code 1.21 UMP-BCM5714s.chg

8480 Boot code 2.28 Boot code 2.43 BCM5702.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8485 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8486 Boot code 3.49 Boot code 3.65 BCM5721.chg

8488 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

8490 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8491 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8647 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8648 Boot code 3.40 Boot code 3.65 BCM5721.chg
ASF code 6.22 ASF code 7.20 ASF2.chg

8649 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8671 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8673 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8676 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8678 Boot code 2.30 Boot code 2.43 BCM5703s.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8685 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8687 Boot code 2.14 Boot code 2.16 BCM5700.chg

8830 Boot code 2.25 Boot code 2.43 BCM5703.chg
ASF code 2.02I ASF code 2.02I ASF1.chg

8832 Boot code 3.21 Boot code 3.38 BCM5704s.chg
IPMI code 2.20 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8835 Boot code 3.19 Boot code 3.41 BCM5704.chg
IPMI code 2.16 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8837 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

8840 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

8841 Boot code 3.29a Boot code 3.65 BCM5721.chg
IPMI code 6.08 IPMI code 6.25 IPMI-BCM5721.chg

8843 Boot code 3.21 Boot code 3.38 BCM5704s.chg
IPMI code 2.28 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8848 Boot code 3.27 Boot code 3.41 BCM5704.chg
IPMI code 2.33 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8849 Boot code 3.49 Boot code 3.65 BCM5721.chg
IPMI code 6.14 IPMI code 6.25 IPMI-BCM5721.chg

8850 Boot code 3.36 Boot code 3.38 BCM5704s.chg
IPMI code 2.36 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8861 Boot code 3.19 Boot code 3.41 BCM5704.chg

8862 Boot code 3.19 Boot code 3.41 BCM5704.chg

8863 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.36 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8864 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.36 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8865 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.41 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8866 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8870 Boot code 3.19 Boot code 3.41 BCM5704.chg

8872 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.41 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8874 Boot code 3.36 Boot code 3.41 BCM5704.chg
IPMI code 2.41 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8878 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

8879 Boot code 3.41 Boot code 3.41 BCM5704.chg
IPMI code 2.45 IPMI code 2.49 IPMI-BCM5704_5704s.chg

9228 Boot code 3.24 Boot code 3.30 BCM5752.chg
ASF code 7.04 ASF code 7.20 ASF2.chg

9229 Boot code 3.24 Boot code 3.30 BCM5752.chg
ASF code 7.04 ASF code 7.20 ASF2.chg

9230 Boot code 3.27 Boot code 3.30 BCM5752.chg
ASF code 7.16 ASF code 7.20 ASF2.chg

9233 Boot code 3.09 Boot code 3.09 BCM5722.chg
IPMI code 6.03 IPMI code 6.03 IPMI-BCM5722.chg


NetXtreme II Servers
Product Initial Release Current Release Change History File
---------------------------------------------------------------------
1885 Boot code 1.8.2 Boot code 4.6.1 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.4 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

1909 Boot code 5.2.2 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.6 NCSI code 2.0.11 NCSI-NX2.chg

1910 Boot code 6.2.0 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

1911 Boot code 6.2.0 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

1913 Boot code 1.8.1 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

1914 Boot code 1.8.2 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

1915 Boot code 1.9.6 Boot code 4.6.1 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.7 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

1936 Boot code 4.6.4 Boot code 6.2.0 BCM5709s.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

1949 Boot code 5.0.6 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

2582 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2583 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2586 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

2587 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

3808 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

3809 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

3815 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

3817 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

3821 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

3822 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

4195 Boot code 5.2.2 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.6 NCSI code 2.0.11 NCSI-NX2.chg

4198 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

4199 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

4254 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

4255 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7141 Boot code 3.7.0 Boot code 6.2.0 BCM5709.chg
IPMI code 0.1.13 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7143 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7144 Boot code 3.7.0 Boot code 6.2.0 BCM5709.chg
IPMI code 0.1.13 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7145 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7146 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7147 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7148 Boot code 5.2.2 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.10 NCSI code 2.0.11 NCSI-NX2.chg

7149 Boot code 5.2.2 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.10 NCSI code 2.0.11 NCSI-NX2.chg

7163 Boot code 4.0.2 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7164 Boot code 5.2.2 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.10 NCSI code 2.0.11 NCSI-NX2.chg

7191 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7192 Boot code 6.2.0 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7233 Boot code 4.4.10 Boot code 6.2.0 BCM5709.chg
IPMI code 0.1.16 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7234 Boot code 4.4.10 Boot code 6.2.0 BCM5709.chg
IPMI code 0.1.16 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg

7378 Boot code 5.0.6 Boot code 6.2.0 BCM5716.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7379 Boot code 5.0.6 Boot code 6.2.0 BCM5716.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7380 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7809 Boot code 4.6.4 Boot code 6.2.0 BCM5709s.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7836 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7837 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7839 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7870 Boot code 4.6.4 Boot code 6.2.0 BCM5709s.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7871 Boot code 5.0.6 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7872 Boot code 5.2.2 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7873 Boot code 6.2.0 Boot code 6.2.0 BCM5709s.chg
NCSI code 2.0.11 NCSI code 2.0.11 NCSI-NX2.chg

7901 Boot code 4.4.14 Boot code 6.2.0 BCM5709s.chg
IPMI code 0.1.17 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg
UMP code 1.0.4 UMP code 1.0.6 UMP-BCM5709s.chg

7902 Boot code 4.4.14 Boot code 6.2.0 BCM5709s.chg
IPMI code 0.1.17 IPMI code 1.0.1 IPMI-BCM5709_5709s.chg
UMP code 1.0.4 UMP code 1.0.6 UMP-BCM5709s.chg

7940 Boot code 4.0.3 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7941 Boot code 4.0.3 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7943 Boot code 4.0.2 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7944 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7945 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
NCSI code 2.0.3 NCSI code 2.0.11 NCSI-NX2.chg

7946 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7947 Boot code 4.6.4 Boot code 6.2.0 BCM5709.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg

7971 Boot code 1.9.3 Boot code 4.6.1 BCM5706s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.6 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg
MPE Boot code 1.9.3 MPE Boot code 4.6.1 BCM5708s.chg

7972 Boot code 1.9.3 Boot code 4.6.1 BCM5706s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.6 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg
MPE Boot code 1.9.3 MPE Boot code 4.6.1 BCM5708s.chg

7978 Boot code 1.8.1 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7979 Boot code 1.8.1 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7985 Boot code 1.9.3 Boot code 4.6.1 BCM5706.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7995 Boot code 1.9.6 Boot code 4.6.1 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.7 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

7996 Boot code 3.4.4 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

7997 Boot code 3.4.4 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg

8853 Boot code 1.8.2 Boot code 4.6.1 BCM5708s.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg
UMP code 1.1.4 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

8877 Boot code 1.8.2 Boot code 4.6.1 BCM5708.chg
IPMI code 1.06.0 IPMI code 1.06.0 IPMI-BCM5706_5706s_5708_5708s.chg


NetXtreme and NetXtreme II Add-in Options for Blades
Product Initial Release Current Release Change History File
---------------------------------------------------------------------
26K4842 Boot code 3.21 Boot code 3.38 BCM5704s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39R8624 Boot code 3.21 Boot code 3.38 BCM5704s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y9306 Boot code 3.28 Boot code 3.29 BCM5715s.chg
PXE code 9.7.10 PXE code 12.2.2 PXE-NX.chg

39Y9310 Boot code 3.38 Boot code 3.38 BCM5704s.chg
PXE code 9.7.10 PXE code 12.2.2 PXE-NX.chg

42C1600 Boot code 3.24 Boot code 3.29 BCM5714s.chg
PXE code 9.0.12 PXE code 12.2.2 PXE-NX.chg

42C1632 Boot code 3.24 Boot code 3.29 BCM5714s.chg
PXE code 9.0.12 PXE code 12.2.2 PXE-NX.chg

46M6164 Boot code 6.2.25 Boot code 6.2.25 BCM57711.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57711.chg
PXE code 7.2.29 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.4.19 UEFI code 7.4.19 UEFI-NX2-ev.chg

46M6168 Boot code 6.2.25 Boot code 6.2.25 BCM57711.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57711.chg
PXE code 7.2.29 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.4.19 UEFI code 7.4.19 UEFI-NX2-ev.chg

44W4465 Boot code 5.2.71 Boot code 5.2.71 BCM57710.chg
NCSI code 2.0.7 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 7.2.29 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.4.19 UEFI code 7.4.19 UEFI-NX2-ev.chg

44W4466 Boot code 5.2.71 Boot code 5.2.71 BCM57710.chg
NCSI code 2.0.7 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 7.2.29 PXE code 7.2.29 PXE-NX2-ev.chg
UEFI code 7.4.19 UEFI code 7.4.19 UEFI-NX2-ev.chg

44W4475 Boot code 4.6.4 Boot code 6.2.0 BCM5709s.chg
NCSI code 1.0.6 NCSI code 2.0.11 NCSI-NX2.chg
PXE code 4.6.8 PXE code 7.0.6* PXE-NX2.chg
UEFI code 4.6.23 UEFI code 7.0.2* UEFI-NX2.chg

44W4479 Boot code 4.4.14 Boot code 6.2.0 BCM5709s.chg
NCSI code 0.5.8 NCSI code 2.0.11 NCSI-NX2.chg
PXE code 4.4.4 PXE code 7.0.6* PXE-NX2.chg
UEFI code NA UEFI code 7.0.2* UEFI-NX2.chg

44X1940 Boot code 4.6.4 Boot code 6.2.0 BCM5709s.chg
PXE code 4.6.8 PXE code 7.0.6* PXE-NX2.chg
UEFI code NA UEFI code 7.0.2* UEFI-NX2.chg

73P9030 Boot code 3.21 Boot code 3.38 BCM5704s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

81Y3133 Boot code 6.2.25 Boot code 6.2.25 BCM57712.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57712.chg
PXE code 7.4.13 PXE code 7.4.13 PXE-NX2-ev.chg
UEFI code 7.4.19 UEFI code 7.4.19 UEFI-NX2-ev.chg


NetXtreme and NetXtreme II Add-in Options for Servers/Workstations
Product Initial Release Current Release Change History File
---------------------------------------------------------------------
22P7801 Boot code 2.25 Boot code 2.43 BCM5703s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

31P6301 Boot code 2.25 Boot code 2.43 BCM5703.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

31P6401 Boot code 3.19 Boot code 3.41 BCM5704.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6066 Boot code 1.9.6 Boot code 4.6.1 BCM5708.chg
PXE code 3.0.6 PXE code 7.0.6* PXE-NX2.chg
UMP code 1.1.8 UMP code 1.1.9 UMP-BCM5706s_5708_5708s.chg

39Y6079 Boot code 2.25 Boot code 2.43 BCM5703.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6088 Boot code 2.25 Boot code 2.43 BCM5703s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6093 Boot code 3.19 Boot code 3.41 BCM5704.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

39Y6098 Boot code 3.29a Boot code 3.65 BCM5721.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

42C1780 Boot code 4.4.14 Boot code 6.2.0 BCM5709.chg
ISCSI code 2.7.15 ISCSI code 7.0.10* ISCSI-NX2.chg
PXE code 4.4.4 PXE code 7.0.6* PXE-NX2.chg
UEFI code NA UEFI code 7.0.2* UEFI-NX2.chg

42C1781 Boot code 4.4.14 Boot code 6.2.0 BCM5709.chg
ISCSI code 2.7.15 ISCSI code 7.0.10* ISCSI-NX2.chg
PXE code 4.4.4 PXE code 7.0.6* PXE-NX2.chg
UEFI code NA UEFI code 7.0.2* UEFI-NX2.chg

42C1790 Boot code 4.4.9 Boot code 5.2.71 BCM57710.chg
NCSI code 0.5.8 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 4.4.11 PXE code 7.0.49* PXE-NX2-ev.chg
UEFI code NA UEFI code 7.0.41* UEFI-NX2-ev.chg

42C1791 Boot code 4.4.9 Boot code 5.2.71 BCM57710.chg
NCSI code 0.5.8 NCSI code 2.0.7 NCSI-BCM57710.chg
PXE code 4.4.11 PXE code 7.0.49* PXE-NX2-ev.chg
UEFI code NA UEFI code 7.0.41* UEFI-NX2-ev.chg

49Y4220 Boot code 5.0.6 Boot code 6.2.0 BCM5709.chg
ISCSI code 4.0.19 ISCSI code 7.0.10* ISCSI-NX2.chg
PXE code 5.0.5 PXE code 7.0.6* PXE-NX2.chg
UEFI code 5.0.6 UEFI code 7.0.2* UEFI-NX2.chg

49Y7910 Boot code 6.2.25 Boot code 6.2.25 BCM57712.chg
NCSI code 6.2.7 NCSI code 6.2.7 NCSI-BCM57712.chg
PXE code 7.4.13 PXE code 7.4.13 PXE-NX2-ev.chg
UEFI code 7.4.19 UEFI code 7.4.19 UEFI-NX2-ev.chg

73P3501 Boot code 3.29a Boot code 3.65 BCM5721.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

73P4001 Boot code 2.25 Boot code 2.43 BCM5703s.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

73P4101 Boot code 2.25 Boot code 2.43 BCM5703.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

73P4201 Boot code 3.19 Boot code 3.41 BCM5704.chg
PXE code 7.6.6 PXE code 12.2.2 PXE-NX.chg

90Y9352 Boot code 1.31 Boot code 1.31 BCM5719.chg
iSCSI code 7.4.2 iSCSI code 7.4.2 ISCSI-NX.chg
EFI code 15.4.6 EFI code 15.4.6 UEFI-NX.chg
PXE code 15.4.2 PXE code 15.4.2 PXE-NX.chg

90Y9370 Boot code 1.30 Boot code 1.30 BCM5720.chg
iSCSI code 7.4.2 iSCSI code 7.4.2 ISCSI-NX.chg
EFI code 15.4.6 EFI code 15.4.6 UEFI-NX.chg
PXE code 15.4.2 PXE code 15.4.2 PXE-NX.chg


NetXtreme and NetXtreme II Add-in Options for Flex Chassis
Product Initial Release Current Release
----------------------------------------------------------
49Y7900 Boot code 1.55 Boot code 1.55 BCM5718.chg
NCSI code 1.01.07 NCSI code 1.01.07 NCSI-NX.chg
IMFW code 1.05 IMFW code 1.05 IMFW-NX.chg
fcode 3.0.1 fcode 5.0.1*
iSCSI code 7.4.2 iSCSI code 7.4.2 ISCSI-NX.chg
EFI code 15.4.6 EFI code 15.4.6 UEFI-NX.chg
PXE code 15.4.2 PXE code 15.4.2 PXE-NX.chg




package version 2.1.9b
Problems Fixed:
- The only change is Broadcom linux bmapi to fix arcjet reboot issues. No code level change between 2.1.9a and 2.1.9b.

package version 2.1.9a
Problems Fixed:
- Changes were made to the boot code, NSCI, fcode, ISCSI, EFI, PXE code for the 49Y7900, 49Y7902(BCM5718).

package version 2.1.8e
Problems Fixed:
- Changes were made to the UEFI code to fix 49Y7910(BCM57712/Cobia) issues.

package version 2.1.8d (See brcm_fw_nic_2.1.8d-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 46M6164, 46M6168, 49Y7910 and 81Y3133.
- Changes were mande to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168, 49Y4220, 49Y7910 and 81Y3133.
- Changes were made to the iSCSI code for the 42C1780, 42C1781, 49Y4220 and 49Y7910.

package version 2.1.7e (See brcm_fw_nic_2.1.7e-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475
, 44W4479
, 44X1940

and 49Y4220.
- Added support for the 49Y7910.

package version 2.1.7d (See brcm_fw_nic_2.1.7d-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791,
44W4465
, 44W4466
, 44W4475
, 44W4479
, 44X1940
, 46M6164
, 46M6168, 49Y4220 and 81Y3133.
- Fixed a problem where the MAC addresses for the HS22/HS22V LOM were incorrectly set to zero.


package version 2.1.7c (See brcm_fw_nic_2.1.7c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 46M6164 and 46M6168.
- Changes were made to the NCSI code for the 46M6164 and 46M6168.
- Changes were made to the PXE code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466.
- Changes were made to the UEFI code for the 42C1790, 42C1791, 46M6164, 46M6168, 44W4465 and 44W4466.
- Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.

package version 2.1.7b (See brcm_fw_nic_2.1.7b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Fixed problem running the PPC firmware update tool on some PPC systems.

package version 2.1.7a (See brcm_fw_nic_2.1.7a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781,
42C1790, 42C1791, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220
- Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817,
3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479,
46M6164 and 46M6168.
- Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.

package version 2.1.6b (See brcm_fw_nic_2.1.6b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- The update tool was modified to fix a problem updating the firmware when certain option
cards are installed in the system.

package version 2.1.6a (See brcm_fw_nic_2.1.6a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4195, 4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7148, 7149, 7164, 7233, 7234, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781,
44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220
- Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.
- Changes were made to the iSCSI code for the 42C1780, 42C1781 and 49Y4220.
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164, 46M6168 and 49Y4220.

package version 2.1.5b (See brcm_fw_nic_2.1.5b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Added iSCSI config update support for mfg.

package version 2.1.5a (See brcm_fw_nic_2.1.5a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the NCSI code for the 1909, 1936, 1949, 3808, 3809, 3815, 3817,
3821, 3822, 4195, 4198, 4199, 4254, 4255, 7145, 7146, 7148, 7149, 7164, 7378, 7379,
7380, 7809, 7836, 7837, 7839, 7870, 7871, 7872, 7944, 7945, 7946, 7947, 44W4475, 44W4479,
42C1790 and 42C1791
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 42C1780, 42C1781, 42C1790, 42C1791 and 49Y4220.
- Changes were made to the IPMI code for the 7141, 7144, 7233, 7234, 7901 and 7902.

package version 2.1.4a (See brcm_fw_nic_2.1.4a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.

package version 2.1.3c (See brcm_fw_nic_2.1.3c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the iSCSI code for the 42C1780 and 42C1781.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 42C1790, 42C1791, 44W4465,
44W4466, 44W4475, 44W4479, 44X1940, 46M6164 and 46M6168.
- Changes were made to the boot code for the 46M6164 and 46M6168.

Enhancements:
- Added version check to prevent firmware updates of code that is not newer than already
installed code.
- Added "-force" command line option to allow forcing the firmware update.

package version 2.1.3b (See brcm_fw_nic_2.1.3b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4198, 4199, 4254, 4255, 7141, 7144, 7145, 7146, 7233, 7234, 7378, 7379, 7380, 7836, 7837,
7839, 7870, 7871, 7901, 7902, 7944, 7945, 7946, 7947, 42C1780, 42C1781, 44W4475, 44W4479
and 44X1940.
- Changes were made to the NCSI code for the 1936, 1949, 3808, 3809, 3815, 3817, 3821, 3822,
4198, 4199, 4254, 4255, 7145, 7146, 7378, 7379, 7380, 7836, 7837, 7839, 7870, 7871, 7944,
7945, 7946, 7947, 44W4475 and 44W4479.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 44W4475, 44W4479 and
44X1940.
- Changes were made to the UEFI code for the 42C1780, 42C1781, 44W4475, 44W4479 and 44X1940.
- Changes were made to the iSCSI code for the 42C1780 and 42C1781.

package version 2.1.3a (See brcm_fw_nic_2.1.3a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 26K4842, 39R8624, 39Y9306, 39Y9310, 42C1600,
42C1632, 46M6164, 46M6168, 44W4465, 44W4466, 73P9030, 22P7801, 31P6301, 31P6401, 39Y6079,
39Y6088, 39Y6093, 39Y6098, 42C1790, 42C1791, 73P3501, 73P4001, 73P4101 and 73P4201.
- Changes were made to the UEFI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.
- Changes were made to the NCSI code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.
- Changes were made to the boot code for the 46M6164, 46M6168, 44W4465, 44W4466, 42C1790,
and 42C1791.

package version 2.1.1c (See brcm_fw_nic_2.1.1c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- none.

Enhancements:
- Added support for the 1949, 4254, 4255, 7378, 7379, 7380, 7871, 7944 and 7945.

package version 2.1.1b (See brcm_fw_nic_2.1.1b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Fixed problem where the firmware update failed to run correctly on RHEL5u4-XEN.

package version 2.1.1a (See brcm_fw_nic_2.1.1a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 1936, 3808, 3809, 3815,
3817, 3821, 3822, 4198, 4199, 7141, 7144, 7163, 7233, 7234, 7809, 7836, 7837, 7839, 7870,
7901, 7902, 7946, 7947, 7978, 7979, 7995, 7996, 7997, 8853, 8877, 44W4465, 44W4466, 44W4475,
44W4479, 44X1940, 39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791.
- Changes were made to the NCSI code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822, 4198,
4199, 7809, 7836, 7837, 7839, 7870, 7946, 7947, 44W4465, 44W4466, 44W4475, 44W4479, 42C1790
and 42C1791.
- Changes were made to the PXE code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940,
39Y6066, 42C1780, 42C1781, 42C1790 and 42C1791.
- Changes were made to the UEFI code for the 44W4465, 44W4466, 44W4475, 44W4479, 44X1940,
42C1780, 42C1781, 42C1790 and 42C1791.
- Changes were made to the iSCSI code for the 42C1780 and 42C1781.

Enhancements:
- Added support for the 46M6164 and 46M6168.

package version 2.1.0a (See brcm_fw_nic_2.1.0a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1936, 3808, 3809, 3815, 3817, 3821, 3822,
4198, 4199, 7141, 7144, 7233, 7234, 7836, 7837, 7839, 7870, 7901, 7902, 7946, 7947,
42C1780, 42C1781, 42C1790, 42C1791, 44W4465, 44W4466, 44W4475, 44W4479 and 44X1940.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781, 42C1790, 42C1791,
44W4465, 44W4466, 44W4475, 44W4479 and 44X1940.
- Changes were made to the ISCSI code for the 42C1780 and 42C1781.

package version 2.0.9h (See brcm_fw_nic_2.0.9h-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Removed the minimum boot code level check for the 44W4465 and 44W4466.

Enhancements:
- Added support for the 3808, 3809, 3815, 3817, 3821, 3822, 4198, 4199, 7836, 7837, 7839
and 9233.

package version 2.0.9g (See brcm_fw_nic_2.0.9g-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UEFI code for 42C1780, 42C1781, 42C1790, 42C1791, 44W4465
44W4466, 44W4475, 44W4479 and 44X1940.
- Fixed the problem where the PXE code for the 44W4465 and 44W4466 failed to update
under 64bit Linux.

Enhancements:
- Added support for the 7946 and 7947.

package version 2.0.9f (See brcm_fw_nic_2.0.9f-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7233, 7234,

7940,
7941,
7971,
7972,
7978,
7979,
7985,
7995,
7996,
7997,
8853,
8877, 39Y6066, 42C1780,
42C1781, 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.
- Changes were made to the NCSI code for the 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.
- Changes were made to the PXE code for 42C1790, 42C1791, 44W4465, 44W4466 and 44W4479.

Enhancements:
- Added support for the 1936, 7870 and 44W4475.
- Added UEFI code for 42C1790, 42C1791, 44W4465, 44W4466, 44W4479 and 44X1940.

package version 2.0.9e (See brcm_fw_nic_2.0.9e-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Added a bnx2 device driver version check for version 1.6.6b or greater.

package version 2.0.9c (See brcm_fw_nic_2.0.9c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1915, 7901, 7902, 7971, 7972, 7995,
8853 and 44W4479.
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479.
- Changes were made to the iSCSI code for the 42C1780 and 42C1781
- Changes were made to the NCSI code for the 44W4479.

Enhancements:
- Added support for the 44X1940.

package version 2.0.8f (See brcm_fw_nic_2.0.8f-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Fcode support was removed for the PXE code for the 44W4465 and 44W4466. This change
does not result in a change in the PXE code version number.
- Changes were made to the PXE code for the 39Y6066, 42C1780 and 42C1781 to fix a
problem where some systems hang when loading PXE code.

package version 2.0.8e (See brcm_fw_nic_2.0.8e-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 39Y6066, 42C1780, 42C1781 and 44W4479.
- Changes were made to the IPMI code for the 7141, 7144, 7233 and 7234.
- Changes were made to the UMP code for the 7901 and 7902.

Enhancements:
- Added support for the 6388, 7942, 44W4465 and 44W4466.

package version 2.0.8d (See brcm_fw_nic_2.0.8d-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 7141, 7144, 7233 and 7234.

Enhancements:
- Added support for the 42C1780 and 42C1781.

package version 2.0.8c (See brcm_fw_nic_2.0.8c-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- None.

Enhancements:
- Added support for the 7901 and 7902

package version 2.0.8b (See brcm_fw_nic_2.0.8b-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 39Y6066.

Enhancements:
- Added support for the 44W4479.

package version 2.0.8a (See brcm_fw_nic_2.0.8a-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7141, 7144, 7971,
7972, 7978, 7979, 7985, 7995, 7996, 7997, 8853, 8877, 9228, 9229, 9230 and 39Y6066.
- Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488,
8648, 9228, 9229, 9230.
- Changes were made to the UMP code for the 39Y6066.
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600,
42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.
- Changes were made to the IPMI code for the 1916, 8014 and 8028.

Enhancements:
- Added support for the 7233, 7234, 7940 and 7941.

package version 2.0.7 (See brcm_fw_nic_2.0.7-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600,
42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.

Enhancements:
- Added support for the 1916, 8014 and 8028.

package version 2.0.6 (See brcm_fw_nic_2.0.6-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1913, 1914, 7141, 7143, 7144, 7978,
7979, 7996, 7997, 8877 and 39Y6066.
- Changes were made to the UMP code for the 39Y6066.
- Changes were made to the PXE code for the 39Y6066.

package version 2.0.5 (See brcm_fw_nic_2.0.5-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- None

Enhancements:
- Added support for the 4190, 4191, 4192, 4193, 4194, 4367 and 4368.

package version 2.0.4 (See brcm_fw_nic_2.0.4-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- None

Enhancements:
- Added support for the 7141, 7143 and 7144.

package version 2.0.3 (See brcm_fw_nic_2.0.3-lin-win-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1885, 1913, 1914, 1915, 7971, 7972,
7978, 7979, 7985, 7995, 8853, 8877, 39Y6066.
- Changes were made to the IPMI code for the 1879, 1880, 1883, 1884, 1887, 4362,
4363, 4364, 4365, 4366, 7362, 7364, 7365, 7367, 7973, 7974, 7975, 7976, 7977,
7981, 7984, 7986, 8485, 8490, 8491, 8832, 8835, 8837, 8840, 8841, 8843, 8848,
8849, 8850, 8863, 8864, 8865, 8866, 8872, 8874, 8878, 8879.
- Changes were made to the ASF code for the 6218, 6223, 6225, 6227, 6228, 8488,
8648, 9228, 9229, 9230.
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600,
42C1632, 73P3501, 73P4001, 73P4101, 73P4201, 73P9030.

package version 2.0.0b (See brcm_fw_nic_2.0.0b-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changed the firmware update process to NOT reset the ethernet devices during the
firmware update process.

package version 2.0.0 (See brcm_fw_nic_2.0.0-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the UMP (Universal Management Port) code for the 1885,
7971, 7972, 7995 and 8853.

package version 1.1.1 (See brcm_fw_nic_1.1.1-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 1879, 1880, 1887, 4347, 4348, 4362,
4363, 4364, 4365, 4366, 6218, 6223, 6225, 6227, 6228, 7969, 7973, 7974, 7975,
7976, 7977, 7992, 8485, 8486, 8488, 8490, 8491, 8648, 8837, 8840, 8841, 8849,
39Y6098, 39Y9306, 42C1600, 42C1632 and 73P3501.
- Changes were made to the IPMI code for the 1879, 1880, 1887, 4362, 4363, 4364,
4365, 4366, 7969, 7973, 7974, 7975, 7976, 7977, 7992, 8485, 8490, 8491, 8837,
8840, 8841 and 8849.
- Changes were made to the PXE code for the 22P7801, 26K4842, 31P6301, 31P6401,
39R8624, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9306, 39Y9310, 42C1600, 42C1632,
73P3501, 73P4001, 73P4101, 73P4201 and 73P9030.

package version 1.1.0 (See brcm_fw_nic_1.1.0-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the Boot Code for the 1913, 1914, 4347, 6218, 6223, 6225,
6227, 6228, 7969, 7971, 7972, 7978, 7979, 7985, 7995, 8486, 8648, 8853, 8877,
9228 and 9229.
- Changes were made to the ASF code for 6218, 6223, 6225, 6227, 6228, 8648,
9228 and 9229.
- Changes were made to the PXE code for the 39Y6066.
- Changes were made to the

Enhancements:
- Added support for the 1879, 1880, 1883, 1884, 1887, 1913, 22P7801, 31P6301,
31P6401, 39Y9306, 39Y6066, 39Y6079, 39Y6088, 39Y6093, 39Y6098, 39Y9310, 4348,
4366, 7362, 7364, 7365, 73P3501, 73P4001, 73P4101, 73P4201, 7992, 7995, 8488
and 9230.

package version 1.0.0 (See brcm_fw_nic_1.0.0-nx-nx2-chg_anyos_anycpu.zip for details.)
Problems Fixed:
- Changes were made to the boot code for the 8832, 1914, 7971, 7972, 7978, 7979
7985, 8853 and 8877.
- Changes were made to the UMP (Universal Management Port) code for the 7971,
7972 and 8853.
brcm_fw_nic_2_1_9b_linux_32-64_chg

===============================================================================
Emulex NIC Device Driver for Linux
===============================================================================

Linux NIC Device Driver Version: 4.2.389.0

Problems Fixed:
- Unloading the driver hangs the system after running IPv6 traffic
- Link status messages cleaned up when in Switch Agnostic mode
- Miscellaneous network performance issues to improve throughput
- Miscellaneous problems related to SRIOV to improve usability
- Ethtool wol command displays wol enabled even when disabled
- Ethtool speed reported as 10000Mb/s for disabled devices in Switch Agnostic mode

Incremental Interoperability:
- RHEL6.3 GA Kernel
- Increase default B/W for SRIOV vf's to 10Gb from 100Mb

Known Issues:
- SR-IOV configuration section of the Linux NIC Driver Documentation will be modified as follows to improve clarity (noted by << >>):

11. Use the Virtual Machine Manager GUI to attach the VF (step 7 on page 34) to the guest operating system by using the add physical device option.

<< Note 1: If user wants to re-configure an already configured setup, it can be done by removing the attached VF from the respective guest operating system using the remove option after selecting the VF attached. And then attaching another VF (step 11).

Note 2: Consult the documentation for your host operating system for help using the Virtual Machine Manager to attach and detach virtual interfaces. >>

12. Start the RHEL 6.x guest operating system. Once the guest operating system is booted, use the lspci command to confirm the visibility of the OneConnect NIC
function. The output shows a OneConnect NIC function, for example:
03:00.0 Ethernet controller: Emulex Corp. Emulex OneConnect 10Gb NIC (be3)

13. The OneConnect Ethernet driver automatically loads with the inbox driver, and creates the network interfaces. Use the ifconfig command to verify that the interface is created.

14. After configuring the network interfaces with proper IP addresses, you can send and receive network traffic from the VM. << (Consult the documentation for your host and guest operating systems for network configuration help). >>

===============================================================================

Linux NIC Device Driver Version 4.1.422.5

Problems Fixed:

- Ethtool information missing with newest version of be2net

===============================================================================

Linux NIC Device Driver Version 4.1.413.0

Problems Fixed:

- WOL changes for Linux NIC driver as mentioned in Bug# 24543
- SR IOV UE when attempt to do multiple (3 times) driver load/unload
- Speed is 10000Mb/s for Disabled devices in UMC Mode
- Incorrect Duplex value is shown for unconnected port of NC552m in Rhel6.1 32bit
- SLES 11 SP2 GMC: Enable support for Lnx NIC Driver
- SRIOV: When VGT is configured for a VF, ip link show doesn't display it for the VF configured.
- RHEL 5.8 GA: Enable support for Lnx NIC Driver
- ip link command with vlan = 4095 has toggling effect
- ip link command with vlan =0 should remove guest VGT privilege

===============================================================================

Linux NIC Device Driver Version 4.1.334.39

- SR-IOV: Can't load be2net driver in a VM after the VM has been rebooted
- SR-IOV: Unload PF driver with VF driver loaded causes system instability
- SR-IOV: VF MAC always gets Emulex OUI
- SR-IOV: Partition the limited per port VLAN entries across VFs and PFs
- Non Member VLAN packets not received in interface promiscuous mode in BE3
- Avoid CQ full condition in HW
- be2net: use RX_FILTER cmd to program multicast addresses
- account for skb allocation failures in ethtool stats
- Support 60 second delay to Linux NIC driver to allow FAT dump completion on recovery from EEH
- Link status is up [ethtool and OCM] when the bandwidth is assign 0 for UMC configuration
- Remove msix module parameter
- Use V1 version of COMMON_NTWK_LINK_STATUS_QUERY for Lancer.
- Emulex: Ethtool failing to update FW
- Emulex: Panic in be2net driver in SLES11-SP2-B7 on adapter
- TCP ACKs from different connections are getting received in single queue
- Multicast filtering feature not working on PPC
- Exit of mcast promiscous mode not working
- VLAN promiscous mode cannot be set on Lancer
- Can't communicate after changing MAC address via VLAN interface
- Improper memory accounting in received packets
- WOL changes for Linux NIC driver as mentioned in bug
- Transparent VLAN tagging feature not working in SR-IOV
elx_dd_nic_ibm1206-4_2_389_0_rhel6_32-64_chg

LSI 1064e SAS Controller BIOS and Firmware Update for BladeCenter HS22V
BIOS v6.30.02.00, Firmware v1.30.10.00 and uEFI Driver v3.12.00.07

Systems Supported: IBM BladeCenter HS22V (7871)

NOTE TO SERVICE - Reference RETAIN #N/A

NOTE: This change history is common between several of the IBM and LSI Basic
or Integrated RAID SAS controllers for BOFM enabled, uEFI systems.
Not all levels were released for all controllers.


Version 2.75 - Critical
------------
Contains:
- BIOS Version: 6.30.02.00
- Firmware Version: 1.30.10.00
- BSD Version: 3.12.00.07

BSD Fixes:
- Fixed an issue where the controller was hanging during initialization
when an adapter was hung in reset with insufficient information to reset
itself.
- Fixed an issue where the SAS MPT BIOS CU reports wrong array size.


Version 2.74 - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.10.00
- BSD Version: 3.12.00.07

BSD Fixes
- Removed the "SAS/SATA missing" warning message when SAS and SATA arrays
are present on the same controller.
Firmware Fixes
- Addressed issue where 6Gb SATA drives will only negotiate at 1.5Gb/s
instead of 3Gb/s.
- Fixed issue where SAS/SATA mixing errors will occur when the controller
is setup to allow mixing of devices.
- Fixed issue with large topology of SATA drives where media errors on a
single drive will cause one phy to hang after IOs to other drives start
to timeout.
- Fixed discovery Error 0x2 in maximum topology with SATA devices,
- Addressed issue where Credit would be stuck at zero until controller
resets resulting in a phy becoming hung and IO failing. Only occurs
with very high IO.

Version 2.72 - Suggested
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.05.00
- BSD Version: 3.12.00.06

Enhancement
- Support 2TB LUNS and greater

Fixes:
- Addressed issue with SATA devices where the drive could go missing for
several minutes.
- Fixed issue where incorrect release of scatter gather list could cause
issues with pending IO to missing devices.
- Addressed issue where IOs to a host with a bad drive could fail.

Version 2.71 - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.03.00
- BSD Version: 3.12.00.05

Fixes:
- Fixed issue where Target mode responds with incorrect WWID after ports are
swapped.
- Fixed issue with Incorrect/Unexpected discovery errors on RAID storage
enclosures.
- Fixed issue where device added events are not sent to the host on RAID
storage enclosures.
- Fixed issue where it is possible for a Incorrect/Duplicate Device handle
to get assigned to a target that is a SSP Initiator.
- Changed IO Delay missing setting to 144 seconds
- Fixed problem of the boot order selection not being saved


Version 2.70a - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.00.00
- BSD Version: 3.12.00.05

Fixes:
- Address issue in BSD code where the RegisterSupport() for all handles are
called incorrectly.

Enhancement:
- Supress Link Error Count in EFI Configuration Utility


Version 2.70 - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.00.00
- BSD Version: 3.12.00.03

Fixes:
- Changed BIOS text to state an IS Volume creation can be 1 to 10 drives.
- Fixed issue with 2TB and above drives where SAS MPT BIOS CU reports wrong
array size.
- Adjusted NVSRAM access timing to fix an issue that could prevent controller
detection during POST.
- Addressed an issue that will maintain Target IDs for attached devices to
an enclosure if the enclosure is removed for a short time.

Functionality:
- Initial release for:
BladeCenter HS22V onboard LSI 1064e controller


Version 2.69b - Non-critical
-------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.88.00
- BSD Version: 3.12.00.03

Enhancement:
- Added support for Blade Open Fabric Manager (BOFM) for uEFI Blades.


Version 2.69 - Suggested
------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.88.00
- BSD Version: 3.10.00.01

Fixes:
- Fixed an issue where, after running heavy I/O to NCQ enabled SATA drives,
the controller may log false data underruns for read or write I/Os. The
PHY on which the I/Os were reported as underrun may eventually lock up.


Version 2.66 - Suggested
------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.86.00
- BSD Version: 3.10.00.01

Fixes:
- Fixed an issue where Solid State Drives (SSDs) were not seen after a link
reset.
- Fixed an issue where direct attached SATA drives were not reported missing
after they were removed. This could result in degraded or failed volumes
being reported as healthy.
- Fixed an issue introduced by new functionality in package 2.50. The issue
would cause a dual attached device to be hidden from both the direct
connection and the expander connection.
- Changed the behavior during drive quiescing/un-quiescing to prevent the
drive metadata from being unnecessarily updated.
- Fixed an issue where drives might go offline during a firmware update, due
to I/O timeouts caused by the length of time needed to update the firmware.


Version 2.63 - Suggested
------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.83.00
- BSD Version: 3.10.00.01

Fixes:
- Fixed an issue where volumes can become inactive due to the metadata on the
drives getting out of synch with NVSRAM.

Functionality:
- Initial release for:
BladeCenter HS22 onboard LSI 1064e controller
ibm_fw_mptsas_hs22v-2_75_linux_32-64_chg

===============================================================================
Emulex iSCSI Device Driver for Linux
===============================================================================

Linux iSCSI Device Driver Version: 4.2.398.0

Problems Fixed:
- Cleaned up a cosmetic problem with warning messages during driver compile from source

Incremental Interoperability:
- RHEL6.3 GA Kernel

Known Issues:
- None

==============================================================================

Linux iSCSI Device Driver Version 4.1.402.0

Problems Fixed:

- LUN is not getting detected for OEM CNA in SLES 11 SP2 64 bit OS
- ioctl semaphore deadlock when running load/unload loop with target
- SLES 11 SP2 GMC: Enable support for Lnx iSCSI Driver
- RHEL 5.8 GA: Enable support for Lnx iSCSI Driver

==============================================================================

Linux iSCSI Device Driver Version 4.1.334.39

Problems Fixed:

- Emulex: Warning messages seen while building Emulex drivers on RHEL platform
- Unable to load be2iscsi driver during iSCSI boot OS install
- Modprobe be2iscsi hangs when system with max targets login
- be2iscsi unload hangs the system
- fw rebooted on 1st mbox cmd after driver load > unload > load
- Failed to initialize iscsi driver
- need to define DMA_32BIT_MASK / DMA_64BIT_MASK in Linux kernel 3.x.x
elx_dd_iscsi_ibm1206-4_2_398_0_rhel6_32-64_chg

uEFI, BIOS and FW Update for SSD Expansion Card (CIOh) for BladeCenter
BIOS v6.30.02.00, Firmware v1.30.10.00 and uEFI Driver v3.12.00.07

Controllers Supported:
- IBM SSD Expansion Card (CIOh) for IBM BladeCenter (59Y5962)

NOTE TO SERVICE - Reference RETAIN #N/A

NOTE: This change history is common between several of the IBM and LSI Basic
or Integrated RAID SAS controllers for BOFM enabled, uEFI systems.
Not all levels were released for all controllers.

Version 2.75 - Critical
------------
Contains:
- BIOS Version: 6.30.02.00
- Firmware Version: 1.30.10.00
- BSD Version: 3.12.00.07

BSD Fixes:
- Fixed an issue where the controller was hanging during initialization
when an adapter was hung in reset with insufficient information to reset
itself.
- Fixed an issue where the SAS MPT BIOS CU reports wrong array size.


Version 2.74 - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.10.00
- BSD Version: 3.12.00.07

BSD Fixes
- Removed the "SAS/SATA missing" warning message when SAS and SATA arrays
are present on the same controller.
Firmware Fixes
- Addressed issue where 6Gb SATA drives will only negotiate at 1.5Gb/s
instead of 3Gb/s.
- Fixed issue where SAS/SATA mixing errors will occur when the controller
is setup to allow mixing of devices.
- Fixed issue with large topology of SATA drives where media errors on a
single drive will cause one phy to hang after IOs to other drives start
to timeout.
- Fixed discovery Error 0x2 in maximum topology with SATA devices,
- Addressed issue where Credit would be stuck at zero until controller
resets resulting in a phy becoming hung and IO failing. Only occurs
with very high IO.

Version 2.72 - Suggested
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.05.00
- BSD Version: 3.12.00.06

Enhancement
- Support 2TB LUNS and greater

Fixes:
- Addressed issue with SATA devices where the drive could go missing for
several minutes.
- Fixed issue where incorrect release of scatter gather list could cause
issues with pending IO to missing devices.
- Addressed issue where IOs to a host with a bad drive could fail.

Version 2.71 - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.03.00
- BSD Version: 3.12.00.05

Fixes:
- Fixed issue where Target mode responds with incorrect WWID after ports are
swapped.
- Fixed issue with Incorrect/Unexpected discovery errors on RAID storage
enclosures.
- Fixed issue where device added events are not sent to the host on RAID
storage enclosures.
- Fixed issue where it is possible for a Incorrect/Duplicate Device handle
to get assigned to a target that is a SSP Initiator.
- Changed IO Delay missing setting to 144 seconds
- Fixed problem of the boot order selection not being saved


Version 2.70a - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.00.00
- BSD Version: 3.12.00.05

Fixes:
- Address issue in BSD code where the RegisterSupport() for all handles are
called incorrectly.

Enhancement:
- Supress Link Error Count in EFI Configuration Utility


Version 2.70 - Critical
------------
Contains:
- BIOS Version: 6.30.00.00
- Firmware Version: 1.30.00.00
- BSD Version: 3.12.00.03

Fixes:
- Changed BIOS text to state an IS Volume creation can be 1 to 10 drives.
- Fixed issue with 2TB and above drives where SAS MPT BIOS CU reports wrong
array size.
- Adjusted NVSRAM access timing to fix an issue that could prevent controller
detection during POST.
- Addressed an issue that will maintain Target IDs for attached devices to
an enclosure if the enclosure is removed for a short time.

Functionality:
- Initial release for:
BladeCenter HS22V onboard LSI 1064e controller
SSD Expansion Card (CIOh) for IBM BladeCenter


Version 2.69b - Non-critical
-------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.88.00
- BSD Version: 3.12.00.03

Enhancement:
- Added support for Blade Open Fabric Manager (BOFM) for uEFI Blades.


Version 2.69 - Suggested
------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.88.00
- BSD Version: 3.10.00.01

Fixes:
- Fixed an issue where, after running heavy I/O to NCQ enabled SATA drives,
the controller may log false data underruns for read or write I/Os. The
PHY on which the I/Os were reported as underrun may eventually lock up.


Version 2.66 - Suggested
------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.86.00
- BSD Version: 3.10.00.01

Fixes:
- Fixed an issue where Solid State Drives (SSDs) were not seen after a link
reset.
- Fixed an issue where direct attached SATA drives were not reported missing
after they were removed. This could result in degraded or failed volumes
being reported as healthy.
- Fixed an issue introduced by new functionality in package 2.50. The issue
would cause a dual attached device to be hidden from both the direct
connection and the expander connection.
- Changed the behavior during drive quiescing/un-quiescing to prevent the
drive metadata from being unnecessarily updated.
- Fixed an issue where drives might go offline during a firmware update, due
to I/O timeouts caused by the length of time needed to update the firmware.


Version 2.63 - Suggested
------------
Contains:
- BIOS Version: 6.26.00.00
- Firmware Version: 1.27.83.00
- BSD Version: 3.10.00.01

Fixes:
- Fixed an issue where volumes can become inactive due to the metadata on the
drives getting out of synch with NVSRAM.

Functionality:
- Initial release for:
BladeCenter HS22 onboard LSI 1064e controller
ibm_fw_mptsas_bc-ssdexp-2_75_linux_32-64_chg

===============================================================================
Emulex Firmware Package
===============================================================================

Firmware Version: 2.01a9 (w/ 5.12a11 Universal Boot Code)

Incremental Interoperability:
- None

Problems Fixed:
- BIOS compatibility issues in some IBM Rack servers

Known Issues:
- None

===============================================================================

Firmware Version: 2.01a9 (w/ 5.12a10 Universal Boot Code)

Incremental Interoperability:
- UEFI 2.3.1 compatibility

Problems Fixed:
- Utility in adapter selection screen shows PCIe2.5Gb/s X 4
- Miscellaneous issues with boot BIOS
- Emulex 8gb ciov Port2 does not accept BOFM Boot-order "both"
- Rhel 6.2 UEFI San boot failed w/ Emulex 8Gb FC
- Fix potential I2C bus contention

Known Issues:
- None

===============================================================================

Firmware Version 2.01a3 (w/ 5.12a5 Universal Boot Code)

New Features

* Enhanced timeout notifications for processing abort failures.

Problems Fixed:

1. All multi-abort I/Os are returned on the same ring from which the ABORT_MXRI
command was received.

2. Changed the TRCV response in the abort state to CMD RJT to enable the
TRSP to be processed.

3. Corrected an issue with blocked TSEND operations.

4. Corrected a buffer leak issue with RRQ exchanges.

5. Corrected an issue where the TRCV IOCB was de-queued improperly causing a
XFR_RDY flood.

6. Corrected an issue where the OXID field was not loaded in the XRI_ABORTED IOCB.

7. Corrected an issue in recognizing whether an EEPROM is present.


Dependencies:
- The corresponding FC Storport device driver and OneCommand Manager Core-kit
(management) will need to be installed for this package to function properly.

--------------------------------------------------------------------------------

Universal Boot Code version 5.12A5

This Universal Boot version 5.12a5 contains:

(1) x86 BootBIOS version 2.12a9

Problems fixed, features added or other updates:

1. 118933 Fixed an issues booting when more than 8 ports are present in the
system and fixed an adapter display issue when more than 8 ports
are present in the systems
2. 118933 Fixed issues installing and booting O/Ss on ports greater than 8.
3. 121923 Fixed issues installing and booting O/Ss on ports greater than 8.
4. 122286 Fixed some boot time screen display issues.

(2) OpenBoot version 3.10a3

This version of OpenBoot supports FC-AL, Private loop, Public loop, and
Fabric Point to Point. Also, it supports multi-initiators and multi-LUNs
(0 through 4055)

Problems fixed, features added or other updates:

1. Unrelated to IBM

(3) EFIBoot version 4.12a12

The current EFI (Extensible Firmware Interface) Boot provides 64-bit System
boot capability through the use of the EFI Shell. This EFIBoot supports EFI
Specification 1.10 and EFI Source Code version 1.10.14.61.

Problems fixed, features added or other updates:

1. Only certain OEM HBAs will locate PlatformToDriverConfigurationProtocolGuid.
Others just skip and continue processing
2. UEFI2.3 Hii Configuration Utility changes
3. HII Browser Save option does not work

===============================================================================

Firmware Version 2.00a4

Problems Fixed:

1. CR105423 - On a port connected to a 3PAR "MBOD" cage, the test runs IO
to the disk drives and issues a "controlport offline" command to offline
the port while IO is running.

2. CR111194 - While doing target side cable pull testing with Block Guard (T10)
Enabled we observed that adapter is not sending RSCN to AIX.

3. CR111625 - *IBM defect 775960 - HBQ ring index pointers?

4. CR111669 - Adapter trap - Block Guard firmware - HOST status register : 0x100146

5. CR111928 - 3PAR - LR with port and subsequent FLOGI failing.


Dependencies:
- The corresponding FC Storport device driver and OneCommand Manager Core-kit
(management) will need to be installed for this package to function properly.
elx_fw_fc_ibm1206-2_01a9_linux_32-64_chg

Multiboot Image for QLogic Fibre Channel Expansion Cards for IBM BladeCenter
Release Notes Version f5.07.01-b2.38-e2.38
11/20/12
===============================================================================

A. BIOS Release Notes
B. EFI Release Notes
C. FCODE Release Notes
D. No Release Notes for Firmware

Versions = BIOS-2.13, EFI-2.38, FCODE-3.14, Firmware-5.07.01

===============================================================================
A. QLogic BIOS for IBM FC Adapters
Release Notes

This software license applies only to QLogic customers.
QLogic Corporation.
All rights reserved.


Table of Contents

1. Version
2. Changes
3. Bug Fixes
4. Known Issues
5. Additional Information
6. Trademarks
7. Notices
8. Contacting Support


1. Version

These release notes describe the changes, fixes, known issues, and release
details that apply to the multi-boot package for the IBM QMI2572/QMI3572/QMI2582.

* Reference the Read1st.txt for the kit version information.


2. Changes

These release notes describe the changes, fixes, known
issues, and release details that apply to BIOS version 2.13


Hardware Support

* Supports QMI2572/QMI3572/QMI2582

Software Components

N/A

Industry Standards Compliance

N/A


3. Bug Fixes


Rev 2.00 Dec.04, 2007
Initial release.
Custom BIOS with BOFM support for IBM
Rev 2.01 Dec. 10, 2007 - Fixed issue with handling 'DFLT' BOFM
opton
Rev 2.02 Mar. 29, 2008 - Added code to setup EDI for alternate
adapter.
Rev 2.03 Jan. 05, 2009 - Changed code to return good status
when 'FC' section not found in BOFM.
Removed check for 'Comsumed' flag
when setting BOFM targets.
Fixed issue with KVM.
Rev 2.04 Mar. 05, 2009 - Fixed comestic bug is CTRL-Q utility
in displaying selectable boot lun.
Changed code to correctly display boot
device type.
Removed 8G support for QMI2572
Added support for UEFI environment.
Rev 2.05 Apr. 28, 2009 - Added support for ISP8001.
Rev 2.06 May 08, 2009 Fixed bug in restoring MAC Address.
Rev 2.07 Jul. 17, 2009 - Added code to save a backup copy of
NVRAM data and use it if primary is
corrupted.
Rev 2.08 Jul. 30, 2009 - Changed code to not Disable BIOS when
no BOFM drives configured.
Rev 2.09 Mar. 09, 2010 - Added code to update MAC address if
PXE BOFM MAC address configured.
Fixed bug in setting buffer pointer.
Rev 2.10 May. 27, 2010 - Changed Link-up timer to 30 seconds.
Rev 2.11 Nov. 17, 2011 - Added code to use Echo Test instead of
Loopback for F_PORT connection.
Added code to update EDC.
Removed support for CLP strings.
Added check for SSDID = 176h for EDC.
Rev 2.12 Jan.11,2012 - Added code code to check for non-EDC
HBA's in CTRL-Q utility.
Rev 2.13 Jan,23,2012 Fixed bug in EDC update code.


4. Known Issues

None


5. Additional Information


6. Trademarks

QLogic, the QLogic logo, QLA, QLE, QMI, SANbox, SANsurfer, and SANblade
are registered trademarks of QLogic Corporation.

SANtrack and SAN Express are trademarks of QLogic Corporation.

All other brand and product names are trademarks or registered
trademarks of their respective owners.


7. Notices

Information furnished in this document is believed to be accurate and
reliable. However, QLogic Corporation assumes no responsibility for
its use, nor for any infringements of patents or other rights of
third parties which may result from its use. QLogic Corporation
reserves the right to change product specifications at any time
without notice. Applications described in this document for any of
these products are only for illustrative purposes. QLogic Corporation
makes no representation nor warranty that such applications are
suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any
errors that may appear in this document.


8. Contacting Support

Please feel free to contact your QLogic approved reseller or QLogic
Technical Support at any phase of integration for assistance. QLogic
Technical Support can be reached by the following methods:

Web: http://support.qlogic.com
North America Contact Information

Email: support@qlogic.com
Phone: (952) 932-4040

Support contact information for other regions of the world is
available at the QLogic website: http://support.qlogic.com


(c) Copyright 2009. All rights reserved worldwide. QLogic, the QLogic
logo, and the Powered by QLogic logo are registered trademarks of
QLogic Corporation. All other brand and product names are trademarks
or registered trademarks of their respective owners.



===============================================================================
B.

Driver Name : Fibre Channel Driver for UEFI
Version : 2.38
Date : 11/3/2011
OS platform : N/A
FW version : See MultiBoot release notes for FW version.
Efiutil Version : 3.11


Table of Contents
I. Overview
II. Enhancements
III. Bug Fixes
IV. Known Issues
V. Additional Information


I. Overview

The following document provides details of the Fibre Channel UEFI driver
version 2.38, Efiutil version 3.11.


II. Enhancements

Driver:
* Added EDC update support. (ER86772)
* Reduced driver size. (ER86772)

Efiutil:
* Added EDC update support. (ER86772)


III. Bug Fixes

Driver:
* Removed EDC fields from QLE25xx HII screens. (ER86772)
* HII EDC fields now ignore Global Parameters with a bad checksum.
(ER86772)


IV. Known Issues

* In the HII menus, Adding/Deleting a Target/LUN will require a reboot for
changes to take effect.


V. Additional Information

* Efiutil and the EFI Driver are a matched set. Always make sure
that Efiutil and the EFI Driver are from the same release package.




===============================================================================
C.
QLogic Fcode for IBM FC Adapters
Release Notes

This software license applies only to QLogic customers.
QLogic Corporation.
All rights reserved.


Table of Contents

1. Version
2. Changes
3. Bug Fixes
4. Known Issues
5. Additional Information
6. Trademarks
7. Notices
8. Contacting Support


1. Version

These release notes describe the changes, fixes, known issues, and release
details that apply to the multi-boot package for the QMI2572/QMI3572/QMI2582.

* Reference the Read1st.txt for the kit version information.


2. Changes


These release notes describe the changes, fixes, known
issues, and release details that apply to FCode version 3.09

Hardware Support

* QMI2572/QMI3572/QMI2582

Software Components

N/A

Industry Standards Compliance

N/A


3. Bug Fixes

Code Changes:

version 3.17b2 10/18/11
* Added SSDID check to set-edc-config. Print Not supported message if not Guppy.
* Stripped ISP2400 & SUN specific code using #ifdefs to reduce IBM size by .5KB

version 3.17b1 10/13/11
* Added EDC FW area in Flash and added write-sfp and read-sfp mailbox commands
* Added set-edc-config, edc-update?, and edc-present! words to nvram.fth.(IBM)
* Added check-edc-load and load-edc-fw words to init-isp.fth for Guppy.(IBM)

version 3.16 09/30/11
* Change PCI-Cmd-Reg value, pci-cmdv, to x146. Add System Error Resp Enable.
* Change MBAR0 size (/regs) from x1000 to x4000 to include MSI-X table.
* Add setting Prefetchable bit if enabled for MBAR0 in map-ifp-regs(read-bar).
* Fix close-hardware to logout-devices if Link-up?, not done-fw-init? flag.
* Add "Problem fixed" printout when validate-nvram fixes the backup copy.
* Change init-image & init-fw to return error? flag on stack so you can abort.
* Fix all mboxs commands to write 0 to all mboxes used by FW, don't assume =0.
* Add clr-flags after a wait-for-risc-int timeout, which will restart the FW.
* Change all Copyright messages to: "Copyright 1999-2011".
* Change mbox-test to actually do some pattern testing and compare data.
* Added 31 second SW timeout for IOCB & mailbox commands in wait-for-risc-int.
* Add retry SCSI command once if IOCB timeout & 8048 Recv. error AEN received.
* Fix stop-fw mailbox command. Clear Bit 1 (Transition to ROM Code) in Mbox-1.

* Utility/Debug changes
1 Change version method for INIT only version to also show FW version.
2 Change find-ilt-code to check Chip-Rev & Card-Type-List in ILT header search
3 Change ilt-valid? to check for Signature Word "QILT" and ILT veersion field
4 Add "Load Raw FW image?" prompt and max-FW-code-size check to ldfw method.
5 Add debug? option debug-probe? (x10000) to disable card access during probe.
6 Fix bug in flash utility which was not setting my_did if the FLT is invalid.

version 3.15 09/29/10
* Utility/Debug changes
1 Add debug? flag: 8000= Dump all mailboxes on all AENs and all Mbox commands.
2 Fix problem in ldfcode Flash utility. INIT version was not setting my_did.

* Boot-wait-time related changes
1 Change boot-wait-time back to v3.12. Now link-down-to will wait if enabled.
2 Change device-present? to exit immediately if the link-up? flag is not true.
3 Fix show-children to not use boot-wait-time for link-down-to timeout value.
4 Fix device-present? to not restart BW-timer. Start-time set in isp-fw-ready?.

version 3.14 04/30/10
* Change validate-nvram to compare only the NVRAM area, not the entire sector.
* Change makefile to used the DID variable for the File name & in PCI header.

version 3.13 03/26/10
* Remove Hard-RICS-reset from reset-risc method & add 100ms delay after reset.
* Make old-sb (old sec-buf) an instance value. Problem on M3000 (ER70453).
* Fix Explicit logout-device IOCB to include the ISP PortID and Port WWN.
* Change login-devices to not logout with FC_Initiators.

* Boot-wait-time related changes
* Change get-to-params to set boot-wt = 8 secs if boot-wait-time is disabled.
* Change set-boot-wait-time to not affect link-down-to (timeout) for Fujitsu.
* Change set-boot-wait-time to be entered/display in decimal, not hex(Fujitsu).

* Additions made for debugging:
1 Changed debug? flags: 4000= Got-R2H-intr, 2000= IOCB-Dump, 800=FW-Ready-wait
2 Add Parameter 1 debug display on login IOCB faliure.
3 Add force-open-ok? test flag in open method. Default = true(no real change).

* Changes to make process and Flash utilities:
1 Use OpenBIOS Toke Tokenizer to make isp2500.
2 Add Sun-Style-Checksum option OpenBIOS Toke for SUN isp2500.

Version 3.12 01/11/10
* Fixed sunid (SUNW,qlc) for the SUN CNA QLE8142. The SSDID is 183, not 182.
* Add flashing support for mpi-config-image from Image-Layout-Table(ILT) File.
* Add check for Card-Type & Swap bits in Image-Layout-Table(ILT) Flash utility.

Version 3.11 12/11/09
* Add support for Sun (SUNW,qlc) CNA QEM8152.

Version 3.10 12/02/09
* Add support for Sun (SUNW,qlc) CNAs QLE8140, QlE8142, QLE8150, & QLE8152.

Version 3.09
* Fix Node-Name-Option bit preservation in restore-default-settings.

Version 3.08
* Fix default WWNN & WWPN preservation in restore-default-settings.
* Add standard properties. Use m4 utility to automaticly create date string.
* Add file rev_level.m4 which has the revision level strings only.
* Change messages "Login failed" to "Login Abort". "Error Subcode" to "Subcode".
* Remove patch of PCI header image size byte at offset 0x2c from init version.


Version 3.07
* Fix read-cap16-cmd. Used when the LUN size is >2TB (i.e. #blocks > 32-bits).
* Fix disk-test to work with large (>2TB) LUNs, where the LBA > 32-bits.
* Remove command retry when 8048 AEN is received.

Version 3.06
* Add option for qlgc-debug? in nvramrc. If the diag-switch? is true,
then the debug? flag is set is set to the value of qlgc-debug?.
* Add lba64 large disk capability (read-blocks64 write-blocks64) for SUN only.
* Add mbox1 & mbox2 display for 8048 interrupt if debug-asyc? flag (01) is on.
* Add more IOCB debugging, Add Erase Response-Queue in mapmem. Had stale data.
* Add more debugging for IOCBs, dma-map-in/out, & wait-for-interrupts.

Version 3.05
* Re-structure devicepresent.fth. Add set-phandle to set obp-target & obp-portid
* Fix multiple close issue found with IBM ioinfo utility.

Version 3.04
* Add alloc-sec-buf & free-sec-buf words with debugging messages.
* Removed VPD validation from validate-nvram due to bug in update utilities.

Version 3.03
* Change validate-nvram to check both FC ports on Dual-port CNAs at probe time.
* Fix init-flt-offsets to mask FLT attributes. Now it finds FW & Feature-key.
* Add NVRAM backup Sector. Add validate-nvram at probe time to fix corruption.

Version 2.05 03/26/09
* Change all FLT Flash offset parameters from constants to values.

Version 2.04 12/03/08
* Add debug message to init-flt-offsets " Init FLT offsets" for ISP2500 only.
* Add FLT and FDT Flash access methods
* Remove set-bootid, set-boot-wwn, & releated qla only words from IBM version.
* Added IBM debugging to BOFM words and set debug?=C00 if diag-switch is true.
* Added max-payload bridge fix for 4-port QMI2564 HBA. Used Gil's method.
* Fix get-mail to handle Response-Queue interrupts (stat=13) & add debugging.
* Removed all Serial-Link-Control access/modify words from ISP2500 only.
* Fix open to always return -1. Returning link-down fw-state fails on Serengetti



3.02 Initial release.


4. Known Issues

None


5. Additional Information


6. Trademarks

QLogic, the QLogic logo, QLA, QLE, QMI, SANbox, SANsurfer, and SANblade
are registered trademarks of QLogic Corporation.

SANtrack and SAN Express are trademarks of QLogic Corporation.

All other brand and product names are trademarks or registered
trademarks of their respective owners.


7. Notices

Information furnished in this document is believed to be accurate and
reliable. However, QLogic Corporation assumes no responsibility for
its use, nor for any infringements of patents or other rights of
third parties which may result from its use. QLogic Corporation
reserves the right to change product specifications at any time
without notice. Applications described in this document for any of
these products are only for illustrative purposes. QLogic Corporation
makes no representation nor warranty that such applications are
suitable for the specified use without further testing or
modification. QLogic Corporation assumes no responsibility for any
errors that may appear in this document.


8. Contacting Support

Please feel free to contact your QLogic approved reseller or QLogic
Technical Support at any phase of integration for assistance. QLogic
Technical Support can be reached by the following methods:

Web: http://support.qlogic.com
North America Contact Information

Email: support@qlogic.com
Phone: (952) 932-4040

Support contact information for other regions of the world is
available at the QLogic website: http://support.qlogic.com


(c) Copyright 2009. All rights reserved worldwide. QLogic, the QLogic
logo, and the Powered by QLogic logo are registered trademarks of
QLogic Corporation. All other brand and product names are trademarks
or registered trademarks of their respective owners.



===============================================================================
D. QLogic Firmware for IBM FC Adapters
(No Release Notes for Firmware)
qlgc_fw_fc_8g-f50701-b213-e238_linux_32-64_chg

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

Broadcom Linux bnx2 and 10GigE Virtual Bus Drivers(VBD)

Version 2.2.3f
02/06/2013
Copyright (c) 2004 - 2013 IBM Corporation
All rights reserved


NOTE:
These driver release information is the original from the vendor. They include multiple driver
change histories for multiple Linux Operating Systems. Some drivers may or may not
pertain to all Linux Operating Systems but are part of this file for references.

====================================================================================================
Original file from Vendor...


Release Notes
Broadcom bnx2 Linux Driver
Version 2.2.3f
10/25/2012
Broadcom cnic Linux Driver
Version 2.5.12e
08/22/2012

Broadcom Corporation
5300 California Avenue,
Irvine, CA 92617

Copyright (c) 2004 - 2013 Broadcom Corporation
All rights reserved

bnx2 2.2.3f (Oct 25, 2012)
==========================
Enhancements
------------
1. Change: (CQ65960) Make minor compatibility changes to support RHEL6.4

Impact: None.


bnx2 2.2.3e (Aug 27, 2012)
==========================
Fixes
-----
1. Problem: ESX 6.0 compile errors seen when disabling NetQueue

Cause: Unused variables were defined in the non-NetQueue path

Change: Clean up code to compile on ESX6.0 inbox

Impact: ESX only


2. Problem: ESX 6.0 firmware dump missing 1 dword.

Cause: MCP dump size is incorrect.

Change: Use correct MCP dump size.

Impact: ESX 6.0 only

cnic 2.5.12e (Aug 22, 2012)
==========================
Fixes
-----
1. Problem: (CQ 65270): bnx2x IRQ assert on 57712 and newer devices that
support iSCSI only.

Cause: Not arming IRQ properly when detecting that the device does not
support FCoE. Regression from cnic 2.5.12c enhancement #3.

Change: Added function pointer to arm IRQ correctly based on chip type.

Impact: iSCSI and FCoE on all 10G devices.

cnic 2.5.12d (Aug 21, 2012)
==========================
Fixes
-----
1. Problem: (CQ 65249): cnic panic on functions that support FCoE only.

Cause: Code accessing iSCSI resources that aren't initialized or
allocated on functions that don't support iSCSI.

Change: Check for valid UIO resource before trying to free it. Always
initialize iSCSI OOO resources.

Impact: 10G iSCSI and FCoE.

bnx2 2.2.3d (Aug 15, 2012)
==========================
Fixes
-----
1. Problem: (CQ 65163): unhandled NETQUEUE messages 16 and 17
seen in vmkernel logs

Cause: Not properly handling unsupported NetQueue ops

Change: Properly handle the NetQueue ops 16 and 17 without
printing the warning message

Impact: ESX only

Enhancements
------------
1. Change: Try to recover from PCI block reset during TX timeout.
Red Hat users have reported PCI block resets that could
not be recovered during tx timeout.

Impact: None.

2. Change: Added mk_kernel_patch.sh to patch bnx2 driver into kernel tree.

Impact: None.

cnic 2.5.12c (Aug 15, 2012)
==========================
Enhancements
------------
1. Change: Added firmware dump support for ESX6.0.

Impact: ESX6.0.

2. Change: Reduced maximum iSCSI abort delay to 5 seconds

Impact: iSCSI

3. Change: Allocate FCoE or iSCSI resources on a cnic only if the
device supports the protocol. This will reduce memory
consumption on multi-function devices.

Impact: iSCSI and FCoE

bnx2 2.2.3c (July 09, 2012)
==========================
Fixes
-----
1. Problem: Unmapping the wrong DMA address in bnx2_free_tx_skbs() in
rare cases.

Cause: Not skipping the last entry in the tx BD ring.

Change: Use the proper macro to get the next BD entry.

Impact: On systems with IOMMUs enabled, the bug can be triggered when
doing resets (ifdown, MTU change) during heavy TX traffic.

cnic 2.5.12b (July 03, 2012)
=============================
Enhancements
------------
1. Change: Updated to bnx2x firmware 7.4.8 HSI for TX BDs.

Impact: iSCSI on all bnx2x devices.

cnic 2.5.11d (June 28, 2012)
=============================
Fixes
-----
1. Problem: Kernel panic under iSCSI OOO condition.

Cause: Bug in cnic when max OOO resource is reached

Change: Initailized packet descriptor to fix the bug.

Impact: iSCSI only.

bnx2 2.2.3b (June 29, 2012)
==========================
Fixes
-----
1. Problem: Compile error in RHEL6.x kernel and similar kernels.

Cause: skb_frag_size() compatibility code not detected properly.

Change: Fixed Makefile to detect it from skbuff.h

Impact: None.

bnx2 2.2.2b (June 24, 2012)
==========================
Fixes
-----
1. Problem: (CQ63682)PSOD in ESX upon device open.

Cause: NAPI was not disabled properly upon device close.
Thus, ASSERT occurs upon reopening device.

Change: Add NAPI disable upon close and add netif_tx_disable
for both linux and ESX build.

Impact: bnx2.

2. Problem: Enableing RSS interferes with RX NETQ feature when
compiled for ESX build.

Cause: RSS is enabled by default in bnx2. The RSS feature
will lead to firmware bypass NETQ code path.

Change: Disable RSS by default when compiled for ESX.

Impact: ESX.

Enhancements
------------
1. Change: Partial sync-up with upstream driver. Please see Changelog.

Impact: All

cnic 2.5.11c (June 12, 2012)
=============================
Fixes
-----
1. Problem: (CQ62298 Partial fix) When running in INTA mode, MTU change
does not work. iSCSI/FCoE does not resume after MTU change.

Cause: During mtu change, bnx2x does not know that cnic is no longer
handling IRQs.

Change: Added a new flag to let bnx2x know that cnic is no longer
handling IRQ during reset.

Impact: bnx2x iSCSI and FCoE.

2. Problem: (CQ62937) bnx2x asserts during iSCSI test with corrupted
TCP NOP-IN.

Cause: Corrupted NOP-IN falls outside of TCP window, causing FW to
go into OOO mode. TCP close with outstanding OOO causes
problem and the close does not complete.

Change: FW change to return an error in this case and cnic driver
change to handle this error by proceeding to clean up the
connection.

Impact: bnx2x iSCSI.

cnic 2.5.11b (April 30, 2012)
=============================
Fixes
-----
1. Problem: (CQ62298 Partial fix) Fix for CQ62026 in cnic 2.5.9d introduced
a regression of clearing the CNIC_UP flag before all CIDs have
been deleted. The regression is causing warning messges that
some CIDs have not been deleted. After fixing this, we're
still encountering further bnx2x error messages in the INTA
code path.

Change: Wait for all CIDs to be deleted before clearing CNIC_UP flag.

Impact: iSCSI and FCoE on all bnx2x devices.

bnx2 2.2.1l (April 18, 2012)
============================
Fixes
-----
1. Problem: PSOD on ESX because of inconsistant NetQueue state
when the NetQueues are allocated/freed out of order

Cause: The forced freeing of the NetQueue before the
NetQueue allocation can cause the incorrect NetQueue
to be freed and marked incorrectly.

Change: Remove the freeing of the NetQueue in the allocation
path and allow the load balancer to control the
error path when NetQueue's could not be
allocated/freed.

Impact: ESX only.

cnic 2.5.10c (April 18, 2012)
=============================
Enhancements
------------
1. Change: Added iface_num parameter to cm_create() and
iscsi_nl_send_msg()to support bnx2i 2.7.2.2b.

Impact: iSCSI only.

bnx2 2.2.1k (April 04, 2012)
============================
Enhancements
------------
1. Change: Reduced code size of FTQ dump during tx_timeout.

Impact: None.

cnic 2.5.10b (April 04, 2012)
=============================
Enhancements
------------
1. Change: Added PCI pass through support for bnx2x E2/E3 devices.

Impact: bnx2x iSCSI/FCoE on E2/E3 devices.

bnx2 2.2.1j (Mar 07, 2012)
==========================
Enhancements
------------
1. Change: Added disable_msi_1shot parameter for debugging purposes.

Impact: VMWare only feature.

cnic 2.5.9d (Mar 07, 2012)
==========================
Fixes
-----
1. Problem: (CQ62026) NULL pointer dereference during cnic reboot test.

Cause: cp->ctx_tbl is NULL during cnic_ctl() call with COMPLETION_CMD.

Change: cnic is registered with the L2 drivers before we allocate
the cp->ctx_tbl so it is possible to get called while
cp->ctx_tbl is NULL. Added check for CNIC_UP flag before
proceeding to dereference cp->ctx_tbl. This together with
the RCU code will completely fix the problem.

Impact: iSCSI and FCoE on 10G.

bnx2 2.2.1i (Mar 06, 2012)
==========================
Fixes
-----
1. Problem: Driver doesn't build on SLES11.1-trace x32 kernel.

Cause: ARCH defined in Makefile conflicts with kernel tree scripts.

Change: Changed ARCH to __ARCH in Makefile

Impact: None.

bnx2 2.2.1h (Mar 05, 2012)
==========================
Fixes
-----
1. Problem: (CQ60393) Driver doesn't build in some RHEL-5.x distros with
just kernel-devel package installed.

Cause: Makefile does not include /usr/src/kernels/$(KVER)-$(uname -m)
in places to search.

Change: Added the additional path to check.

Impact: None.

cnic 2.5.9c (Feb 29, 2012)
==========================
Fixes
-----
1. Problem: (CQ61908) cnic does not compile on 3.x kernel.

Cause: Upstream patch titled:

ethernet/broadcom: ip6_route_output() never returns NULL.

backported carelessly.

Change: Fixed syntax errors.

Impact: 3.x kernel only.

cnic 2.5.9b (Feb 28, 2012)
==========================
Fixes
-----
1. Problem: (CQ61584) bnx2x asserts during middle-box iSCSI tests.

Cause: Middle-box test corrupts packets and causes iSCSI fw to
generate 0x4 (NIC_ERR) completion code. This conflicts
with new logic that uses NIC_ERR to convey parity error.

Change: Redefined parity error completion code to be 0x81 for
L4, iSCSI, and FCoE.

Impact: FCoE and iSCSI.

bnx2 2.2.1g (Feb 28, 2012)
==========================
Fixes
-----
1. Problem: Calling of bnx2_vlan_rx_kill_vid() is not rtnl_lock
protected.
Change: hold rtnl_lock when execute this routine under ESX4.0
and ESX4.1.
Impact: ESX4.0/4.1 only.

Enhancements
------------
1. Change: Added MSI-X table printout during tx timeout.

Impact: None.

bnx2 2.2.1f (Feb 8, 2012)
==========================
Fixes
-----
1. Problem: (CQ61327) Unable to pass traffic on RHEL5.x

Cause: bp->num_rx_rings not initialized due to backport errors. This
was introduced in 2.2.1e when adding ethtool -l|L support.

Change: Initialized bp->num_rx_rings to 1 on these older kernels.

Impact: RHEL5 and SLES10 only.

cnic 2.5.8f (Feb 06, 2012)
==========================
Enhancements
------------
1. Change: Added VLAN update from iscsiuio. This allows VLAN to be
specified in iface.

Impact: iSCSI only.

cnic 2.5.8e (Jan 24, 2012)
==========================
Enhancements
------------
1. Change: Enhanced FCoE parity recovery by sending immediate FW_DESTROY
completion with error during parity error recovery.

Impact: FCoE only.

bnx2 2.2.1e (Jan 24, 2012)
==========================
Enhancements
------------
1. Change: Added support for ethtool -[l|L]. Please refer to README.TXT
for details.

Impact: 5709 with support for MSIX only.

cnic 2.5.8d (Jan 19, 2012)
==========================
Enhancements
------------
1. Change: Enhanced FCoE driver registration to provide FCoE
capabilities to bnx2x driver.

Impact: Systems with Management support of these features. These
changes were made to match bnx2x 1.72.07.

2. Change: (CQ60867) Backed out earlier changes related to this CQ.
genksyms checksums are based on structure names and type
names, so the scheme of using an identical structure with
a different name will not work.

Impact: None.

cnic 2.5.8c (Jan 10, 2012)
==========================
1. Problem: (CQ60744) Lose connection to FCoE targets after parity error
recovery.

Cause: (Partial) DISABLE_CONN SPQ message does not complete, causing
delaying waiting for bnx2fc to timeout.

Change: Added immediate KCQ error completion for FCOE_DISABLE_CONN.
when SPQ fails.

Impact: FCoE.

2. Problem: (CQ60184) cnic parity error recovery fails (Part 2).

Cause: If a TCP connection fails due to parity error, termination
sequence does not follow the expedited error recovery path.
This causes unnecessary delay during parity error recovery.

Change: Set the HW_ERR bit when TCP connection fails due to SPQ
error. Termination will then follow the expedited error
recovery path.

Impact: iSCSI on bnx2x.

3. Problem: (CQ60867) Module versioning warning when installing cnic
driver on SLES11SP2 without matching bnx2i/bnx2fc.

Cause: cnic_register_driver() stub in cnic.c does not have
cnic_ulp_ops structure that matches inbox bnx2i/bnx2fc.

Change: Added dummy cnic_ulp_ops that match RHEL6.2 and SLES11SP2
structures.

Impact: None.

bnx2 2.2.1d (Jan 10, 2012)
==========================
Fixes
-----
1. Problem: PSOD seen in TX handling in either bnx2_tx_int()
or bnx2_start_xmit() routines

Cause: Memory re-ordering is occuring so that the TX BD is not
updated before the ringing of the TX doorbell.

Change: On ESX the wmb() macro is defined to only as a compiler
barrier. Redfine the wmb() macro to properly synchronize
memory using the sfence instruction.

Impact: ESX only.

cnic 2.5.8b (Jan 05, 2012)
==========================
Enhancements
------------
1. Change: Added CNIC_CTL_FCOE_ENHANCED_STATS_CMD and
CNIC_CTL_FCOE_CAPABILITIES_GET_CMD as stubs.

Impact: None.

cnic 2.5.7i (Dec 21, 2011)
==========================
Fixes
-----
1. Problem: (CQ60184) cnic parity error recovery fails.

Cause: SPQ errors during parity error recovery was not propagated to
L4 and ULP, causing unnecessary long timeouts.

Change: Added immediate KCQ error completion for L4 and iSCSI kwqes if
SPQ fails.

Impact: iSCSI on bnx2x.

bnx2 2.2.1c (Dec 21, 2011)
==========================
Fixes
-----
1. Problem: (CQ60281) BNX2 hang on ESX 4.1 when changing tx ring size
with Ethtool.

Cause: BNX2 set_ringparam() ethtool ops callback attempts to hold
rtnl_lock while vmlinux has already held this lock when
when invoking this callback. This leads to deadlock situation
and driver will hang forever.

Change: Make sure all ethtool ops callbacks don't hold rtnl_lock.

Impact: ESX only.

2. Problem: (BDKL87) PSOD in bnx2 start_xmit() path when stressing with
change ring size script on ESX 4.1u2.

Cause: When using ESX4.0/4.1u0-u2, the vmkernel doesn't not check
tx queue state properly in certain race condition. This can
lead to bnx2 start_xmit() to deference NULL tx buffer.

Change: check tx queue state before proceed with stat_xmit().

Impact: ESX4.0/4.1u0-u2.

cnic 2.5.7h (Dec 08, 2011)
==========================
Enhancements
------------
1. Change: Added iSCSI and FCoE driver status and counters support.

Impact: Systems with Management support of these features.

2. Change: Added upstream patches to sync up with upsteam driver:
net: treewide use of RCU_INIT_POINTER
net: remove ipv6_addr_copy()

Impact: None.

bnx2 2.2.1b (Dec 08, 2011)
==========================
Enhancements
------------
1. Change: Added several upstream patches to sync up with upsteam
driver:
net: treewide use of RCU_INIT_POINTER
bnx2: fix skb truesize underestimation
net: Remove unnecessary driver assignments of ethtool_ringparam fields to zero

Impact: None.

bnx2 2.1.12b (Oct 14, 2011)
===========================
Fixes
-----
1. Problem: (CQ59255) iSCSI warning messages appear and performance
drops when connected to a lefthand target.

Cause: Packets with invalid TTT generate warnings and exception
handling.

Change: Updated to 6.2.3 firmware for 5706 and 6.2.1.b for 5709

Impact: iSCSI

cnic 2.5.7g (Sep 23, 2011)
==========================
Enhancements
------------
1. Change: Added cnic_register_driver()/cnic_unregister_driver stubs
so that depmod will not return errors if native bnx2i/bnx2fc
drivers have not been updated.

Impact: None.

bnx2 2.1.11e (Sept 19, 2011)
===========================
Enhancements
------------
1. Change: Set the feature, NETIF_F_NO_SCHED, for ESX 5.0 and
greater releases only

Impact: ESX only

Fixes
-----
1. Problem: Compile errors on some older kernels.

Cause: Compatibility API pci_is_pcie() requires bool type which may
not be defined on older kernels.

Change: Moved bool type compatibility definition above pci_is_pcie().

Impact: None.

bnx2 2.1.11d (Aug 30, 2011)
===========================
Enhancements
------------
1. Change: Integrate Code Review Comments from VMware
* Add feature flag to reflect if a device is
compliant with network scheduling.
* Conditionally move bnx2 drivers to high memory
* Remove unused field/code

Impact: ESX only

2. Change: Remove unnecessary read of PCI_CAP_ID_EXP from upstream.

Impact: minor (5709 only).

cnic 2.5.7f (Sep 13, 2011)
=========================
Fixes
-----
1. Problem: Duplicate cp local variable in cnic_shutdown_rings().

Cause: Coding error.

Change: Removed duplicate variable.

Impact: None.

cnic 2.5.7e (Aug 8, 2011)
=========================
Fixes
-----
1. Problem: (CQ57498) System hangs during bnx2x parity error recovery.

Cause: cnic waits for RAMRODs to complete without timeout. During
parity error recovery, all DMAs will stop.

Change: Added timeouts to all RAMRODs.

Impact: iSCSI and FCoE on bnx2x

cnic 2.5.7d (July 28, 2011)
===========================
Enhancements
------------
1. Change: Increased the max number of FCoE sessions to 1024.

Impact: FCoE.

bnx2 v2.1.11c (July 26, 2011)
============================
Enhancements
------------
1. Change: Upstream sync to use ethtool_cmd_speed API.

Impact: None.

2. Change: Added memory barrier to sync transmit descriptor before updating
TX mailbox. We believe that this may fix some very rare panics
reported by VMWare.

Impact: bnx2 packet transmit.

cnic 2.5.7c (July 26, 2011)
===========================
Fixes
-----
1. Problem: FCOE_DESTROY_FUNC ramrod not completing, causing timeout
and OOO cleanup timeout during MTU change.

Cause: FCOE_DESTROY_FUNC was sent before all FCoE CIDs have been
deleted.

Change: Wait for all (2 seconds delayed) FCoE CFC_DELETE ramrods to
be completed before sending FCOE_DESTROY_FUNC.

Impact: FCoE only.


cnic 2.5.7b (July 19, 2011)
===========================
Enhancements
------------
1. Change: Re-instated vlan_id in ->indicate_netevent(). It is needed
by bnx2fc to handle NETDEV_UNREGISTER on VLAN devices.

Impact: bnx2fc.

2. Change: Allocate FCoE CID space only on E2+ devices.

Impact: None.

bnx2 v2.1.11b (July 19, 2011)
============================
Enhancements
------------
1. Change: Added tx_timeout error handling and made it common with
VMWare code.

Impact: bnx2 NETDEV WATCHDOG error handling

2. Change: Fix compile errors on the latest net-next upstream kernel.

Impact: compilation

cnic 2.5.6d (July 13, 2011)
===========================
Enhancements
------------
1. Change: Removed vlan_id from ->indicate_netevent().

Impact: None.

bnx2 v2.1.10d (July 12, 2011) cnic 2.5.6c (July 12, 2011)
=========================================================
Fixes
-----
1. Problem: Not compiling on 3.0.0 kernel.

Cause: Makefile not recognizing the 3.0.x kernel

Change: Modified Makefile and sync'ed with upstream drivers.

Impact: None.

bnx2 v2.1.10c (July 1, 2011)
============================
Fixes
-----
1. Problem: Not compiling on older kernels (such as RHEL5.4) and newer
kernels (such as 2.6.36)

Cause: Problems with compatibility code.

Change: Fixed compatibility code.

Impact: None.

bnx2 v2.1.10b (June 30, 2011)
============================
Enhancements
------------
1. Change: Added more complete MCP dump during error conditions.

Impact: None.

2. Change: Modified driver messages slightly to match upstream format
(by using netdev_printk, netdev_err, etc).

Impact: None.

Fixes
-----
1. Problem: Not reading iSCSI license on 570x devices reliably.

Cause: We were reading from the CP scratch pad before the CP firmware
is loaded.

Change: Read from MCP shmem location instead.

Impact: 1G iSCSI on bnx2 devices.

cnic 2.5.6b (June 30, 2011)
============================
1. Problem: (CQ56522, CQ56259) Unable to connect to iSCSI target, bnx2x
firmware assert during iSCSI connection

Cause: iSCSI L2 ring CID has been changed in bnx2x 1.70.14. uIP is
using a hardcoded value of 0x11.

Change: cnic now passes the CID to uIP.

Impact: iSCSI on bnx2x devices.

2. Problem: (CQ56230) Cannot compile on some 32-bit systems.

Cause: Passing 64-bit NULL pointer as 32-bit 0 dma_addr_t value.

Change: Use 0 instead of NULL for dma_addr_t values.

Impact: None.

cnic 2.5.5b (June 22, 2011)
============================
Enhancements
------------
1. Change: Added WWN info to cnic_eth_dev. This is a temporary solution
until ndo_fcoe_get_wwn() is implemented.

Impact: None.

bnx2 v2.1.9b (June 22, 2011)
============================
Enhancements
------------
1. Change: Added del_timer_sync() in bnx2_remove_one() from upstream
commit 8333a46ad3877485e4d67ef499c6dda36bfd1f9a. See
ChangeLog for details.

Impact: None.

bnx2 v2.1.8c (June 16, 2011)
============================
Enhancements
------------
1. Change: In ESX, bnx2 will setup int mode during .probe time.
However, the dev->name will be finalized only when
pci_announce_device is done. So, we assign irq->name
in bnx2_request_irq instead of in bnx2_setup_int_mode.

Impact: ESX only.

cnic 2.5.4b (June 1, 2011)
============================
Fixes
-----
1. Problem: (CQ55915) iSCSI does not connect on 57800 in 4-port mode.

Cause: cl_qzone_id was wrong on the 3rd and 4th port. uIP also has
some problems determining 4-port mode.

Change: Fixed the QZONE_ID macro.

Impact: bnx2x iSCSI.

bnx2 2.1.8b (June 1, 2011)
============================
Fixes
-----
1. Problem: (CQ55422) NCSI firmware version displayed backwards on PPC.

Cause: Endian bug when reading the data from shared memory.

Change: Fixed byte swapping issue.

Impact: None.

2. Problem: bnx2 does not compile on some PPC distros.

Cause: pci_enable_pcie_error_reporting() not properly defined in some
distros.

Cause: Added #ifdef to prevent compiling
pci_enable_pcie_error_reporting() on PPC since it uses EEH
instead of AER.

Impact: None.

cnic 2.5.3b (May 24, 2011)
============================
Enhancements
------------
1. Change: Updated to FW 7.0.18 HSI.

Impact: iSCSI and FCoE on bnx2x.

bnx2 2.1.7b (May 24, 2011)
============================
Enhancements
------------
1. Change: Added register read write functions for VMWare gdb

Impact: None.

2. Change: Fixed compile issues on VMWare by resolving KWQ symbol
conflicts between netq code and cnic code.

Impact: None.

cnic 2.5.2b (April 21, 2011)
============================
Enhancements
------------
1. Change: Updated 2.4.2b cnic to T7.0.

Impact: iSCSI and FCoE on bnx2x.

cnic 2.4.5b (May 16, 2011)
==========================
Enhancements
------------
1. Change: Check CFC delete error code during completion. If it is set,
do not reuse the CID. This change is only compatible with
bnx2x 1.64.30 or newer.

Impact: iSCSI and FCoE.

cnic 2.4.4b (May 04, 2011)
==========================
Fixes
-----
1. Problem: (CQ54938) iSCSI timeout during async logout.

Cause: TCP reset request may not complete if there is a race with
firmware receiving a remote RST.

Change: Added code to handle TCP reset racing with remote RST and
TCP close racing with remote FIN.

Impact: iSCSI

cnic 2.4.3b (April 28, 2011)
============================
Fixes
-----
1. Problem: cnic may lose interrupts after processing 64 kcq entries.

Cause: The driver handles a maximum of 64 entries before calling
the ulp drivers. If the chip has more entries, the driver
does not handle the rest but acknowledges the latest
status block index.

Change: Changed the logic to keep looping until all kcq entries
are handled.

Impact: iSCSI and FCoE on all devices.

cnic 2.4.2b (April 21, 2011)
============================
Fixes
-----
1. Problem: (CQ54715, CQ54717) XSEMI parity error detected during iSCSI
login on 57712 in NPAR mode.

Cause: Statistic counter ID greater than MAX_STAT_COUNTER_ID_E2 in
client init data for iSCSI L2 ring.

Change: Check client ID against MAX_STAT_COUNTER_ID_EXX before enabling
statistics.

Impact: iSCSI on bnx2x.

cnic 2.4.1d (April 14, 2011)
============================
Enhancements
------------
1. Change: Added silent VLAN 0 removal on iSCSI ring.

Impact: iSCSI on bnx2x.

cnic 2.4.1c (April 11, 2011)
============================
Fixes
-----
1. Problem: (CQ49586) iSCSI reboot test fails after a few iterations.

Cause: TCP port 60000 is used every time during boot. During reset,
the TCP connection is never terminated so using the same port
to connect to the target during reboot will not work.

Change: Added randomization of the first TCP port to use.

Impact: iSCSI.

bnx2 v2.1.6b (April 6, 2011)
============================
Enhancements
------------
1. Change: Get iSCSI license information to prevent cnic from registering
if there is no license. This will make it consistent with 10G
behavior.

Impact: iSCSI only.

cnic 2.4.1b (April 6, 2011)
===========================
Fixes
-----
1. Problem: (CQ53236) FCoE HBA not functional after reloading bnx2x.

Cause: In some distros, NETDEV_UP can happen immediately after
NETDEV_REGISTER while bnx2x module is still in init state.
At this time, cnic will not be able to symbol_get() from
bnx2x, preventing the cnic from registering.

Change: Check all events, and we should be able to catch NETDEV_CHANGE
abd register cnic.

Impact: iSCSI and FCoE.

Enhancements
------------
1. Change: Updated 10G HSI to firmware 6.4.32 (bnx2x 1.64.23)

Impact: iSCSI and FCoE.

cnic 2.4.0b (Mar 29, 2011)
==========================
Enhancements
------------
1. Change: Updated cnic to with with bnx2x 1.70.x and added support
for 578xx devices.

Impact: iSCSI and FCoE.

bnx2 v2.1.5d (Feb 28, 2011) cnic 2.3.5d (Feb 28, 2011)
======================================================
Fixes
-----
1. Problem: (CQ53174) iSCSI detected conn error and ping timeout.

Cause: Race condition between cnic driver and hardware DMA'ing a
new status block with new iSCSI events. The bug was
introduced when adding FCoE support.

Change: 1. Add proper memory barrier after reading status block.
2. After servicing FCoE EQ, we must loop back and check the
iSCSI EQ again because we may have a newer status block
index that is read after servicing the iSCSI EQ.

Impact: 57712 iSCSI and FCoE.

bnx2 v2.1.5c (Feb 15, 2011) cnic 2.3.5c (Feb 15, 2011)
======================================================
Enhancements
------------
1. Change: Updated 5709 firmware to 6.2.1a, with netq fixes and iSCSI
performance regression fixes.

Impact: 5709.

bnx2 v2.1.5b (Feb 08, 2011) cnic 2.3.5b (Feb 08, 2011)
======================================================
Fixes
-----
1. Problem: iSCSI does not connect in DCB environment.

Cause: iSCSI packets are tagged with the wrong ethertype.

Change: Added initialization of xstorm's reserved_vlan_type field.

Impact: bnx2x iSCSI.

bnx2 v2.1.4h (Jan 27, 2011) cnic 2.3.4h (Jan 27, 2011)
======================================================

Enhancements
------------
1. Change: Ported T6.4 HSI changes to support iSCSI.

Impact: bnx2x iSCSI.

2. Change: Fixed endian bug in setting up page table addresses.

Impact: iSCSI.

bnx2 v2.1.4g (Jan 20, 2011) cnic 2.3.4g (Jan 20, 2011)
=========================================================

Enhancements
------------
1. Change: Removed shared mem logic to read iSCSI and FCoE info.
This logic is now in the bnx2x driver.

Impact: iSCSI and FCoE on bnx2x.

2. Change: Removed FCoE support on 57711. This is no longer supported
by the HSI.

Impact: None.

bnx2 v2.1.4b (Jan 05, 2011) cnic 2.3.4b (Jan 05, 2011)
=========================================================

Enhancements
------------
1. Change: Merged with bnx2 2.0.22b.

bnx2 v2.1.3b (Dec 22, 2010) cnic 2.3.3b (Dec 22, 2010)
=========================================================

Enhancements
------------
1. Change: Merged with bnx2 2.0.21b.

bnx2 v2.1.2f (Dec 13, 2010) cnic 2.3.2f (Dec 13, 2010)
=========================================================
Enhancements
------------
1. Change: Added NPAR FCoE offload checking.

Impact: FCoE.

bnx2 v2.1.2c (Oct 28, 2010) cnic 2.3.2c (Oct 28, 2010)
=========================================================
Enhancements
------------
1. Change: Updated cnic to the latest 6.4.9 HSI.

Impact: bnx2x iSCSI and FCoE.

bnx2 v2.1.2b (Oct 12, 2010) cnic 2.3.2b (Oct 12, 2010)
=========================================================
Enhancements
------------
1. Change: Updated cnic to the latest 6.4.7 HSI.

Impact: bnx2x iSCSI - requires bnx2x 1.64.03 or above.

bnx2 v2.1.1b (Sep 28, 2010) cnic 2.3.1b (Sep 28, 2010)
=========================================================
Enhancements
------------
1. Change: Updated cnic to the latest 6.4.x HSI.

Impact: bnx2x iSCSI - requires bnx2x 1.64.02 or above.

bnx2 v2.0.23b (Feb 01, 2011) cnic v2.2.13b (Feb 01, 2011)
=========================================================
Fixes
-----
1. Problem: EEH errors on PPC when loading bnx2i

Cause: KWQ page tables set up in wrong endian order, causing EEH
errors when sending the first KWQ message.

Change: Fixes page tables endian order.

Impact: PPC only.

bnx2 v2.0.22f (Jan 18, 2011) cnic v2.2.12f (Jan 18, 2011)
=========================================================
Enhancements
------------
1. Prevent AER error messages on PPC. PPC does not support AER.

Impact: 5709 only.

2. Integrated with bnx2x 1.62.10.

Impact: bnx2x iSCSI only.

bnx2 v2.0.22e (Jan 12, 2011)
=========================================================
Fixes
-----
1. Problem: change MTU would fail for the CNIC IRQ.

Cause: Mismatched module IDs for request/free IRQ.

Change: Masquerade as CNIC when cnic ops are called from bnx2.

Impact: ESX only.

bnx2 v2.0.22d (Jan 11, 2011) cnic v2.2.12d (Jan 11, 2011)
=========================================================
Fixes
-----
1. Problem: NetQueue would not properly allocate RX queue

Cause: BNX2_NETQ_HW_OPENED bit was not properly set.

Change: When the NetQueue device is openned properly set the
BNX2_NETQ_HW_OPENED bit in the netq_flags field.

Impact: ESX NetQueue

2. Problem: NetQueue could possibly get out of sync with the uppper
layers

Cause: The queue cleanup code between the driver and upper layer
is not synchronized

Change: Introduce the NetQueue lock to synchronize the cleaning
of the queues between the vmkernel and the bnx2 driver.

Impact: ESX NetQueue

3. Problem: iSCSI may not work if multi-function is disabled in NPAR NICs.

Cause: Bug in logic in detecting NPAR mode.

Change: Offload bit should not be checked if iSCSI MAC address is invalid.

Impact: iSCSI on 57712 NPAR NIC.

bnx2 v2.0.22c (Jan 6, 2011) cnic 2.2.12c (Jan 6, 2011)
=========================================================
Enhancements
------------
1. Change: Updated to 6.2.1a firmware for 5709. It has fixes for
CQ51953 (ESX netqueue issue) and CQ51894 (iSCSI performance).

Impact: 5709 iSCSI and L2.

bnx2 v2.0.22b (Jan 4, 2011) cnic 2.2.12b (Jan 4, 2011)
=========================================================
Enhancements
------------
1. Change: Send netlink IF_DOWN message during cnic_unregister_device().
This fixes the problem of bnx2i referencing freed hba when we
used to send the netlink message during cnic_unregister_driver().

Impact: iSCSI.

2. Change: Upstream fix for memory leak in cnic_alloc_uio_rings() when
we cannot allocate all the memory.

Impact: None.

3. Change: Upstream fix to remove flush_scheduled_work() since it is
obsolete.

Impact: None.

4. Change: Do not allow iSCSI on bnx2x devices in MF mode. The
hardware does not yet support it.

Impact: iSCSI.

Fixes
-----
1. Problem: SPQ RAMROD type field does not consistently contain the
function ID.

Change: Fixed in cnic_submit_kwqe_16() for HSI 6.0 and above.

Impact: iSCSI in NPAR mode.

bnx2 v2.0.21b (Dec 21, 2010) cnic 2.2.11b (Dec 21, 2010)
=========================================================
Enhancements
------------
1. Change: Call cm_connect_complete() when an invalid path_response
netlink message is received. This will speed up iscsid in
disconnecting the connection. This helps to resolve
CQ49665.

Impact: iSCSI.

bnx2 v2.0.20g (Dec 17, 2010) cnic 2.2.10g (Dec 17, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ51766) cnic driver panics in cnic_service_bnx2() during
iscsid restart.

Cause: Referencing the cp->kcq1 pointer before checking that the device
is up.

Change: Fixed logic so that the cp->kcq1 pointer will only be
refernced after checking the device is up.

Impact: iSCSI.

Enhancements
------------
1. Change: Added retry logic in iscsi_nl_send_msg() to retry netlink
messages to userspace.

Impact: iSCSI.

bnx2 v2.0.20f (Dec 09, 2010) cnic 2.2.10f (Dec 09, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ51544) Unable to connect to iSCSI targets on 57712 NPAR
LOMs with NPAR disabled.

Cause: ff:ff:ff:ff:ff:ff iSCSI MAC address was used in this case.

Change: Add code to detect invalid MAC address and use port MAC address
instead. That's the only to determine NPAR is disabled.

Impact: 57712 iSCSI.

2. Problem: MTU change in INTA mode crashes occasionally.

Cause: Status block may be accessed if INTA is shared with another
device during reset. There is a short period that the status
block is freed.

Change: Free IRQ before freeing status block.

Impact: bnx2 MTU change/ring size change.

3. Problem: Heap corruption reported by VMWare.

Cause: list_del() is called after kfree() in OOO code.

Fix: call list_del() before kfree().

Impact: iSCSI OOO.

bnx2 v2.0.20e (Dec 06, 2010) cnic 2.2.10e (Dec 06, 2010)
=========================================================
Enhancements
------------
1. Change: Adjusted hc timeout for EQ to use the T6.0 value of 4. This
will match T5.x HC timeout values.

Impact: 10G iSCSI only.

2. Change: Minor changes to match upstream code.

Impact: None.

bnx2 v2.0.20d (Nov 16, 2010) cnic 2.2.10d (Nov 16, 2010)
=========================================================
Fixes
-----
1. Problem: VMware NetQueue not working properly on 5709.

Cause: HSI mismatch.

Change: Updated HSI to match T6.0 bnx2 firmware.

Impact: NetQueue on 5709.

Enhancements
------------
1. Change: Adjusted kernel compatibility code to compile on RHEL5.6.

Impact: bnx2 and cnic.

bnx2 v2.0.20c (Oct 28, 2010) cnic 2.2.10c (Oct 28, 2010)
=========================================================
Fixes
-----
1. Problem: NMI occurs during repeated load/unload of bnx2 driver on
5709.

Cause: The 5709 chip's DMA block wasn't stopped properly before reset.

Change: Fixed by clearing DMA_ENABLE in NEW_CORE_CTL register and
polling for pending bus transactions to stop.

Impact: 5709.

Enhancements
------------
1. Change: Update 5706/5708/5709 firmware to 6.2.1.

Impact: All 1G devices.

2. Change: Fixed one circular lock dependency issue with bnx2i when making
up call to send iSCSI NL message.

Impact: None.

bnx2 v2.0.20b (Oct 13, 2010) cnic 2.2.10b (Oct 13, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49481) pci_enable_pcie_error_reporting failed on
5706 and 5709.

Cause: AER not supported on non-PCIE devices.

Change: Enable AER only on PCIE devices (5709).

Impact: None.

Enhancements
------------
1. Change: (CQ49858) Support KVM pass-through mode by eliminating
config cycles to non-standard PCI registers
(PCICFG_MISC_CONFIG, PCICFG_REG_WINDOW*).

Impact: All chips.

bnx2 v2.0.18c (Sep 13, 2010) cnic 2.2.6c (Sep 13, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49832) bnx2 flow control not working

Cause: Mistakenly disabled in firmware in 2.0.17j to fix CQ46393.

Change: Re-enabled RV2P flow control with additional fixes to
for a number of odd flow control issues. New firmware
versions are 6.0.15 for 5706/5708 and 6.0.17 for 5709.

Impact: 5706/5708/5709.

Enhancements
------------
1. Change: Added zeroing of the iSCSI L2 ring's RX BD page to help
signal ring shutdown to uIP.

Impact: iSCSI.

2. Change: Fix compile issues on 2.6.36 kernel.

Impact: None.

bnx2 v2.0.18b (Sep 02, 2010) cnic 2.2.6b (Sep 02, 2010)
=========================================================
Enhancements
------------
1. Change: Slightly improve the cnic Netlink fix in cnic 2.2.5k.

Impact: iSCSI.

bnx2 v2.0.17l (Aug 19, 2010) cnic 2.2.5l (Aug 19, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49502) - bnx2x_panic_dump doing DHCP and Data/Header Digest

Cause: A mismatch was found in the txbd where the hw prod idx did not
match the sw prod idx (via the vlan_id field). The problem will
show when uIP restarts without cnic reload. Since uIP restarted,
it has lost all previous history about the uio ring.

Change: Added cnic_shutdown_rings to the uio_close path so whenever
uio_open is called from uIP, the rings will start off fresh.

Impact: 570X/5771X iSCSI.

2. Problem: (CQ49211) Connection via bnx2i path fails in SuSE 11 SP1

Cause: For 5708/09, the previous firmware set did not take the l2 frame
header length into account in the placement filter.

Change: Updated to 5706/08 fw 6.0.14 and 5709 fw 6.0.16 which addresses
this issue.

Impact: 570X iSCSI.


bnx2 v2.0.17k (Aug 18, 2010) cnic 2.2.5k (Aug 18, 2010)
=========================================================
Fixes
-----
1. Problem: iSCSI sessions do not recover when running under
heavy stress conditions with the socket layer.

Cause: The NetLink buffer would get congested, so that the response
to the PATH_UPDATE back to uIP would not be delivered.

Change: Use CNIC to throttle the number of outstanding PATH_REQ's
to uIP, easing the congestion on the Netlink buffer.

Impact: 570X/5771X iSCSI.

bnx2 v2.0.17j (Aug 15, 2010) cnic 2.2.5j (Aug 15, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49395) Session recovery occurs during heavy traffic.

Cause: The mapping of the 10g hw context id to l5 cid didn't consider
the port/vfid.

Change: Fixed the 10g hw context id to l5 cid mapping in TCP OOO

Impact: 5771X iSCSI.

2. Problem: (CQ49111) System freezes when unloading bnx2x drivers while
having active sessions.

Cause: The iro_arr was not initialized before deferencing which led to
a kernel panic. This is caused by a race condition between uIP
and cnic.

Change: Moved the initialization of the iro_arr to before uIP can call
uio open.

Impact: 5771X iSCSI.

3. Problem: (CQ49211) 5708/09 Connection via bnx2i path fails SuSE 11 sp1

Cause: For 5709, the fast coalescing algorithm had a bug in the fw.

Change: Updated 5709 MIPS firmware to 6.0.14 which contains a fix for
this issue.

Impact: 5709 iSCSI.

4. Problem: (CQ46393) 5706/08/09 NC-SI Traffic Stops After Host Kernel Panic

Cause: RV2P firmware was set to drop input packets at a rate which is
slower than input line rate when the host stops posting buffers.
This has caused the rxp ftq to backup which eventually led to the
rxp ftq hw to assert PAUSE and flood the network.

Change: RV2P firmware was modified to disable any waiting before dropping
the input packet when the host doesn't post buffers.

Impact: 5706/08/09.


bnx2 v2.0.17i (Aug 09, 2010) cnic 2.2.5i (Aug 09, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49159) 57710 firmware asserts running disktest.

Cause: CSTORM memory corruption.

Change: Do not initialize and use the FCoE EQ on 57710. The memory
offsets for the FCoE EQ ring are not defined on 57710.

Impact: 57710 iSCSI.

2. Problem: (CQ49271) Soft lockup during ifup/ifdown test with active iSCSI
connections.

Cause: rtnl_lock may have a circular dependency with another filesystem
mutex during uio_close().

Change: Removed rtnl_lock() in cnic_uio_close().

Impact: All iSCSI.

bnx2 v2.0.17h (Aug 03, 2010) cnic 2.2.5h (Aug 02, 2010)
=========================================================
Enhancements
------------
1. Change: Enabled new RV2P flow control on all bnx2 devices.

Impact: All bnx2 devices.

2. Change: Suppressed "OOO CQE is empty" kernel message.

Impact: None.

bnx2 v2.0.17g (Aug 02, 2010) cnic 2.2.5g (Aug 02, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49152) cnic driver crashes during iscsid restart.

Cause: cnic_wq destroyed while cnic_delete_task() is still queued
in the workqueue.

Change: Call destroy_workqueue() after cnic_release() which waits
for the cnic_delete_task() to finish.

Impact: 10G iSCSI.

bnx2 v2.0.17f (July 30, 2010) cnic 2.2.5f (July 30, 2010)
=========================================================
Fixes
-----
1. Problem: iSCSI license not read correctly on 57712 in NIC partitioning
mode.

Cause: Missing NIC partitioning license logic.

Change: Added NIC partitioning license logic.

Impact: 10G iSCSI.

Enhancements
------------
1. Change: Updated 5709 firmware to 6.0.13. The new 5709 firmware
has additional rx and tx performance improvements.

Impact: 5709.

bnx2 v2.0.17e (July 29, 2010) cnic 2.2.5e (July 29, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49117, CQ49111) Soft locup when unloading bnx2x with cnic
and bnx2fc/bnx2i loaded.

Cause: cnic_cm_stop_bnx2x_hw() thread under rtnl_lock() and pci_bus_sem
has to wait for cnic_delete_task() to finish the 2-second wait
and CFC DELETE of every FCoE or iSCSI connection. There may
be work structs scheduled on the common workqueue ahead of
cnic_delete_task() that require the same semaphores, leading
to the soft lockup.

Change: Use a dedicated workqueue for cnic_delete_task().

Impact: 10G iSCSI and FCoE.

2. Problem: (CQ49113) Compilation error with bnx2x 1.60.30.
(CQ48828) lediag fails with cnic loaded.

Cause: license_key structure changed to use all 32-bit fields. This
change is to fix CQ48828 (lediag fails with cnic loaded).
16-bit access causes lediag failure.

Change: Made corresponding change to read 32-bit values for the
iSCSI license.

Impact: 10G iSCSI.

3. Problem: (CQ49097) cnic panics when loading on 5708.

Cause: The driver uses NULL OOO ring pointers to initialize OOO
for 5708.

Change: Skip OOO completely on 5708.

Impact: bnx2 iSCSI.

bnx2 v2.0.17d (July 28, 2010) cnic 2.2.5d (July 28, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49071) Soft lockup during system shutdown after logging
in to 10G iSCSI sessions.

Cause: This was introduced in 2.2.5c when fixing CQ49003.
flush_scheduled_work() can deadlock because we're
holding rtnl_lock and linkwatch_event may be on the
workqueue.

Change: Fixed by using flags to wait for the cnic_delete_task()
to finish.

Impact: 10G iSCSI.

2. Problem: cnic driver does not load on 5708 devices.

Cause: Bug in driver that skips devices without OOO support.

Change: OOO setup has been changed so that cnic initialization will
continue even if OOO fails for whatever reason on all chips.

Impact: iSCSI.

Enhancements
------------
1. Change: Updated 5708 firmware to 6.0.11 and 5709 firmware to
6.0.12. The new 5709 firmware fixes small packet rx
performance issue. Some adiitional fixes for iSCSI
and OOO.

Impact: All bnx2 chips.

bnx2 v2.0.17c (July 23, 2010) cnic 2.2.5c (July 23, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ49003) Panic in cnic_free_bnx2x_conn_resc() during
ifdown with many 10G iSCSI active sessions.

Cause: cancel_work_sync() is not available in RHEL5.x kernels to
wait for cnic_delete_task() to finish before freeing
the device's data structures (in particular the csk table).

Change: Use flush_scheduled_work() to wait instead.

Impact: 10G iSCSI on older kernels (e.g. RHEL5.x)

Enhancements
------------
1. Change: Added AER (Advanced Error Reporting) on bnx2.

Impact: None.

bnx2 v2.0.17b (July 20, 2010) cnic 2.2.5b (July 20, 2010)
=========================================================
Fixes
-----
1. Problem: Still seeing uio_release panics during ifup/ifdown test.

Cause: UIO device unregistered prematurely.

Change: Do not unregister UIO devices until rmmod.

Impact: iSCSI.

Enhancements
------------
1. Change: Various upstream patches. Please see ChangeLog for details.

bnx2 v2.0.16d (July 14, 2010) cnic 2.2.4d (July 14, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ44916) Unload bnx2/bnx2x fails after connecting to
iSCSI targets.

Cause: UIO device deleted before userspace has closed the device,
causing various failures including kernel panic.

Change: Separated UIO structure from cnic_dev structure so that
we can wait until UIO is closed before unregister and deleting
UIO.

Impact: iSCSI. This change should have possitive impact on ifup/ifdown,
MTU change/selftest/hotplug/etc with active iSCSI sessions.

Enhancements
------------
1. Change: Allocate the actual number of MSI-X vectors instead of always
9. Also, keep trying if the number of vectors is less than
the desired number.

Impact: 5709 networking and iSCSI.

bnx2 v2.0.16c (July 12, 2010) cnic 2.2.4c (July 12, 2010)
=========================================================
Enhancements
------------
1. Change: Added VLAN_TAG_PRESENT to distinguish between physical and
VLAN netevents in cnic.

Impact: FCoE.

bnx2 v2.0.16b (July 8, 2010) cnic 2.2.4b (July 8, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ48753) cnic will not compile with bnx2x 1.60.27.

Cause: IGU symbols not defined without ELINK_DEBUG defined.

Change: Added ELINK_DEBUG.

Impact: None.

2. Problem: (CQ48717) Kernel panic in bnx2x during ifdown with active iSCSI
sessions.

Cause: uio_close() is called after the device is already down. bnx2x
will crash when we try to shutdown the iSCSI ring.

Change: Shutdown the iSCSI ring even if uio_close() is not called in
the shutdown path.

Impact: 10G iSCSI.

Enhancements
------------
1. Change: Always run in MSI-X mode on 5709.

Impact: 5709.

2. Change: Added wait of 2 seconds when sending PATH_REQ if UIO has not
been opened yet. This improves the liklihood of login success
during the first login if using older iscsid.

Impact: iSCSI.

bnx2 v2.0.15k (July 1, 2010) cnic 2.2.3k (July 1, 2010)
=========================================================
Fixes
-----
1. Problem: Compile problems on various older kernels.

Cause: pci_save_state()/pci_restore_state incompatibility in older
kernel. DECLARE_PCI_UNMAP_ADDR() caused dma mapping
field to be undefined on kernels not using IOMMU.

Change: Do not use pci_save_state()/pci_restore_state() on older
kernels. Use dma_addr_t to declare mapping fields.

Impact: None.

bnx2 v2.0.15j (June 30, 2010) cnic 2.2.3j (June 30, 2010)
=========================================================
Fixes
-----
1. Problem: bnx2x firmware asserts if cnic is loaded on 57711E (MF)
functions 2 and higher and the device is brought up.

Cause: Statistics for iSCSI ring not implemented, casuing firmware to
assert when the iSCSI ring is initialized.

Change: Do not enable statistics if the clien ID is bigger than
MAX_STAT_COUNTER_ID.

Impact: bnx2x iSCSI on 57711E.

2. Problem: cnic terminations for iSCSI and FCoE connections may panic or
hang during repeated ifdown/ifup.

Cause: Data structures may be freed while cnic is still waiting for the
2 second CFC_DELETE wait time.

Change: Use cancel_work_sync() to wait for the completion of the
cnic_delete_task(). Check that the CTX_FL_DELETE_WAIT flag
has been set before waiting.

Impact: bnx2x iSCSI and FCoE.

3. Problem: (CQ48642) Compile errors on older kernels.

Cause: VMWARE_ESX_DDK_VERSION not defined in Linux.

Change: Added check for VMKLNX.

Impatc: None.

bnx2 v2.0.15i (June 30, 2010) cnic 2.2.3i (June 30, 2010)
=========================================================

Enhancements
------------
1. Change: Added iSCSI out-of-order support.

Impact: iSCSI.

bnx2 v2.0.15h (June 18, 2010) cnic 2.2.3g (June 10, 2010)
=========================================================
Enhancements
------------
1. Change: Enabled HW RSS indirection table on 5709.

Impact: RSS on 5709.

2. Change: Updated to 6.0.10 firmware.

Impact: all chips.

bnx2 v2.0.15g (June 10, 2010) cnic 2.2.3g (June 10, 2010)
=========================================================
Enhancements
------------
1. Change: Added FCoE statistics SPQ command.

Impact: FCoE.

bnx2 v2.0.15f (June 4, 2010) cnic 2.2.3f (June 4, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ46648) CID leaks while running iLAB 5.12 connection closure
test.

Cause: Race condition between bnx2i initiated TCP close and an
asynchronous RESET_COMP from firmware.

Change: Re-structured cnic code that handles close, abort, and various
completion events to ensure all scenarios are accounted for
with no race conditions.

Impact: All iSCSI connection termination scenarios.

Enhancements
------------
1. Change: Added host iSCSI IP address to the cnic_dev structure so that
bnx2i can report it to sysfs. This is needed for iSCSI boot
during pivot_root.

Impact: iSCSI boot.

bnx2 v2.0.15e (June 3, 2010) cnic 2.2.3d (June 2, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ48133) bnx2 fails to compile on older 2.6 kernels.

Cause: PCI MSIX attributes not defined in kernel .h files.

Change: Added compatibility code.

Impact: None.

bnx2 v2.0.15d (June 2, 2010) cnic 2.2.3d (June 2, 2010)
=========================================================
Fixes
-----
1. Problem: (CQ47942) rmmod hangs if the device has been opened and closed
more than once.

Cause: netif_napi_add() called once during every ->open().
netif_napi_del() is only called once during rmmod.

Change: Call netif_napi_del() in ->close().

Impact: None.

bnx2 v2.0.15c (May 21, 2010) cnic 2.2.3c (April 21, 2010)
=========================================================
Fixes
-----
1. Problem: service iscsid restart on 5709 does not work.

Cause: Not restarting KWQ correctly due to stale context.

Change: Fixed by correctly zeroing KWQ/KCQ/RX context
memory.

Impact: bnx2 iSCSI.

2. Problem: iSCSI license not read correctly on 57711E in single
function mode.

Cause: Bug in reading the mf_cfg block.

Change: Bug fixed.

Change: 57711E iSCSI.

Enhancements
------------
1. Change: Added GRO support.

Impact: All devices on kernels supporting GRO.

bnx2 v2.0.15b (May 12, 2010) cnic 2.2.3b (April 12, 2010)
=========================================================
Fixes
-----
1. Problem: iSCSI does not work on 57712.

Cause: License checking always disabled on 57712.

Change: Added proper checking for 57712 iSCSI license.

Impact: None.

2. Problem: (CQ47360) Compile errors on older kernels not supporting
UIO and latest iSCSI.

Cause: New cnic driver will only compile on kernels newer than
2.6.31 and some selected distros that have the backport.

Change: Makefile changes to compile cnic only on supported kernels.

Impact: None.

Enhancements
------------
1. Change: Changed bnx2_cnic_probe() to bnx2_cnic_probe2() so
that out-of-tree driver componenets will not inter-
operate with upstream components. This avoids
compatibility problems that often lead to kernel
crashes.

Impact: Out-of-tree cnic will not operate with upstream
L2 drivers and vice versa.

2. Change: Revert the PRS_REG_NIC_MODE change done in 2.0.11h. Newer
bnx2x driver (1.60.18+) do not require this setting.

Impact: None.

bnx2 v2.0.14b (April 28, 2010) cnic 2.2.2b (April 28, 2010)
============================================================
Enhancements
------------
1. Change: Added compatibility code for RHEL5.4+ kernels.

Impact: None.

2. Change: Added VLAN ID to netdev event callback.

Impact: bnx2i.

bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1c (April 30, 2010)
============================================================
Enhancements
------------
Add debug code to dump all KWQE's (RAMROD) posted to 5771x chipset.
This feature can be enabled/disabled using module parameter, by default
this feature is disabled. Also a exported function is introduced to
dump 3 pages worth of KCQE's

bnx2 v2.0.13b (April 22, 2010) cnic 2.2.1b (April 22, 2010)
============================================================
Enhancements
------------
1. Change: cnic has been updated to be similar to the upstream versions
using UIO with added T6.0 iSCSI support for 10G and other bug
fixes.

Impact: iSCSI now requires UIO, new bnx2i, and bnx2x 1.60.16+.

bnx2 v2.0.11j (April 22, 2010) cnic 1.10.2j (April 22, 2010)
============================================================
Fixes
-----
1. Problem: (CQ47298) Does not compile with bnx2x 1.60.16.

Cause: cnic_if.h has changed.

Change: Updated code to be compatible with new cnic_if.h.

Impact: None.

bnx2 v2.0.11i (April 15, 2010) cnic 1.10.2i (April 15, 2010)
============================================================
Fixes
-----
1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours
of traffic.

Cause: Chip timing out on write cycle to the MSI-X mask bit, causing
the unmask operation to be dropped.

Change: Increase GRC timeout in register 0x8cc.
(Same fix from 2.0.8e).

Impact: bnx2x MSI-X mode.

2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and
VLANs are used with cnic loaded.

Cause: bond_del_vlans_from_slave() holds bond->lock when calling
ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to
stop the rx handling while changing the vlgrp. The call
also calls bnx2_cnic_stop() which has many sleeping functions.

Change: Do not stop cnic when VLANs are changed. Since there is no
reset during VLAN change, there is no need to stop cnic.
(Same fix from 2.0.8e).

Impact: VLAN and iSCSI.

3. Problem: (CQ46940) Poor small packet performance on 5709.

Cause: FTQ discards caused by bottlenecks in firmware.

Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709.
(Same fix from 2.0.8c)

Impact: 5709.

Enhancements
------------
1. Change: Improved rx performance by prefetching next entry's descriptor
header and SKB.

Impact: All chips.

2. Change: Updated cnic interface to support out-of-order processing. This
is needed for bnx2x 1.60.15 but the feature is not available in
cnic yet.

Impact: None.

bnx2 v2.0.11h (Mar 29, 2010) cnic 1.10.2h (Mar 29, 2010)
========================================================
Fixes
-----
1. Problem: iSCSI not functional with bnx2x 1.60.11.

Cause: PRS_REG_NIC_MODE set to 1, causing L2 to receive iSCSI traffic.

Change: Cleared PRS_REG_NIC_MODE.

Impact: bnx2x iSCSI.

bnx2 v2.0.11g (Mar 17, 2010) cnic 1.10.2g (Mar 17, 2010)
========================================================
Enhancements
------------
1. Problem: iSCSI not functional on 57712.

Cause: Bugs and incomplete support of 57712 in cnic driver.

Change: Fixed and completed 57712 support.

Impact: iSCSI.

bnx2 v2.0.11f (Mar 15, 2010) cnic 1.10.2f (Mar 15, 2010)
======================================================
Fixes
-----
1. Change: More 6.0.12 firmware HSI changes (bnx2x 1.60.10).

Impact: bnx2x iSCSI.

bnx2 v2.0.11e (Mar 9, 2010) cnic 1.10.2e (Mar 9, 2010)
======================================================
Enhancements
------------
1. Change: Updated to 6.0.12 firmware HSI (bnx2x 1.60.10).

Impact: bnx2x iSCSI.

bnx2 v2.0.11d (Feb 25, 2010) cnic 1.10.2d (Feb 25, 2010)
========================================================
Enhancements
------------
1. Change: Fixed shared memory base checking for T6.0 bnx2x HSI.

Impact: bnx2x iSCSI.

2. Change: Added new igu status block ID to handle iSCSI status
block acknowledgement in T6.0 HSI.

Impact: bnx2x iSCSI.

3. Change: Allow multiple ethtool speed advertisments when using
newer ethtool 6.

Impact: ethtool -s.

Fixes
-----
1. Problem: Statistics 64-bit counters may not be accurate after MTU
change.

Cause: Bug missing the carry when summing 64-bit counters.

Change: Fixed the missing carry.

Impact: statistics.

bnx2 v2.0.11c (Feb 04, 2010) cnic 1.10.2c (Feb 04, 2010)
========================================================
Enhancements
------------
2. Change: Added 57712 support in cnic driver.

Impact: None.

bnx2 v2.0.11b (Jan 28, 2010) cnic 1.10.2b (Jan 27, 2010)
========================================================
Enhancements
------------
1. Change: Saved bnx2 statistics block before MTU change, ring change,
etc.

Impact: bnx2 statistics.

bnx2 v2.0.10b (Jan 12, 2010) cnic 1.10.1b (Jan 12, 2010)
========================================================
Enhancements
------------
1. Change: Improved cnic's MTU change/reset logic to fix multiple problems
in VMWare.

Impact: iSCSI.

2. Change: Converted to bnx2x T6.0 HSI.

Impact: bnx2x iSCSI.

bnx2 v2.0.8e (April 13, 2010) cnic 1.9.13b (Dec 16, 2009)
=========================================================
Fixes
-----
1. Problem: (RHBZ 511368) Driver loses one MSI-X vector after many hours
of traffic.

Cause: Chip timing out on write cycle to the MSI-X mask bit, causing
the unmask operation to be dropped.

Change: Increase GRC timeout in register 0x8cc.

Impact: bnx2x MSI-X mode.

2. Problem: (RHBZ 554706) scheduling while atomic warning when bonding and
VLANs are used with cnic loaded.

Cause: bond_del_vlans_from_slave() holds bond->lock when calling
ndo_vlan_rx_register(). bnx2 calls bnx2_netif_stop() to
stop the rx handling while changing the vlgrp. The call
also calls bnx2_cnic_stop() which has many sleeping functions.

Change: Do not stop cnic when VLANs are changed. Since there is no
reset during VLAN change, there is no need to stop cnic.

Impact: VLAN and iSCSI.

bnx2 v2.0.8d (April 02, 2010) cnic 1.9.13b (Dec 16, 2009)
=========================================================
Enhancements
------------
1. Change: Improved rx performance by prefetching next entry's descriptor
header and SKB.

Impact: All chips.

bnx2 v2.0.8c (Mar 31, 2010) cnic 1.9.13b (Dec 16, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ46940) Poor small packet performance on 5709.

Cause: FTQ discards caused by bottlenecks in firmware.

Change: Upgraded to 5.0.0.j15 MIPS firmware for 5709.

Impact: 5709.

bnx2 v2.0.8b (Dec 16, 2009) cnic 1.9.13b (Dec 16, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44964) RHEL5.4 crashes when bnx2 driver is updated with
out-of-tree version.

Cause: Newer out-of-tree driver's cnic_eth_dev structure has been
updated, making it incompatible with RHEL5.4's cnic driver.

Change: Reverted the structure update for RHEL5.4.

Impact: None.

Enhancements
------------
1. Change: Improved the reset logic to prevent NETDEV WATCHDOG when
TSS is enabled.

Impact: MTU change, ring size change, selftest, etc.

2. Change: Fixed some compiler warnings when compiling bnx2 and cnic
drivers.

Impact: None.

bnx2 v2.0.7b (Dec 7, 2009) cnic 1.9.12b (Dec 7, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44620) Spurious KCQ entries leading to bnx2x assert.

Cause: Stale status block with old KCQ index after restarting hardware.

Change: Added some additional cleanup and initialization steps including
zeroing the status block.

Impact: None.

Enhancements
------------
1. Change: Updated RV2P P1 for 5709 to 5.0.0.j10 to address a flow control
issue that can lead to context corruption. Flow control
watermarks have also been optimized.

Impact: 5709 flow control.

bnx2 v2.0.6b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44801) Unable to compile bnx2 on most 2.6 kernels.

Cause: print_mac() kernel compatibility not defined correctly.

Fix: Simple compatibility fix.

Impact: None.

bnx2 v2.0.5b (Dec 4, 2009) cnic 1.9.11b (Nov 19, 2009)
=======================================================
Enhancements
------------
1. Change: Sync'ed up with latest upstream bnx2 driver. Please see
ChangeLog for details.

Impact: Yes, Linux and VMWare.

bnx2 v1.9.42b (Dec 1, 2009)
=======================================================
Fixes
-----
1. Problem: Compile error against the VMware ESX 4.0 DDK

Cause: vmk_IscsiNetHandle is not defined with the
VMware ESX 4.0 DDK

Change: Added compile flag

Impact: None.


Enhancements
------------

1. Change: Add BMAPILNX ioctl to allow for FW upgrade

Impact: bnx2 VMware ESX 4.0


bnx2 v1.9.41b (Nov 19, 2009) cnic 1.9.11b (Nov 19, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44617) Compile error on SLES10 and RHEL4 kernels.

Cause: bool not defined on older kernels.

Change: Added compatibility code.

Impact: None.

2. Problem: (CQ42096) iSCSI sessions do not recover after running
selftest/ifdown/etc with max sessions connected.

Cause: cnic_lock mutex has circular dependency, causing deadlock
when iscsid tries to cleanup connections.

Change: Merged in upstream cnic patches to avoid circular
dependency.

Impact: None.

Enhancements
------------
Change: (CQ43088) Changed the firmware version string format.

Impact: None.

bnx2 v1.9.40b (Nov 18, 2009) cnic 1.9.10b (Nov 12, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44528) Kernel runs out of memory after load/unload bnx2.

Cause: RX SKB buffers were not freed.

Change: Fixed the regression introduced by VMWare development.

Impact: None.

2. Problem: (CQ44399) iLAB 5.10 connection establishment test failure.

Cause: Firmware SYN-ACK handling issue.

Change: Updated firmware to 5.0.0.j6 in bnx2_fw.h and 5.0.0.j9 in
bnx2_fw2.h.

Impact: iSCSI.

Enhancements
------------
Change: (CQ43088) Added VPD-R V0 firmware version string to ethtool -i.

Impact: None.

bnx2 v1.9.39b (Nov 6, 2009) cnic 1.9.10b (Nov 12, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ44470) Kernel panics when bnx2/bnx2x is unloaded with
active iSCSI sessions.

Cause: NETDEV_UNREGISTER will cause bcm570x_* transport to be
destroyed while sessions may still be active.

Change: Use module referencing to prevent bnx2/bnx2x from unloading.
This is a simple interim solution to revert back to the
old behavior. In T6.0, we will migrate to the upstream
driver architecture and network drivers will be able to be
unloaded again.

Impact: None.

Enhancements
------------
Change: Added a short register dump during NETDEV_WATCHDOG.

Impact: None.

bnx2 v1.9.38b (Nov 6, 2009) cnic 1.9.9b (Nov 6, 2009)
=====================================================
Fixes
-----
1. Problem: (CQ44446) cnic panics during 10G iSCSI initialization.

Cause: Recent interface changes introduced this regression.
cnic_service_bnx2x() panics when accessing uninitialized
status block pointer.

Change: Added state checking in cnic_service_bnx2x().

Impact: None.

2. Problem: (CQ44439) bnx2 does not compile on older 2.6 kernels.

Cause: mutex not defined on older kernels.

Change: Use rtnl_lock() to protect bnx2_reset_task().

Impact: None.

bnx2 v1.9.37b (Nov 4, 2009) cnic 1.9.8b (Nov 3, 2009)
=====================================================
Enhancements
------------

1. Change: Updated 5708/5706 firmware to 5.0.0.j5 for better small packet
performance.

Impact: 5706/5708.

Fixes
-----
1. Problem: (CQ43280) Cannot unload cnic after bnx2/bnx2x is loaded.

Cause: module referencing.

Change: Changed module referencing scheme.

Impact: None.

bnx2 v1.9.36b (Oct 22, 2009)
=======================================================
Enhancements
------------

1. Change: Expand on NetQueue module parameters.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.35b (Oct 22, 2009)
=======================================================
Fixes
-----
1. Problem: If only 1 queue is used on VMware ESX, iSCSI
offload would fail.

Cause: The inboxed VMware driver would only use
1 MSI-X vector. Because of this the driver
would not setup MSI-X

Change: Always setup MSI-X reguardless of the
number of MSI-X vectors used.

Impact: 5709 iSCSI on VMware

bnx2 v1.9.34b (Oct 20, 2009)
=======================================================
Fixes
-----
1. Change: Updated xinan firmware to 5.0.0.j8
Nop timeout tuning (VMware PR467194)
Added a new data fw heartbeat to work with
the new bootcode and also handle older
bootcode.

Impact: 5709.

bnx2 v1.9.33b (Oct 8, 2009)
=======================================================
Enhancements
------------

1. Change: Make NetQueue module parameters more explict.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.32b (Oct 8, 2009) cnic v1.9.7c (Oct 8, 2009)
=======================================================
Fixes
-----
1. Problem: CNIC unable to handle an unsolicited
RESET COMPLETE which would result in a hung
session.

Cause: The CNIC driver couldn't handle unexpected SYN.

Change: The CNIC driver will now handle an unsolicited
RESET COMPLETE and cleanup properly.

Impact: cnic

Enhancements
------------

1. Change: Allow the default NetQueue options to be
controlled through the macro,
BNX2_ENABLE_NETQUEUE.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.31b (Oct 6, 2009)
=======================================================
Fixes
-----
1. Problem: PSOD would occur when alloc()'ing NetQueue's

Cause: With the removal of the global 'disable_netq'
parameters, the NetQueue CID's weren't being
mapped in some cases

Change: Always map the NetQueue CID's

Impact: bnx2 VMware ESX NetQueue

bnx2 v1.9.30b (Oct 5, 2009)
=======================================================
Fixes
-----
1. Problem: PSOD would occur because of TX timeouts

Cause: The VMware netdev watchdog timer was ran before
the reset task got a chance to run on a loaded
system.

Change: Elongated the TX timeout value for VMware ESX
only to allow for the reset task to run.

Impact: bnx2 VMware ESX


Enhancements
------------

1. Change: Updated vmkernel module parameter, 'force_netq',
to allow NetQueue setting to be adjusted per
function rather then globally for all functions.

Impact: bnx2 VMware ESX


bnx2 v1.9.29b (Oct 1, 2009)
=======================================================
Fixes
-----
1. Change: Updated xinan firmware to 5.0.0.j7 and
teton firmware to 5.0.0.j4 which will fix
L2 hang due to iSCSI PDU's padding byte
extended to another TCP segment

Impact: 5706/5708/5709.


bnx2 v1.9.28b (Sep 25, 2009)
=======================================================
Fixes
-----
1. Change: Updated firmware to 5.0.0.j6 which will add
the corresponding flow control trip point.

Impact: 5709.


bnx2 v1.9.27b (Sep 24, 2009) cnic v1.9.7b (Sep 24, 2009)
=======================================================
Fixes
-----
1. Problem: For the cnic users would see in the kernel logs:

"kcq abs(hw_prod(0) - sw_prod(65534)) >
MAX_KCQ_IDX(2047)"

Cause: The function was not taking into account the
wrapping of the software and hardware producer
indexes.

Change: Recaculate the difference between the index with
wrapping taken into account.

Impact: cnic


Enhancements
------------

1. Change: Updated firmware to 5.0.0.j5 which increased the
rxpq depth from 32 to 256 to enhance the performance
on systems without flow control.

Impact: 5709.


bnx2 v1.9.26c (Sep 17, 2009)
=======================================================
Enhancements
------------
1. Change: Cleanup the VMware NetQueue code. Eliminate unneeded
RX flush routine, fix the number of queues to be the
same on 1500 and 9000 MTU sized packets.

Impact: bnx2 VMware NetQ.

bnx2 v1.9.26b (Sep 14, 2009)
=======================================================
Fixes
-----
1. Problem: VMware PSOD on MTU change

Cause: MSI-X window was remapped to the beginning of the PCI
config space. The driver would disable the bar space
because the MSI-X window was remapped incorrectly. This
would eventually cause a PSOD.

Change: Before the chip reset, the driver would disable MSI-X,
after the chip reset, MSI-X is re-enabled.

Impact: VMware NetQueue


bnx2 v1.9.25b (Aug 21, 2009) cnic v1.9.6 (Aug 21, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ 43182/43252) Compile error on RHEL4

Cause: struct mutex not defined on older kernels.

Change: Wrap cnic_lock mutex structure and code with #ifdef BCM_CNIC.

Impact: None.

2. Problem: Unloading cnic after ifdown may crash.

Cause: cnic unregisters with bnx2/bnx2x twice.

Change: Fixed logic to unregister only once.

Impact: None.

bnx2 v1.9.24b (Aug 13, 2009) cnic v1.9.6 (Aug 13, 2009)
=======================================================
Fixes
-----
1. Problem: (CQ 42778) Kernel occasionally panics when enabling jumbo
frames.

Cause: If the driver is unable to allocate memory for the buffers,
the device is not properly shutdown.

Change: Added logic to shutdown device if unable to allocate buffers
and complete the setup of the device.

Impact: bnx2, changing MTU and ring sizes.

Enhancements
------------
1. Change: Updated firmware to 5.0.0.j3 for better small packet rx
performance. Firmware also fixes header digest error during
I/O.

Impact: All bnx2 devices.

bnx2 v1.9.23b (July 29, 2009) cnic v1.9.5 (July 29, 2009)
==========================================================

Fixes
-----
1. Problem: (CQ 42723) KCQ not resetting to 0 problem

Cause: RCU deadlock during shutdown

Change: Move the bnx2_register_cnic() call out of the
above sequence. Instead, register and
unregister during NETDEV_UP/NETDEV_DOWN events.

Change all slow path RCU read locks to mutex.
In cnic, we also use reference counting to
protect some slow paths.

Impact: bnx2 iSCSI, bnx2x iSCSI


bnx2 v1.9.22b (July 23, 2009) cnic v1.9.4 (July 23, 2009)
==========================================================

Enhancements
------------
1. Change: If a TX timeout occurs, there could be the possiblity that the
chip is hung. By printing chip state into the kernel ring buffer,
it will be easier to determine this.

Impact: bnx2 iSCSI.

2. Change: The bnx2 firmware should always be matched with the proper bnx2
driver. The bnx2 firmware version string are now printed.
It will be easier to identify the running firmware.

Impact: bnx2

3. Change: When a TX timeout occurs and the chip is reset, the ability to
debug the chip further is lost. This is because the chip state
information is lost during the reset. The users have a choice
to prevent the chip reset.

Impact: bnx2

4. Change: Add a check to see if there was a KCQ overflow was
in the bnx2x firmware. Now this check has been moved to the
CNIC so that the driver could control the cleanup/recovery.

Impact: bnx2 iSCSI.


bnx2 v1.9.21b (July 16, 2009)
==========================================================
Enhancements
------------
1. Change: Updated firmware to 5.0.0.j2 to fix remote reset problem

Impact: bnx2 iSCSI.


bnx2 v1.9.20b (July 09, 2009), cnic v1.9.3 (July 09, 2009)
==========================================================
Fixes
-----
1. Problem: (CQ42534) cnic.c does not compile on older kernels.

Cause: Some iscsi_proto constants not defined in

Change: Added the constant definitions if not already defined.

Impact: None.

Enhancements
------------
1. Change: Updated firmware to 5.0.0.j to fix TMF releated iSCSI issues.

Impact: bnx2 iSCSI.

bnx2 v1.9.19b (July 01, 2009), cnic v1.9.2 (July 01, 2009)
==========================================================
Fixes
-----
1. Problem: (CQ42399) 10G iSCSI fails when initiator and target MTUs
don't match.

Cause: cnic driver sets the MSS without knowing the actual MSS
option and timestamp option during TCP connection.

Change: Changed driver to set MSS to 0xffff so that firmware can
calculate MSS on its own.

Impact: bnx2x iSCSI.

2. Problem: 1G iSCSI fails when initiator and target MTUs don't
match and timestamp is enabled.

Cause: Firmware was not adjusting for the 12-byte timestamp option
if MSS was reduced by MSS option.

Change Updated firmware to 5.0.0.i

Impact: bnx2 iSCSI.

3. Problem: (CQ42353) Unable to disable TCP timestamp on 10G iSCSI.

Cause: Timestamp was hardcoded to be enabled for 10G.

Change: Update global timestamp option during each TCP connection.

Impact: bnx2x iSCSI.

4. Problem: (CQ42329) bnx2x MC assert during IPv6 login/logout.

Cause: EQ filled with more than 128 L4 kcqes without MSI-X interrupt
for 2 seconds. The driver can only buffer 128 L4 kcqes.

Change: Increased L4 kcqe buffer to 256 entries as a temporary solution.
Need to understand the delayed interrupt issue.

Impact: None.

bnx2 v1.9.18b (June 25, 2009), cnic v1.9.1 (June 24, 2009)
==========================================================
Enhancements
------------
1. Change: Added FTQDiscard counter to the list of counters being
reported. During small packet test, there may be FTQ
overflow and this counter is very useful.

Impact: None.

2. Change: Updated firmware to 5.0.0.h to improve small packet L2
performance and to enhance iSCSI TMF handling.

Impact: 5706/5708/5709.

bnx2 v1.9.17b (June 24, 2009), cnic v1.9.1 (June 24, 2009)
==========================================
Fixes
-----
1. Problem: Leaking NetQueues if the firmware did not respond in time

Cause: System might be clogged and there is not enough time to
process the KCQ

Change: Updated driver/firmware to allow the calling of the free RX
queue request before a RX alloc request is issued

Impact: 5709

2. Problem: An offloaded iSCSI connection would get stuck

Cause: Issing an offload request might fail, and this was not handled
properly.

Change: Updated driver/firmware to return the proper return code and
handle offload connection failures.

Impact: 5706/5708/5709

3. Problem: tasklet_init() is being called on a task that is scheduled

Cause: When the CNIC calls register_device(), that task might already
be schedled.

Change: tasklet_disable() is insufficient because the tasklet remains
scheduled and stays on the tasklet list, instead tasklet_kill()
is now used.

Impact: 5706/5708/5709



bnx2 v1.9.16b (June 10, 2009), cnic v1.9.0 (June 10, 2009)
==========================================================
Enhancements
------------
1. Change: (CQ38228) Use symbol_get() for ipv6 symbols so that the
cnic driver will load without necessarily loading ipv6
modules.

Impact: iSCSI over IPv6.

2. Change: Updated 5706/08/09 MIPS firmware to 5.0.0.g.

Impact: 5706/08/09.

3. Change: Backported some dma_mapping_error() checking.

Impact: None.

bnx2 v1.9.15b (June 1, 2009), cnic v1.8.6 (June 1, 2009)
========================================================
Enhancements
------------
1. Change: Upstream bnx2 tx path optimizations. Please see ChangeLog.

Impact: bnx2 tx path.

2. Change: In the cnic driver, save the last allocated TCP port during
unregistration so that previously used TCP ports will not
be immediately re-used.

Impact: iSCSI.

3. Change: VMWare TCP port allocation changes.

Impact: VMWare iSCSI.

bnx2 v1.9.14b (May 21, 2009)
==========================================
Fixes
-----
1. Problem: NOPOUT timeouts on 570x iSCSI connections.

Cause: Bugs in TCP timestamp implementation.

Change: Updated MIPS firmware to 5.0.0.f.

Impact: 5706/5708/5709.

bnx2 v1.9.13b (May 18, 2009)
==========================================
Fixes
-----
1. Problem: Potentially exceeding the NetQueue limit recommendations
by VMware which could stress system resources

Cause: When system resources are strained.

Change: There are now limits on the number of NetQueues which the
driver will request:
When the MTU is 1500 the max number of queues per port is 8
When the MTU is 9000 the max number of queues per port is 4

Impact: NetQueue enabled version of VMware ESX

2. Problem: Getting conflicting NetQueue and iSCSI completions

Cause: When MSI-X is not used on a 5709, NetQueue is still enabled

Change: NetQueue is not disabled is MSI-X is not used.

Impact: NetQueue enabled version of VMware ESX


bnx2 v1.9.12b (May 13, 2009)
==========================================
Fixes
-----
1. Problem: Potentially returning a negative number of NetQueues

Cause: When calculating the number of rings, we use the calculation from
the number of msi-x vectors returned, The number of NetQueues
returned could potentially be negitive if only 1 vector was
returned. This is because the driver was subtracting 2
instead of subtracting 1 (for the default queue) from the total
number of rings.

Change: Return the proper number of queues not including the default
queue.

Impact: NetQueue enabled version of VMware ESX

bnx2 v1.9.11b (May 12, 2009), cnic v1.8.5 (May 13, 2009)
========================================================
Fixes
-----
1. Problem: TCP Delay ACK not working on bnx2x iSCSI

Cause: Disabled in cnic driver.

Change: Fixed csk->tcp_flags definitions and enabled the proper storm
bit for delay ACK.

Impact: bnx2x iSCSI.

bnx2 v1.9.11b (May 12, 2009)
==========================================
Fixes
-----
1. Problem: iSCSI timestamp TCP option not working.

Cause: Disabled in firmware.

Change: Updated to 5.0.0e MIPS firmware.

Impact: 5709.

bnx2 v1.9.10b, cnic v1.8.4 (May 11, 2009)
==========================================
Fixes
-----
1. Problem: NetQ and iSCSI do not work in Vmware environment.

Cause: 1. cnic driver is overwriting CP and COM mailbox bit values newly
defined to support multiple kcqs.

2. Firmware is completing some iSCSI kcqes on the NetQ's kcq.

Change: Fixed cnic driver to only set and clear bit 0 of the CP
and COM mailbox.

Firmware has been updated to 5.0.0d. This firmware also
supports TCP timestamp option for iSCSI connections.

Impact: 5706/5708/5709 iSCSI, NetQ.

bnx2 v1.9.9b (May 1, 2009)
==========================================
Fixes
-----
1. Problem: There is link, but can't pass traffic on ESXi

Cause: Bits in the RX context are being trampled during the
renegotiation of the link.

Change: RX context offset 0x6 should only be initialized once
during init and not be updated during run-time. Offset
4 contains the BIDX that's mapped to the mailbox.

Impact: VMware with NetQueue

bnx2 v1.9.8b, cnic v1.8.2 (April 27, 2009)
==========================================
Enhancements
------------
1. Change: Updated cnic driver to support 1.50.x HSI as well as the older
1.48.107 HSI. A compile flag will be used to select one or the
other.

Impact: iSCSI on bnx2x.

2. Change: Spec file and Makefile changes detect the proper module
install directory.

Impact: installation.

bnx2 v1.9.7b, cnic v1.8.1 (April 22, 2009)
==========================================
Fixes
-----
1. Problem: Compile error with redfinition of struct kwqe.

Cause: Both the CNIC and bnx2 defined this structure.

Change: Because the bnx2 definition is L2 specific, it was renamed to
struct l2_kwqe.

Impact: None.

2. Problem: Add context memory DMA alignment for 57710.

Cause: For the 57710 context memory needs to be 16k aligned.
Without this alignment you will see errors when trying to
establish more then 5 iSCSI connections on VMware ESX 4.0 U1.

Change: Properly aligned the context memory by allocating a bigger
chunk of memory and then finding the proper alignment.
This reduces the number of possible connections in half
but now we can properly establish more then 5 connections
on VMware.

Impact: iSCSI.


bnx2 v1.9.6b (April 17, 2009)
=============================
Enhancements
------------
1. Change: Added NetQueue support for VMware.

Impact: 5709.

bnx2 v1.9.5b (April 17, 2009)
=============================
Enhancements
------------
1. Change: Updated to 5.0.0.a firmware with NetQ support and iSCSI max
connection license information. RV2P firmware unchanged:
4.6.16 for 5706, 4.6.15 for 5709.

Impact: All chips.

2. Change: Set USE_INT_PARAM on 5709. This will switch the chip in
use "interrupt mode" coalescing after MSI/MSI-X.

Impact: 5709.

3. Change: Included 5706 when doing statistics block DMA workaround.

Impact: 5706.

bnx2 v1.8.8b (March 12, 2009)
=============================
Enhancements
------------
1. Change: Updated to latest 4.6.17 CP firmware for 5709.

Impact: iSCSI licensing on 5709.

bnx2 v1.8.7b, cnic v1.7.8 (March 10, 2009)
==========================================
Enhancements
------------
1. Change: Reverted 5706/5708 firmware to 4.6.16. Low latency interrupt
mode does not work on 5706/5708.

Impact: None.

2. Change: VMWare changes to expose max. number of iSCSI connections in
the cnic_device structure.

Impact: VMware iSCSI.

Fixes
-----
1. Problem: (CQ39867) Compile error on RHEL5.3 Xen kernel.

Cause: msi related symbols undefined because CONFIG_PCI_MSI is not
enabled on Xen kernels.

Change: Added CONFIG_PCI_MSI around the msi related code.

Impact: None.

2. Problem: (CQ39818) iSCSI targets do not reconnect after running self test.

Cause: Interrupt is disabled by bnx2 before notifying CNIC to clean up
and stop. As a result, bnx2i will not receive interrupts when
closing the connections if sharing INTA/MSI with network.

Change: Disable interrupt after notifying CNIC to stop.

Impact: iSCSI.

bnx2 v1.8.6b, cnic v1.7.7 (March 2, 2009)
=========================================
Enhancements
------------
1. Change: Updated to new 5706 firmware (4.6.17) and 5709 firmware (4.6.16).
New interrupt coalescing mode for improved latency and iSCSI
cache line fix on 5709.

Impact: All bnx2 chips.

2. Change: CNIC iSCSI changes for VMWare.

Impact: VMWare only.

bnx2 v1.8.5b, cnic v1.7.6 (Feb 9, 2009)
=======================================
Fixes
-----
1. Problem: (CQ39380) bnx2x iSCSI license not read correctly.

Cause: Using wrong variable to check the license.

Change: Fixed the logic.

Impact: bnx2x iSCSI.

2. Problem: Driver accesing MMIO registers during VLAN operations when
the device is in D3hot state in older kernels.

Cause: VLAN registration functions do not check for device state.

Change: Added if_running check before MMIO access in VLAN registration
functions.

Impact: VLAN operations on all bnx2 chips.

Enhancements
-----------
1. Problem: Updated 5706/5708 firmware to 4.6.16.

Impact: 5706/5708.

bnx2 v1.8.4b, cnic v1.7.5 (Jan 30, 2009)
========================================
Fixes
-----
1. Problem: (CQ39281) Management firmware stops passing traffic when
bnx2 driver is loaded with jumbo frames enabled.

Cause: Firmware bug.

Change: Updated to 4.6.15 firmware.

Impact: 5706/5708/5709.

2. Problem: iSCSI does not work on 57711 in single function mode.

Cause: Driver only allows iSCSI on 57711 if iSCSI is enabled.

Change: iSCSI config. not required in single function mode.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: (CQ38576) Add 5709 to bnx2.4 man page.

Impact: None.

bnx2 v1.8.3b, cnic v1.7.4 (Jan 23, 2009)
========================================
Fixes
-----
1. Problem: (CQ38610, CQ39000, CQ39015, CQ39071, CQ39133) Various Jumbo
frames related data corruption issues.

Cause: Bug in RV2P firmware causing jumbo frames to be DMA'ed without
the frame header control structure occasionally.

Change: New firmware.

Impact: 5706/5708/5709.

bnx2 v1.8.2c, cnic v1.7.4 (Dec 30, 2008)
========================================
Fixes
-----
1. Problem: (CQ38955) Xen kernel panic when unloading bnx2 with jumbo MTU.

Cause: Bug in bnx2_free_rx_mem(). The jumbo page ring memory was
freed incorrectly using the wrong local variable as array
index.

Change: Fixed bug by using the correct variable as array index.

Impact: Jumbo frames.

2. Problem: (CQ38965) iSCSI connection timeout on bnx2x.

Cause: During CFC Delete RAMROD completion handling, the wrong (older)
iSCSI connection ID can sometimes be retrieved using the
harware CID. The CID in the mapping table was not cleared
after the CID was freed.

Fix: Adding clearing of the CID in the data structure after a CID
is freed.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: (CQ38744) Reduced R2TQ memory usage to match new firmware
interface (firmware 4.8.9). This reduces the amount of
kernel memory substantially for each iSCSI connection on
bnx2x.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.7.3 (Dec 17, 2008)
========================================
Enhancements
------------
1. Change: Added iSCSI configuration check on 57711E devices before
allowing iSCSI connections.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.7.2 (Nov 25, 2008)
========================================
Fixes
-----
1. Problem: bnx2x iSCSI does not work on functions 2 or above.

Cause: This was caused by multiple problems:
a) Status block ID specified by bnx2x was wrong.
b) MSI-X vector assigned to CNIC was wrong.
c) New method to ack. status block using HC register was not
implemented.
d) Status block ID in CSTORM status block is always 0, and
as a result, the status block ID used to ack. the status
block was wrong.

All these problems only affect functions 2 and above.

Change: All problems fixed in bnx2x and cnic.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.7.1 (Nov 15, 2008)
========================================
Enhancements
------------
1. Change: Added CNIC support for Multi function bnx2x iSCSI.

Impact: bnx2x iSCSI.

bnx2 v1.8.2b, cnic v1.6.2 (Nov 12, 2008)
========================================
Enhancements
------------
1. Change: Updated to latest 4.6.13 5709 firmware to fix context corruption
with flow control enabled.

Impact: 5709.

2. Change: Added support for 5716S PCI ID.

Impact: None.

Fixes
-----
1. Problem: (CQ35904) Netdump does not work.

Cause: Problem introduced by MSI-X multiqueue. IRQ handlers were
changed to take bnx2_napi parameter instead of netdev parameter.

Change: Fixed by passing proper parameter to IRQ handler from netpoll.
All IRQ handlers are called when using multiple MSI-X vectors.

Impact: 5709 netpoll.

bnx2 v1.8.1f, cnic v1.6.1 (Nov 5, 2008)
========================================
Fixes
-----
1. Problem: All TSO packets corrupted on 5706/5708.

Cause: Firmware bug zeroing the wrong field in IP header.

Change: Updated to latest 4.6.11 5706/5708 firmware and 4.6.12 5709
Firmware.

Impact: 5706/5708/5709.

2. Problem: bnx2x chip asserts when trying to make iSCSI connection
to an unknown IP address.

Cause: When connection fails, the driver sends a command to an
unitialized CID.

Change: Added logic to only send deletion commands to initialized
CIDs.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: Added support for one single VLAN to a bnx2x iSCSI interface.

Impact: bnx2x iSCSI.

bnx2 v1.8.1e, cnic v1.6.0 (Oct 27, 2008)
========================================
1. Change: Updated to latest 5709 firmware to fix iSCSI data integrity
problem.

Impact: 5709.

bnx2 v1.8.1d, cnic v1.6.0 (Oct 23, 2008)
========================================
Enhancements
------------
1. Change: Updated to latest bnx2 firmware to fix iSCSI data integrity
problem.

Impact: 5706/5708/5709.

2. Change: Updated to the latest bnx2x HSI files.

Impact: bnx2x iSCSI.

bnx2 v1.8.1c, cnic v1.5.9 (Oct 13, 2008)
========================================
Fixes
-----
1. Problem: (CQ37905) Unable to compile on SLES10 SP2.

Cause: DIV_ROUND_UP macro not defined in this kernel.

Change: Added it for compatibility.

Impact: None.

Enhancements
------------
1. Change: Updated to latest 5709 firmware that fixes an NCSI problem.

Impact: 5709.

2. Change: Handle TCP reset in the middle of TCP close more appropriately.

Impact: iSCSI.

3. Change: Handle iSCSI license checking in the same way as 5708/5709.

Impact: iSCSI on bnx2x.

bnx2 v1.8.1b, cnic v1.5.8 (Oct 13, 2008)
========================================
Fixes
-----
1. Problem: bnx2x iSCSI CIDs may be allocated outside the range of allocated
host memory.

Cause: CID range bigger than the amount of allocated host context
memory.

Change: Changed to match the CID range with memory range.

Impact: bnx2x iSCSI.

Enhancements
------------
1. Change: Sync'ed with the latest upstream driver bnx2 1.8.1.

Impact: None.

2. Change: Implemented iSCSI connection license enforcement for bnx2x
devices.

Impact: bnx2x iSCSI.

bnx2 v1.8.0j, cnic v1.5.7 (Oct 6, 2008)
========================================
Fixes
-----
1. Problem: (CQ37610) Chip hangs when changing MTU with active iSCSI
connections.

Cause: Both cnic and bnx2 drivers setting up the chip at the same
time.

Change: Added check so that the register_cnic function will fail
if the bnx2 driver is in reset.

Impact: iSCSI.

2. Problem: (CQ37762) Able to unload bnx2/bnx2x drivers while there are
active iSCSI connections.

Cause: CNIC driver does not have a reference count on the BNX2/BNX2X
drivers.

Change: This became a problem after the register_cnic function was
no longer exported. To solve the problem, the CNIC driver
will now get an explicit reference during register_cnic.

Impact: iSCSI.

3. Problem: (CQ37429) MMIO access while the chip is in D3hot state.

Cause: The driver does not check if_running state consistently during
ethtool operations.

Change: Added proper checks to all ethtool and multicast change
functions.

Impact: ethtool operations and multicast operations.

Enhancements
------------
1. Change: Simplified ipv4 TSO logic in the driver. This was made
possible with newer 5708 firmware.

Impact: 5708 TSO and other traffic.

2. Change: ethtool -p now blinks forever. This is the standard behavior
in most other net drivers.

Impact: ethtool -p.

bnx2 v1.8.0i, cnic v1.5.5 (Sep 30, 2008)
========================================
Fixes
-----
1. Problem: (CQ36787) iSCSI login/logout commands fail on 5709 after a
while.

Cause: Not handling the KWQ completion properly on 5709 in INTA/MSI
mode.

Change: Changed to handle KWQ completions by checking the
cmd_consumer_index instead of the rx_quick_index15.

Impact: 5709 ISCSI in INTA/MSI mode.

2. Problem: (CQ37497) CNIC driver does not compile on powerpc.

Cause: csum_ipv6_magic() not defined.

Change: Added #include

Impact: None.

v1.8.0g (Sep 24, 2008)
========================
Fixes
-----
1. Problem: (CQ37511) System locks up when loading cnic driver on 2.6.16
kernel.

Cause: symbol_put_addr() in 2.6.16 tries to acquire the same lock twice.

Change: Workaround by using __symbol_put() which does not have the same
problem.

Impact: None.

v1.8.0f (Sep 23, 2008)
========================
Fixes
-----
1. Problem: (CQ37405) Kernel panic when performing ifup/ifdown with iSCSI
connections on bnx2x devices.

Cause: Sending searcher delete to bnx2x devices when connection was
not established (due to Spanning Tree or other reasons).

Change: Check PG offload state before sending searcher delete.

Impact: iSCSI on bnx2x.

v1.8.0e (Sep 22, 2008)
========================
Enhancement
-----------
1. Change: Updated to latest driver firmware 4.6.6 for 5709.

Impact: 5709.

2. Change: Updated cnic so that it will not crash even if using older
bnx2/bnx2x drivers without CNIC support. The net driver
can also be loaded after cnic and it will still work without
crashing.

Impact: iSCSI.

3. Change: (CQ 37381) Updated driver to check Vaux PRESET before allowing
WoL. This is needed to support 5709 quad-port boards.

Impact: WoL on all devices.

v1.8.0d (Sep 15, 2008)
========================
Enhancements
------------
1. Change: Updated CNIC iSCSI setup for bnx2x devices.

Impact: iSCSI on bnx2x devices.

v1.8.0c (Aug 25, 2008)
========================
Fixes
-----
1. Problem: Does not compile on older kernels.

Cause: "__maybe_unused" undefined on older kernels. "num_online_cpus()"
undefined on 2.4 kernels.

Change: Added compatibility code to workaround.

Impact: None.

v1.8.0b (Aug 25, 2008)
========================
Enhancement
-----------
1. Change: Updated to latest driver firmware 4.6.2 for 5709.

Impact: 5709.

v1.7.9c (Aug 5, 2008)
========================
Fixes
-----
1. Problem: bnx2 does not compile on older kernels.

Cause: is missing on 2.6.19 and older kernels.

Change: Added compatibility code to check for kernel version before
including the file.

Impact: none.

v1.7.9b (Aug 5, 2008)
========================
Enhancements
------------
1. Change: Added multi-tx ring for 5709. This fetaure is available on
2.6.27 kernel when using MSI-X.

Impact: 5709

2. Change: Added support for 57710 iSCSI in the CNIC driver.

Impact: iSCSI.

v1.7.7c (July 14, 2008)
========================
Fixes
-----
1. Problem: Source RPM fails to build.

Cause: New file missing in tarball.

Change: Added missing file.

Impact: None.

v1.7.7b (July 9, 2008)
========================
Enhancements
------------
1. Change: Added probe function so that the CNIC driver can get the
pci_device pointer earlier before registration.

Impact: iSCSI.

2. Change: Added support for 5716.

Impact: None.

v1.7.6c (June 6, 2008)
========================
Enhancements
------------
1. Change: Added multi-ring RX support on 5709 using MSI-X. This feature
is only available on 2.6.24 and newer kernels running on SMP
machines.

Impact: 5709.

2. Change: Added secondary unicast address support. We now support up
to 5 unicast addresses. This feature is only available on
2.6.23 and newer kernels.

Impact: All chips.

v1.7.6b.1 (Aug 14, 2008)
========================
Fixes
-----
1. Problem: (CQ36808) VLAN tagged packets received by host stack without
the VLAN tag.

Cause: If no VLANs are set up using vconfig, and if the driver
configures the chip to strip the VLAN tag, the problem can
happen. With IPMI or UMP enabled, the driver is likely to
configure the chip to strip the VLAN tag.

Change: Modified the driver to re-insert the VLAN tag when necessary.
I.e. when IPMI/UMP is enabled and vconfig has not setup any
VLANs.

Impact: All chips receiving VLAN traffic.

v1.7.6b (May 29, 2008)
========================
Fixes
-----
1. Problem: IPv4 TSO generates bad packet when the TSO packet size
is 1-MSS.

Cause: Probably firmware does not expect this boundary condition.

Change: Detect this 1-MSS condition in driver and skip the TSO logic.
1-MSS TSO packet will be treated like a regular TX checksum
offload packet.

Impact: TSO on all chips.

2. Problem: Cannot disable VLAN stripping even when management firmware
is disabled.

Cause: The new logic to check firmware VLAN stripping capability
was buggy.

Change: Fixed the code so that VLAN stripping can always be disabled
if management firmware is disabled.

Impact: VLAN/management firmware.

v1.7.5d (May 13, 2008)
========================
Enhancements
------------
1. Change: Incorporated latest firmware 4.4.18. Bug fix is in
RV2P.

Impact: All chips.

v1.7.5c (May 7, 2008)
========================
Enhancements
------------
1. Change: Incorporated latest firmware 4.4.17. Bug fix is in
RV2P.

Impact: All chips.

v1.7.5b (May 5, 2008)
========================
Fixes
-----
1. Problem: (CQ35080) Hard lock when running ethtool -s on the device
that is in the down state.

Cause: I/O to the device to set link speed in D3-hot state can cause
lockup because the chip does not respond to I/O.

Change: ethtool -s will just store the new settings without configuring
the new speed. When the device is later brought up, the new
speed will be set as part of chip init.

Impact: All chips.

2. Problem: (CQ35075 CQ35042) Various compile errors on SuSE SLES 9 and SLES
10 distro kernels.

Cause: ip_hdr() and __le32/__le32 backported to the distro kernels.

Change: Adjusted compatibility defines.

Impact: None.

Enhancements
------------
1. Change: Incorporated latest 5709 firmware 4.4.16. Timer context
scanning is reduced with this firmware to 500us. With this,
the temporary enhancement in 1.7.4c #2 has been removed.

Impact: 5709 iSCSI.

v1.7.4e (April 26, 2008)
========================
Fixes
-----
1. Problem: (CQ34841) 5709 does not link up on some remote PHY systems.

Cause: No initial link interrupt.

Change: Added code to poll for link when remote PHY is present.

Impact: Remote PHY systems.

2. Problem: (CQ34767) Kernel panic on 5709 when using jumbo frames
with NCSI traffic.

Cause: RV2P bug causing RX packets to overwrite kernel memory.

Change: Updated to latest RV2P code for 5709 and 5708.

Impact: 5706/5708/5709.

v1.7.4d (April 17, 2008)
========================
Fixes
-----
1. Problem: IPv6 iSCSI does not work.

Cause: Added code in the last version 1.7.3c to check for CONFIG_IPV6
before enabling the IPv6 CNIC support. This failed to check
for CONFIG_IPV6_MODULE if IPv6 is configured as module in the
kernel configuration.

Change: Changed the checking to CONFIG_IPV6 or CONFIG_IPV6_MODULE.

Impact: None.

v1.7.4c (April 16, 2008)
========================
Fixes
-----
1. Problem: (CQ34814, CQ33984) Driver does not compile on 2.4 kernels.

Cause: __le32 and __be32 not defined in 2.4 kernels.

Change: Defined these as u32 on 2.4 kernels.

Impact: 2.4 kernels.

Enhancements
------------
1. Change: Incorporated latest 5709 4.4.12 firmware to fix various iSCSI
problems.

Impact: 5709.

2. Change: Slowed down the timer block reload time. It was noticed that
after the CNIC driver was unloaded, the timer context memory
was reloaded in a tight loop by the chip. This issue needs
to be properly addressed in the firmware at a future date.

Impact: iSCSI.

v1.7.4b (April 11, 2008)
=======================
Enhancements
------------
1. Change: Incorporated latest 5709 4.4.11 firmware to fix various iSCSI
problems.

Impact: 5709.

v1.7.3k (April 9, 2008)
=======================
Enhancements
------------
1. Change: Incorporated latest 5709 4.4.10 firmware to fix various iSCSI
problems. CID ranges are now read directly from shared memory.

Impact: 5709.

v1.7.3j (April 7, 2008)
=======================
Fixes
-----
1. Problem: (CQ33967) Ethtool register test fails.

Cause: Register 0x1004 context status register should not be tested.

Change: Removed 0x1004 from register test.

Impact: None.

Enhancements
------------
1. Change: Incorporated latest 5709 4.4.9 firmware to fix various iSCSI
problems.

Impact: 5709.

v1.7.3i (April 4, 2008)
=======================
Fixes
-----
1. Problem: (CQ33948) iSCSI over IPv6 does not work on SLES10.

Cause: The CNIC driver does not handle IPv6 on older kernels without
NETEVENTS support.

Change: Modified the logic to support older kernels.

Impact: All iSCSI connections using IPv4 or IPv6.

2. Problem: (CQ34315) Scanning iSCSI disks during max sessions test causes
connection problems.

Cause: 5709 context memeory allocated by CNIC driver does not match
the iSCSI and PG CID range used by the firmware.

Change: Changed to the matching CID range.

Impact: 5709 iSCSI.

v1.7.3h (March 28, 2008)
=======================
Fixes
-----
1. Problem: (CQ33984, CQ34210, CQ34310, CQ34597) Various compiler warnings
and errors on RHEL, SuSE, and 2.4 kernels.

Cause: New features not compatible with older kernels, or older
vendor kernels backported with newer features.

Change: Fine-tuned compatibility compiler directives.

Impact: All kernels.

v1.7.3g (March 10, 2008)
=======================
Enhancements
------------
1. Change: Updated to latest 5709 firmware version 4.4.7.

Impact: 5709.

v1.7.3f (March 10, 2008)
=======================
Fixes
-----
1. Problem: CNIC takes a long time to resolve ARP, causing iSCSI to fail.

Cause: NETEVENT_NEIGH_UPDATE event notifier sometimes takes a long time
to be called.

Change: This is under investigation. For now, the workaround is to
use the existing neighbour entry if it is in NUD_VALID state.
Previously, we would only use it if it was in NUD_CONNECTED
state.

Impact: iSCSI neighbour resolution.

2. Problem: iSCSI sometimes fails to initialize.

Cause: The KWQ is in full condition and prevents any KWQE to be sent
to the firmware. This is caused by the KWQ consumer index in
the status block not initializing to 0.

Change: Added workaround to skip the KWQ full condition check when
sending the first KWQE. This should be properly fixed in
firmware.

Impact: None.

v1.7.3d (February 15, 2008)
============================
Fixes
-----
1. Problem: System hangs with iSCSI traffic.

Cause: Infinite loop in NAPI poll.

Change: Fixed the problem of not comparing the CNIC tag properly when
determining whether there is more work in NAPI poll.

Impact: None.

2. Problem: iSCSI does not work on 5709

Cause: Not initializing 5709 properly for iSCSI. The chip_id field was
not propagated to the CNIC driver.

Change: Fixed the chip_id field.

Impact: None.

v1.7.3c (February 09, 2008)
============================
Enhancements
------------
1. Change: Updated 5708 and 5709 firmware to version 4.4.2.

Impact: All devices.

2. Change: Updated RV2P firmware to the latest. This may fix the jumbo
frame issue.

Impact: All devices, especially jumbo frames on 5709 Bx.

3. Change: Modified CNIC interface in preparation for 57710 devices.

Impact: iSCSI.

v1.7.2f (February 04, 2008)
============================
Fixes
-----
1. Problem: Temporary workaround for one prototype 5709S mezz. card not
working.

Cause: The driver was looking at the wrong shared memory location to
identify the card.

Change: Fixed the code to check the correct BNX2_SHARED_HW_CFG_CONFIG
location.

Impact: 5709S.

v1.7.2e (January 31, 2008)
============================
Fixes
-----
1. Problem: (CQ33704) CNIC driver fails MSI-X mode on 5709.

Cause: When implementing the fix, the wrong constant was used
for the CNIC MSI-X vector.

Change: Corrected to use the correct constant BNX2_CNIC_VEC.

Impact: None.

2. Problem: iSCSI outgoing packets over IPv6 are bigger than 1518 bytes.

Cause: MSS calculation was based on IPv4 and did not accout for the
IPv6 header size.

Change: Adjusted MSS calculation for IPv6.

Impact: None.

v1.7.2c (January 30, 2008)
============================
Fixes
-----
1. Problem: CNIC driver does not work in MSI-X mode on 5709.

Cause: This is a regression caused by moving the CNIC MSI-X
vector from 8 to 2. The context memory did not get
updated with the new vector.

Change: Changed the definition. All bits that depend on the
MSI-X vector will now have the proper definitions automatically.

Impact: None.

v1.7.2b (January 30, 2008)
============================
Enhancements
------------
1. Change: Updated 5709 firmware to 4.4.1.

Impact: 5709.

2. Change: Added temporary workaround for one prototype 5709S mezz. card.
The workaround will be removed once newer cards are available.

Impact: 5709S.

v1.7.1e (January 14, 2008)
============================
Enhancements
------------
1. Change: Updated 5709 firmware to 4.1.1 for IPv6 iSCSI support.

Impact: 5709.

2. Change: Updated 5708 RXP firmware to 4.1.1.

Impact: 5706/5708.

3. Change: Updated RV2P firmware for 5709.

Impact: 5709.

4. Change: Added IPv6 support to CNIC driver.

Impact: New BNX2I driver must be used with this new CNIC driver.

v1.7.1d.3 (February 7, 2008)
============================
Fixes
-----
1. Problem: 5706S continues to not link down occasionally on some blade
systems.

Cause: In some cases, even turning off the tx current does not
cause the link to go down.

Change: Link transition can be triggered based on the SYNC_FAILED bit
in the AN_DEBUG register when all else fails.

Impact: 5706S.

v1.7.1d.1 (February 1, 2008)
============================
Fixes
-----
1. Problem: 5706S still not linking down occasionally on some blade
systems when the switch blade is disconnected.

Cause: Occasionally, all the bits that we check will falsely
indicate link up and trigger the parallel detect logic on
this blade platform. Once in parallel detect mode with
autoneg disabled, the driver will never detect link down.

Change: Disabled parallel detect on this platform by checking
PCI sub IDs to identify the device.

Impact: Parallel detect not supported on this vendor device.

v1.7.1d (January 25, 2008)
============================
Fixes
-----
1. Problem: 5706S still not linking down on some blade systems when the
switch blade is disconnected.

Cause: This is the same problem that was fixed in 1.7.0b. After
switch module is removed, the SYNC_FAILED bit sometimes
toggles low, and this causes the parallel detect logic in the
driver to trigger and disable autoneg. Disabling autoneg
causes false link to come up immediately.

Change: It seems that the RUDI_INVALID bit can be used to prevent the
above from happening. Modified parallel detect code to
additionally check the RUDI_INVALID bit and trigger only when
the bit is cleared.

Impact: Parallel detect logic in 5706S.

v1.7.1c (December 27, 2007)
============================
Fixes
-----
1. Problem: Driver crashes when adding VLAN and bonding.

Cause: Bonding calls driver's VLAN function in interrupt context with lock
held. We recently added a VLAN feature in 1.6.8b which requires
chip reset when VLANs are added or removed. The reset will call
vmalloc/vfree which must not be called in interrupt context.

Change: Reverted the VLAN feature for now. Will workaround it in the
future.

Impact: 5709 only. This new VLAN feature is no longer available.

v1.7.1b (December 24, 2007)
============================
Fixes
-----
1. Problem: Driver crashes when using jumbo frames on 5709 A1.

Cause: RV2P firmware problem.

Change: Disabled jumbo page ring on 5709 Ax chips.

Impact: Jumbo receive page rings not supported on 5709 Ax.

2. Problem: CNIC driver prints "Failed waiting for ref count to go to zero"
when unloading the driver. This is a minor cosmetic issue.

Cause: Minor bug in driver comparing ref_count to 1 instead of zero
during exit.

Change: Fixed the code to check for ref_count == 0.

Impact: None.

v1.7.0b (December 12, 2007)
============================
Fixes
-----
1. Problem: (CQ33032) CPU utilization increases dramatically when TSO
is enabled.

Cause: Driver is spending a lot of unnecessary time in TX handling
code when TSO is enabled. This regression was introduced when
the TX handling code was changed to match the RX handling code.
The RX handling code was changed to fix a packet rot problem.
When TSO is enabled, the tx index can stop at non-packet
boundaries and the code will keep waiting until it gets to the
next packet boundary.

Change: Fixed it to handle this condition properly.

Impact: None.

2. Problem: 5706S does not link down in some blade systems.

Cause: Hardware problem.

Change: Added workaround logic to check periodically and force a
link down when the PHY reports SYNC status failed. This
only works when autoneg is enabled.

Impact: 5706S.

v1.6.8e (December 10, 2007)
============================
Fixes
-----
1. Problem: When using jumbo MTU with large RX ring sizes, system will
crash or the driver won't load.

Cause: Bug in driver where the page descriptor array was declared
too small.

Change: Fixed the array size.

Impact: None.

2. Problem: CNIC driver won't compile on kernels without CONFIG_PCI_MSI.

Cause: Some code needs to be conditionally compiled only when
CONFIG_PCI_MSI is set.

Change: Added #ifdef CONFIG_PCI_MSI where necessary.

Impact: None.

3. Change: Disabled iSCSI on 5709 until next release.

Impact: None.

v1.6.8d (December 07, 2007)
============================
Change: Reverted the 5706S workaround made in 1.6.8c because it was
unreliable.

Impact: None.

v1.6.8c (December 07, 2007)
============================
Fixes
-----
1. Problem: (CQ32794) Kernel panic (skb_over_panic) with jumbo frames.

Cause: RV2P firmware incorrectly placed jumbo data into SKB.

Change: New RV2P firmware.

Impact: Jumbo frames on all hardware.

2. Problem: (CQ32817) ethtool loopback test fails.
3. Problem: (CQ32842) Chariot test fails.

Cause: RX buffer size too small to contain MTU-sized frame.
This was introduced by the new Jumbo RX logic.

Change: Fixed RX buffer size logic.

Impact: Traffic on all hardware.

4. Problem: (CQ32862) Fails to compile on RH9u9.

Cause: Kernel API skb_fill_page_desc() backported to RH kernel
causing duplicate definition.

Change: Adjusted compatibility code.

Impact: None.

5. Problem: (CQ32866) ISCSI driver fails to compile with 1.6.8b.

Cause: print_mac() multiply defined when bnx2.h is included
in the bnx2i driver.

Change: Changed print_mac() to static inline.

Impact: None.

6. Problem: 5706S does not link down in some blade systems.

Cause: Hardware problem.

Change: Added workaround logic to check periodically.

Impact: 5706S.

Enhancements
------------
1. Change: Added flow control logic on 5709.

Impact: 5709.

2. Change: Updated all firmware to 4.0.5.

Impact: All hardware.

v1.6.8b (November 28, 2007)
============================
Enhancements
------------
1. Change: Added MSIX support for 5709 B0.

Impact: 5709 B0.

2. Change: Added multi-page buffer support for Receive Jumbo frames.

Impact: All chips. This feature is experimental at this point.

3. Change: Allow VLAN tags in receive packets when management firmware
is enabled.

Impact: 5709 only. This feature is experimental and requires new
boot code and UMP/IPMI code.

4. Change: Updated firmware to 4.0.3.

Impact: All chips.

v1.6.7b (October 16, 2007)
============================
Fixes
-----
1. Problem: (CQ31861) Remote copper PHY does not link up if WoL is enabled.

Cause: bnx2_set_power_state() assumes that only copper devices support
WoL and proceeds to configure the copper PHY to 10/100 Mbps.
This assumption is no longer valid after Serdes WoL support
was added in 1.6.3c.

Change: Fixed the code to take check for Serdes and copper when setting
up the PHY for WoL.

Impact: WoL.

v1.6.6b (October 10, 2007)
============================
1. Change: Update 5708 firmware to 3.7.19.

v1.6.5k (October 10, 2007)
============================
1. Problem: Will not compile on 2.6.23 kernel.

Cause: get_perm_addr no longer defined in struct ethtool_ops

Change: Adjusted kernel compatibility #ifdef.

Impact: None.

v1.6.5j (October 10, 2007)
============================
No change to bnx2. Updated cnic driver to 1.1.24.

v1.6.5i (October 8, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.18.

v1.6.5h (October 4, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.17.

v1.6.5g (October 1, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.16.

v1.6.5f (September 30, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to newer 3.7.15.

v1.6.5e (September 29, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.15.

v1.6.5d (September 28, 2007)
============================
Enhancements
------------
1. Change: Combined RPM package and tar file with CNIC driver.

v1.6.5c (September 26, 2007)
============================
Enhancements
------------
1. Change: Update 5708 firmware to 3.7.14.

v1.6.5b (September 25, 2007)
============================
Fixes
-----
1. Problem: (CQ30086) 5709 A1 does not link up when connected to
some Broadcom devices.

Cause: Early DAC wakeup workaround needed for 5709 A1.

Change: Added workaround.

Impact: None.

Enhancements
------------
1. Change: Added CNIC support for iSCSI.

Impact: Only enabled on 2.6.16 and newer kernels.

v1.6.3c (July 23, 2007)
=======================
Fixes
-----
1. Problem: (CQ30591) ethtool -t fails on remote PHY systems.

Cause: Link test and loopback test were not modified to support
remote PHY.

Change: Added remote PHY support to link test and changed the code
to skip PHY loopback on remote PHY since it's not supported.

Impact: None.

2. Problem: (CQ30625) ethtool speed settings are lost after ifdown.

Cause: The remote PHY settings stored in firmware is not the same
as the driver's last setting.

Change: Modified the code to keep the driver's setting unless there's
is change in the remote PHY media.

Impact: ethtool -s on remote PHY systems.

Enhancements
------------
1. Change: Change ethtool's wol setting to NVRAM's default and
add support for Serdes WoL if NVRAM supports it.

Impact: ethtool wol's default setting.

v1.6.3b (July 13, 2007)
=======================
1. Problem: Problems reading and writing flash on 5709.

Cause: Hardware changes in 5709.

Change: Rearranged current flash code to properly support 5709.

Impact: Changes will impact flash operations on 5706/5708/5709 devices.

2. Problem: (CQ30516) Management firmware version string disappears
on 2nd modprobe of the driver.

Cause: The 2nd modprobe will program the device back to D0 from D3hot.
This causes a reset and it will take some time before the
management firmware information will be available.

Change: Added a proper wait loop to wait for the firmware information
to be deposited in shared memory.

Impact: None.

v1.6.2f (July 3, 2007)
=======================
1. Problem: The fix for CQ29488 in the previous version is problematic
and needs to be reverted.

Cause: Adding the netif_carrier_off() call before register_netdev()
in bnx2_init_one() can cause problems if register_netdev()
fails. netif_carrier_off() can queue a link watch event
that can run later. If register_netdev() fails, the netdev
structure will be freed and the link watch event may panic
when it is scheduled to run.

Change: Moving the netif_carrier_off() to after register_netdev()
also will not work as it can cause race conditions with
the interrupt handler. So the best thing to do is to
revert the earlier fix and not address the CQ29488 issue.

Impact: CQ29488 is not fixed.

v1.6.2e (July 3, 2007)
=======================
Fixes:
------
1. Problem: (CQ29528) Link does not come up using remote PHY (continued).

Cause: ifup script may be using mii-tool to obtain link status,
and interfering with remote PHY firmware.

Change: Block mii-tool ioctl access when remote PHY firmware is present.

Impact: None.

2. Problem: (CQ29488) Driver reports link up in ethtool before the interface
is brought up.

Cause: The netdevice structure's initial link setting is up and that
gets reported directly by ethtool.

Change: Added netif_carrier_off() call in bnx2_init_one().

Impact: None.

v1.6.2d (June 22, 2007)
=======================
Fixes:
------
1. Problem: (CQ29528) Link does not come up using remote PHY.

Cause: The fix in 1.6.2b still has a problem. The copper or Serdes
default link setting does not follow the correct port when
the port is changed during chip reset.

Change: Fix the code to always refresh the port and link setting
during chip reset.

Impact: None.

2. Problem: (CQ30181) Cannot compile on 2.4 kernels.

Cause: USEC_TO_SEC constant is not defined on older kernels.

Change: Added conditional #define for this constant on older kernels.

Impact: None.

Enhancements:
-------------
1. Change: Update 5709 firmware to 3.7.1.

Impact: 5709 devices.

v1.6.2b (June 21, 2007)
=======================
Enhancements:
-------------
1. Change: Added management firmware version to ethtool -i.

Impact: None.

Fixes:
------
1. Problem: (CQ29528) Link does not come up using remote PHY.

Cause: The driver is using the wrong port when setting up the remote
PHY link.

Change: Fixed bug to always use the correct requested port or
default port when setting remote PHY link.

Impact: None.

2. Problem: (CQ30028) Advertised Autoneg not set in ethtool.

Cause: Remote PHY code is not setting the flag which is for
information only.

Change: Added code the set the flag for consistency.

Impact: None.

v1.6.1c (May 22, 2007)
=====================
Enhancements:
-------------
1. Change: (CQ28907) Added support for setting copper and fibre speeds.

Impact: Only available on Remote PHY systems.

v1.6.1b (May 7, 2007)
=====================
Fixes:
------
1. Problem: (CQ29301) Setting invalid speed setting causes driver to
crash.

Cause: Lock taken without unlock when exiting iwith error the
procedure to set speed.

Change: Fixed the code with proper unlock.

Impact: None.

v1.6.0b (April 30, 2007)
========================
Enhancements:
-------------
1. Change: Improved handshake with remote PHY firmware.

Impact: None.

v1.5.10c (May 4 , 2007)
=======================
Fixes:
------
1. Problem: Extremely low TSO performance when destination has a
smaller MSS than the source.

Cause: Packets smaller than MTU are not processed as TSO packets.

Change: Removed the SKB length check when doing TSO.

Impact: None.

v1.5.10b (May 1, 2007)
=========================
Enhancements:
-------------
1. Change: Removed Remote PHY until next release.

Impact: No Remote PHY support.

2. Change: Added check for 2.5G capability before enabling 2.5G on
5709S.

Impact: None.

Fixes:
------
1. Problem: (CQ28438) NETDEV WATCHDOG after OS boot.

Cause: The mailbox queue is halted after the OS reads config.
register 0x94.

Change: Set MQ_CONFIG_HALT_DIS in register MQ_CONFIG on 5709 A0 and
A1.

Impact: None.

v1.5.9b (April 20, 2007)
=======================
Enhancements:
-------------
1. Change: Enhanced remote PHY support for 5708S.

Impact: None.

Fixes:
------
1. Problem: (CQ29056) Driver does not compile on SLES 10 SP1 kernel.

Cause: Backported netif_tx_lock() causes compatibility problem.

Change: Adjuested compatibility #ifdef.

Impact: None.

2. Problem: (CQ28880) Driver fails register test after running traffic.

Cause: A reserved register 0x500c was mistakenly included in the test.

Change: Removed this register from the test.

Impact: None.

v1.5.8b (March 13, 2007)
=======================
Enhancements:
-------------
1. Change: Added remote PHY support for 5708S.

Impact: None.

v1.5.7b (March 2, 2007)
=======================
Enhancements:
-------------
1. Change: Added IPV6 TSO for 5709.

Impact: None.

2. Change: Added 2.5G parallel detection for 5709s.

Impact: None.

v1.5.6b (February 28, 2007)
===========================
Enhancements:
-------------
1. Change: Added Serdes support for 5709.

Impact: None.

Fixes:
------
1. Problem: (CQ28433) Driver does not compile on some early 2.6 and
2.4 kernels.

Cause: Kernel compatibility issue.

Change: Added some missing #ifdef CONFIG_PCI_MSI.

Impact: None.

2. Problem: (CQ28527) System hangs when running bonding scripts on 5709.

Cause: Bonding driver reads MDIO registers after the device is in
D3hot state.

Change: Added check to disallow MDIO access after the device is down.

Impact: None.

v1.5.5b (January 31, 2007)
===========================
Fixes:
------
1. Problem: (CQ28252) Driver reports the same MAC address for both
ports of 5709.

Cause: The driver was obtaining the MAC address from the same
shared memory area for both ports.

Change: Updated driver to read from the deicated shared memory
area for each port.

Impact: None.

2. Problem: (CQ28226) 5709C does not link up when connected to Dell
5324 and some other switches.

Cause: PHY's Early DAC Wakeup Enable bit's strapped value is set.

Change: Disable Early DAC Wakeup enable on 5709 A0 after PHY reset.

Impact: None.

v1.5.4b (January 8, 2006)
===========================
Fixes:
------
1. Problem: 5709 copper device detected as serdes.

Cause: Media detection code not complete.

Change: Added complete media detection code.

Impact: None.

Enhancement:
------------
1. Change: Add IPv6 checksum support.

Impact: None.

v1.5.2b (December 22, 2006)
===========================
Merged in all latest changes.

v1.5.1c (November 30, 2006)
===========================
Enhancement:
------------
1. Change: Remove 5709 FPGA code.

Impact: None.

v1.5.1b (November 15, 2006)
===========================
Enhancement:
------------
1. Change: Added support for 5709.

Impact: None.

v1.4.52c (March 07, 2007)
=========================
Enhancement:
------------
1. Change: Increase maximum receive ring size to 4080.
The default is kept the same at 255.

Impact: None.

v1.4.51b (December 21, 2006)
============================
Fixes:
------
1. Problem: (CQ27802) Cannot enable flow control in some cases.

Cause: In some cases when flow control is forced to on, the
driver detects no changes in advertisement, and as a
result, will not re-autoneg. Without the link change,
flow control settings will not change.

Change: Added some code to setup flow control when no other
PHY settings are made. This will ensure that flow
control changes will take effect immediately.

Impact: None.

v1.4.50b (December 15, 2006)
============================
Fixes:
------
1. Problem: (CQ27424) Panic when writing to nvram.

Cause: Bug in driver when an alignment buffer is used

Change: Fixed the bug so that the alignment buffer is freed with the
correct pointer.

Impact: None.

v1.4.49b (December 13, 2006)
============================
Fixes:
------
1. Problem: (CQ27459) Driver reports link down when link is up.

Cause: Hotplug scripts can cause bnx2_open() to be called immediately
after bnx2_init_one() calls register_netdev(). The initial
link state set after register_netdev() may overwrite the actual
link state set by the link handler on SMP systems.

Change: Move all initial state setup code to before calling
register_netdev().

Impact : None.

v1.4.48b (December 08, 2006)
============================
Fixes:
------
1. Problem: (RHBZ 212055) Panic in bnx2_poll().

Cause: Bug in determining tx ring space when the tx ring is
completely full.

Change: Fixed the flawed logic in bnx2_tx_avail().

Impact: None.

2. Problem: (CQ27424) Buffer overflow when writing to nvram.

Cause: Bug in driver when the beginning NVRAM offset is
not 4-byte aligned.

Change: Fixed the bug to allocate enough buffer space.

Impact: None.

3. Problem: (CQ27543) Loopback failed if MAC address is changed.

Cause: Driver uses permanent MAC address for loopback which may
be different from a locally administered address.

Change: Fixed by alwaysing using the current MAC address in the
netdevice structure.

Impact: None.

v1.4.47b (November 02, 2006)
===========================
Fixes:
------
1. Problem: (CQ25922) 5708S does not pass PHY loopback test on
some blade servers.

Cause: It takes longer (about 100msec) to link up in some
backplane environments when the Serdes is set to PHY
loopback mode.

Change: Increase delay loop to up to 1 sec when waiting for
link up after PHY loopback. Previous wait time was
100usec.

Impact: None.

v1.4.46b (October 30, 2006)
===========================
Fixes:
------
1. Problem: (CQ25916) Device does not receive packets when configured
by the Xen bridge script and when IPMI is enabled.

Cause: Firmware does not forward packets to the host when the
device is in promiscuous mode in some cases.

Change: Firmware change and driver change to enable the
BNX2_RPM_SORT_USER0_PROM_VLAN bit when going into
promiscuous mode.

Impact: None.

v1.4.45b (October 19, 2006)
===========================
Enhancement:
------------
1. Change: Added software parallel detection on 5708S to link at
1000Mbps or 2500Mbps automatically if the link partner is
forced at 2500Mbps.

Impact: None.

2. Change: Added 2500Mbps forced speed setting. Setting it requires
a future version of ethtool or custom apps.

Impact: None.

3. Change: Port driver to compile on 2.6.19 kernel.

Impact: None.

Fixes:
------
1. Problem: Driver does not complile on 2.4 kernels.

Cause: TSO symbols not defined in 2.4 kernels.

Change: Added #ifdef for compatibility.

Impact: None.

2. Problem: MSI doesn't work on 5706 when the host bridge is AMD8132.

Cause: Compatibility issue.

Change: Added code to disable MSI when 5706 is on a systems with
AMD8132.

Impact: 5706 cannot use MSI on such systems.

v1.4.44b (August 10, 2006)
==========================
Fixes:
------
1. Problem: A rare tx race window exists in the tx path.

Cause: CPU re-ordering can cause the tx queue to be stopped
forever when the tx ring is full in a very rare
condition. See ChangeLog for more details.

Change: Fixed the race condition with memory barriers.
See ChangeLog for more details.

Impact: None.

Enhancement:
------------
1. Change: Increase default rx ring size to 255 to prevent
packet drops under heavy load.

Impact: Higher memory usage.

2. Change: Port driver to run on 2.6.18 kernel.

Impact: None.


v1.4.43b (June 26, 2006)
=======================
Enhancement:
------------
1. Change: (CQ25508) Use DRV_MSG_CODE_UNLOAD_LNK_DN message on
5708 B1 and older chips so that the link will turn
off after ifdown.

Impact: None.

v1.4.42b (June 2, 2006)
=======================
Fixes:
------
1. Problem: (CQ22585) WoL cannot be enabled on 5708 B2.

Cause: Hardware limitation in previous 5708 versions required
driver to always disable driver WoL on 5708.

Change: With the issue fixed in B2, the driver was changed to
allow 5708 B2 and above to support driver WoL.

Impact: None.

2. Problem: (CQ21779) Driver does not report dropped receive packets.

Cause: Packets dropped by firmware are reported in a scratch pad
location in memory separate from other counters.

Change: Added code to report this firmware counter.

Impact: None.

Enhancements:
-------------
1. Change: (CQ24690) Allow driver to be compiled for non-running kernels.

Impact: None.

v1.4.41b (May 17, 2006)
=======================
Fixes:
------
1. Problem: Driver writes wrong data to non-buffered flash.

Cause: Bug in driver causing the unchanged portion of the page
to be corrupted.

Change: Fixed bug.

Impact: None.

v1.4.40b (April 17, 2006)
=========================
Enhancements:
-------------
1. Change: Combine 2 small memory allocations into 1.

Impact: None.

2. Change: Separate tx consumer and producer entries into separate
cache lines for better performance.

Impact: None.

3. Change: Compress firmware data to reduce driver size.

Impact: Driver now requires zib_inflate library which should be
available on most vendor kernels.

v1.4.39b (Mar. 10, 2006)
=======================
Fixes:
------
1. Problem: (CQ23181) Driver loses track of link changes in some cases.

Cause: In some cases, the status block gets a link change indication
that contradicts with the MII link status. This is due to
transient link signals during link changes.

Change: Add coalesce_now at the end of link change interrupt to flush
out the transient behavior.

Impact: None.

2. Problem: 5708 only supports 40-bit DMA addresses.

Cause: Limitation of the built-in PCIE-to-PCIX bridge.

Change: Add workaround code to make sure all DMA addresses are
less than 40 bits.

Impact: Some minor impact on performance on some 64-bits systems.
There should be practically no performance impact on i386 and
x86_64 systems.

3. Problem: "Copyright" deprecated in RPM spec file.

Change: Changed to "License".

Impact: Should be none on the distributions that we support.

v1.4.38b (Feb. 10, 2006)
=======================
Fixes:
------
1. Problem: Setting rx ring size to 255 causes memory allocation errors.

Cause: Multiple bugs that do not handle the full ring properly.

Change: Fixed all bugs related to full ring handling and changed
maximum ring size from 4080 to 1020 after discussion with
Dave Miller.

Impact: Maximum rx ring size is now smaller.

2. Problem: Compile warnings and panic on IA64.

Cause: not included.

Change: Added include .

Impact: None.

v1.4.36b (Jan. 19, 2006)
=======================
Version number update.

v1.3.36 (Jan. 17, 2006)
=======================
Fixes:
------
1. Problem: (CQ22827) bnx2 does not compile on 2.6.6 and earlier
kernels.

Cause: Introduced bug while fixing CQ22666.

Change: Fix compatibility code.

Impact: None.

2. Problem: (CQ22823) bnx2 reports extra .5 at the end of firmware
version string.

Change: Skip the last digit in the firmware version string.

Impact: None.

3. Problem: (CQ22585) WoL still does not work on 5708.

Cause: New WoL mechanism introduced in 1.3.34 has a flaw.

Change: Removed the workaround code and disabled WoL support
on 5708. During shutdown and suspend, the driver will
shutdown the device and WoL will be setup by the
bootcode according to the nvram's out-of-box WoL
setting.

Impact: 5708 will not support driver-initiated (ethtool-intiated)
WoL.

v1.3.35 (Jan. 17, 2006)
=======================
Fixes:
------
1. Problem: (CQ22666) bnx2 driver does not compile on RHEL3 U7.

Cause: if_mii() back-ported to RHEL3 U7.

Change: Adjusted the compatibility code.

Impact: None.

2. Problem: (CQ22718) UMP connection is lost after enabling WoL.

Cause: FORCE LINK was mistakenly set during WoL setup.

Change: Do not set FORCE LINK.

Impact: None.

v1.3.34 (Jan. 13, 2006)
=======================
Fixes:
------
1. Problem: (CQ22585) WoL does not work on 5708.

Cause: Internal bridge not in proper PME state.

Change: Added new firmware message to allow bootcode to help set up
WoL.

Impact: None.

Enhancements:
-------------
1. Change: Added compile option to include crc32 function for RH2.4
boot kernels.

Impact: None.

2. Change: Updated TSO firmware to handle ECN.

Impact: None.

v1.3.33 (Dec. 12, 2005)
=======================
Enhancements:
-------------
1. Change: Increased firmware hand-shake timeout from 50 msec to
100 msec. Also changed the delay from busy-wait udelay
to non-busy-wait msleep.

Impact: None.

2. Change: Added code to read nvram size from shared memory if
available. Otherwise, the size will come from the
flash table which only gives the smallest size for
that type of flash.

Impact: None.

3. Change: Added workaround to issue 2 separate IOs for interrupt
acknowledgement. The workaround is only used for INTA
(non-MSI) interrupts.

Impact: Slightly higher overhead for INTA interrupts.

v1.3.32 (Dec. 01, 2005)
=======================
Enhancements:
-------------
1. Change: Added PHY loopback to the loopback selftest.

Impact: None.

2. Change: (CQ21810) Added ethtool -d register dump.

Impact: None.

3. Change: Reduce the number of registers tested in selftest to make
the driver smaller.

Impact: None.

4. Change: Increased maximum rx ring size to 4080.

Impact: None.

5. Change: Changed rx checksum logic for better reliability.

Impact: None.

6. Change: Added 5708 B1 workarounds.

Impact: None.

v1.3.31 (Nov. 18, 2005)
=======================
Fixes:
------
1. Problem: (CQTO2080) Cannot pass traffic during 2nd ifup if IPMI
is enabled.

Cause: A flaw in driver/firmware handshake.

Change: Changed driver/firmware handshake by doing WAIT0 first before
writing the first signature.

Impact: None.

2. Problem: (CQTO2056) VLAN-tagged IPMI traffic fails after driver is
loaded.

Cause: Driver configures the NIC to keep the VLAN tag by default,
causing VLAN-tagged IPMI traffic to fail.

Change: Changed driver to always strip VLAN tags if IPMI is enabled.

Impact: VLAN will always be stripped when IPMI is enabled. This may
affect some applications that rely on raw VLAN packets.

Enhancements:
-------------
1. Change: Sync'ed up with latest upstream bnx2.

v1.3.29 (Oct. 6, 2005)
=======================
Fixes:
------
1. Problem: (CQTO1929) Traffic stops when MTU is greater than 1500
with TSO enabled.

Cause: TSO firmware bug.

Change: Updated to latest firmware.

Impact: None.

v1.3.28 (Sep. 29, 2005)
=======================
Fixes:
------
1. Problem: (CQTO1875) Traffic stops when running Nettack with TSO
turned on.

Cause: TSO firmware bug.

Change: Updated to latest firmware.

Impact: None.

2. Problem: (CQTO1575) ethtool -S shows non-zero rx_error_bytes.

Cause: Hardware errata.

Change: Ignore this counter and always report zero.

Impact: None.

v1.3.27 (Sep. 21, 2005)
=======================
Enhancements:
-------------
1. Change: Enabled ethernet@wirespeed on copper devices.

Impact: None.

2. Change: Enabled customized pre-emphasis and other serdes control
settings on 5708S backplane devices. A special PHY
register will be programmed according to the NVRAM value.

Impact: None.

3. Change: Modified Makefile to check for the source symbolic link
in the kbuild environment.

Impact: None.

4. Change: Improved NAPI poll processing so that all events will be
processed before interrupts are re-enabled. This will
reduce the number of unnecessary interrupts.

Impact: None.

5. Change: Add support for ETHTOOL_GPERMADDR (from John Linville)

Impact: None.

Fixes:
------
1. Problem: Bug in irq handler causing extra register read.

Cause: Bug in bnx2_interrupt() reading BNX2_PCICFG_MISC_STATUS
register when it is not necessary.

Change: Fixed the logic bug and added prefetch of status block in
msi handler.

Impact: None.

v1.3.25 (Aug. 22, 2005)
=======================
Fixes:
------
1. Problem: Ethtool register and memory tests fail on 5708.

Cause: Some code was not merged properly many versions ago.

Change: Merged in properly code.

Impact: None.

Enhancements:
-------------
1. Change: Slow down flash clock speeds

Impact: None.

2. Change: Code re-sync'ed with upstream driver.

Impact: None.

v1.3.24 (Aug. 16, 2005)
=======================
Enhancements:
-------------
1. Change: Changed all spin_lock_irqsave locks to spin_lock_bh for
better overall system performance. All code requiring
spin_lock runs in BH or user context.

Impact: None.

2. Change: Removed atomic operations in the transmit fast path.
Code should run a bit faster as atomic operations can be
quite slow.

Impact: None.

v1.3.23 (Aug. 10, 2005)
=======================
Enhancements:
-------------
1. Change: Added reporting of link speed to firmware.

Impact: None.

2. Change: Added shared memory base look-up.

Impact: None.

3. Change: Possible sparse fixes (from Peter Hagervall)
- use C99 struct initializers
- make a few arrays and structs static
- remove a few uses of literal 0 as NULL pointer
- use convenience function instead of cast+dereference in
bnx2_ioctl()
- remove superfluous casts to u8 * in calls to readl/writel

Impact: None.

4. Change: Updated documentation with the crc32 library requirement and
other minor updates.

Impact: None.

v1.3.22 (July 25, 2005)
=======================
Enhancements:
-------------
1. Change: Added check for default link speed setting in shared memory.
This allows some blade servers that don't support autoneg to
default to forced speed to speed up link-up time.

Impact: None.

2. Change: Changed timer code to speed up the timer after serdes autoneg.
This speeds up the time for parallel detection when the link
partner does not autoneg. After autoneg or parallel detction
completes, timer goes back to normal 1 HZ interval. With the
new scheme, link should be detected up using parallel detection
in less than 0.7 seconds. Autoneg normally completes in 120
msec exchanging base pages and 3 next pages.

Impact: None.

v1.3.21 (July 21, 2005)
=======================
Enhancements:
-------------
1. Change: Updated firmware to properly handle TSO packets with ECN
bits set.

Impact: None.

2. Change: Updated to latest rxp firmware.

Impact: None.

3. Change: Added check for the 2.5G capability in shared memory.

Impact: None.

4. Change: Expanded nvram support for 5708.

Impact: None.

Fixes:
------
1. Problem: (CQTO1511) Downing a team of bnx2 adapters causes hang.

Cause: Deadlock when the second adapter's close routine calls
flush_scheduled_work() because the linkwatch_event
is scheduled on the work queue when the first adapter
is closed. The linkwatch_event will try to get the rtnl_lock
which is already held by the bnx2_close routine.

Change: Fixed by not calling flush_scheduled_work(). Instead,
use a flag to indicate work is pending and wait until
the flag is cleared.

Impact: None.

2. Problem: (CQTO1439) ethtool -S on 5708 causes oops.

Cause: A pointer is not initialized if the device is 5708.

Change: Added proper initialization.

Impact: None.

3. Problem: Some error counters are mis-reporting.

Cause: The workaround for the hw errata is not applied properly
on the chips with the errata.

Change: Added proper checks for the workaround.

Impact: None.

4. Problem: High BER on 5708 SerDes.

Cause: hardware errata.

Change: Added workaround for 5708 A0 and B0.

Impact: None.

v1.3.19 (May 27, 2005)
=======================
Enhancements:
-------------
1. Change: Merged 5708 code with the latest 1.1.19.

Impact: None.

Fixes:
------
1. Problem: (CQTO1260) 5708S does not link at 1000Mbps when forced. It
links at 2500Mbps when connected back-to-back with another
5708S.

Cause: 2.5G bit is still turned on.

Change: Fixed by turning off 2.5G when the speed is forced.

Impact: None.

v1.1.19 (May 26, 2005)
=======================
Enhancements:
-------------
1. Change: Made significant changes to merge into the kernel. Among
them, consolidate all source files into bnx2.[ch] and
bnx2_fw.h, change structure style register definitions
to offset based.

Impact: None.

Fixes:
------
1. Problem: Excessive stack usage.

Cause: Use of local variable array.

Change: Fix excessive stack usage in bnx2_alloc_bad_rbuf() by
replacing local variable array with kmalloc array. Also
changed function to return error code, and changed some
of the callers to check for the return code.

Impact: None.

2. Problem: Bug in receive checksum.

Cause: Software bug.

Change: Fix bug in rx checksum by indicating CHECKSUM_UNNECESSARY
only when the hw calculated checksum is 0xffff.

Impact: None.

3. Problem: Excessive busy loop.

Cause: Software bug.

Change: Replaced one excessive udelay of 15msec with msleep since
the calling context is always process.

Impact: None.

4. Problem: Need to call flush_scheduled_work() and bnx2_netif_stop().

Cause: Bug in bnx2_close().

Change: Fix bug in bnx2_close() by calling flush_scheduled_work()
since we are using a work queue in netdev watchdog. Also
added bnx2_netif_stop() call in bnx2_close().

Impact: None.

5. Problem: Some symbols do not have bnx2 prefix and are not static.

Change: Add bnx2_ prefix to some remaining names and mark some
remaining names static.

Impact: None.

v1.1.17 (Apr. 7, 2005)
=======================
Fixes:
------
1. Problem: Driver does not compile on 2.6.12 kernel.

Cause: pci_dev->slot_name has been deprecated.

Change: replaced with pci_name.

Impact: None. All kernels supported by bnx2 including 2.4.21-*EL have
pci_name defined.

v1.1.16 (Mar. 16, 2005)
=======================
Fixes:
------
1. Problem: (CQTO936 & 1004) Tx carrier and rx_byte_errors reported
during normal operations.

Cause: 5706 hardware errata on these 2 statistics counters.

Change: Modified driver to skip these 2 counters.

Impact: These 2 counters will always report 0 and not the true
statistics.

v1.3.15 (Mar. 11, 2005)
======================
Enhancements:
-------------
1. Change: Added SGMII 10/100/1000 Mbps and fiber mode 1000/2500 Mbps
support.

Impact: None.

v1.1.15 (Mar. 09, 2005)
=======================
Enhancements:
-------------
1. Change: Added code to program proper phy settings for jumbo
frames on copper and serdes devices.

Impact: None.

2. Change: Changed INTx ISR to handle a valid case where INTx
arrives before status block update.

Impact: None.

3. Change: Added a separate ISR for MSI to handle subtle differences
between INTx and MSI.

Impact: None.

v1.1.14 (Mar. 03, 2005)
======================
Fixes:
------
1. Problem: netdump does not work on latest RH3EL errata kernel.

Cause: #define RED_HAT_LINUX_KERNEL removed from kernel
include files, causing netdump poll function to
be compiled wrong for RH kernels.

Change: Changed Makefile to workaround the problem.

Impact: None.

v1.1.12 (Feb. 25, 2005)
======================
Fixes:
------
1. Problem: (CQTO1062) Driver allows ethtool to set illegal speed/duplex
on fiber cards.

Cause: Missing checks for the case where autoneg is off.

Change: Added proper checks.

Impact: No.

v1.1.11 (Feb. 18, 2005)
======================
Enhancements:
-------------
1. Change: (CQTO901) Added bnx2(4) man page.

Impact: None.

v1.1.10 (Feb. 16, 2005)
======================
Fixes:
------
1. Problem: Wrong device ID in pci_dev_id table.

Change: Fixed ID.

Impact: None.

v1.1.9 (Feb. 10, 2005)
======================
Fixes:
------
1. Problem: (CQTO771) Driver fails to compile on RHEL3 update 4.

Cause: The RH kernel has back-ported some netif functions
not found in the same vanilla kernel version. Duplicate
function names are defined.

Change: Added intelligence in Makefile to detect such conditions
and change the CFLAGS accordingly.

Impact: None.

2. Problem: (CQTO1017) Driver allows 1000 half duplex autoneg off.

Cause: Missing validity check.

Change: Added check.

Impact: None.

Enhancements:
-------------
1. Change: The code to handle tx queue full condition was redone
to properly handle all boundary and race conditions.

Impact: Minimum tx ring size is now MAX_SKB_FRAGS+1.

2. Change: Tx timeout code was changed to work queue context.
This allows netif to be shutdown gracefully before
chip reset.

Impact: None.

3. Change: Added memory barriers to ISR and NAPI poll for
correctness.

Impact: None.

v1.1.8 (Feb. 01, 2005)
======================
Fixes:
------
1. Problem: (CQTO969) No interupts on a system that does not
support MSI.

Cause: On this system, the MSI generated in the MSI test
terminates with Master Abort which is a fatal
condition for the chip.

Change: A chip reset is added when MSI test fails to bring
the chip back to normal operations again (in INTx mode).

Impact: None.

Enhancements:
-------------
1. Change: Removed register 0x84 from the ethtool register test.
This is an interrupt control register that should
not be touched to prevent unwanted interrupts.

Impact: None.

v1.1.7 (Jan. 28, 2005)
======================
Enhancements:
-------------
1. Change: Added interrupt test when MSI is enabled. If MSI test
fails, driver will fallback to INTx mode.

Impact: None.

2. Change: Added test for certain chipsets where MSI is known
to fail, and disable MSI unconditionally when
such chipsets are found.

Impact: None.

3. Change: Removed support for 1000 Mbps half duplex.

Impact: 1000 Mbps half duplex will no longer work.

v1.1.6 (Jan. 26, 2005)
======================
Fixes:
------
1. Problem: (CQTO940) MTU size not set properly when device is down.

Cause: bnx2_change_mtu only handled the "up" case.

Change: Simple fix to handle the "down" case as well.

Impact: None

2. Problem: (CQTO926) 5706S does not autoneg properly after the
tx cable is pulled.

Cause: If the link partner is autonegotiating, autoneg will
fail when the tx cable is pulled. The software will
turn off autoneg seeing that the rx cable is still
attached with SIGNAL_DETECT. When the tx cable is
re-attached, autoneg is still off and the link partner
will not establish link.

Change: Added code to poll another PHY register to check if
configs are received when autoneg is disabled.

Impact: None

Enhancements:
-------------
1. Change: Added OEM product name strings.

Impact: None.

v1.1.5 (Jan. 25, 2005)
======================
Fixes:
------
1. Problem: PCI-X bus speed may not be detected correctly by the driver,
causing failure because certain register settings are done
based on bus speed.

Cause: hardware problem.

Change: Use a different register to detect PCI-X speed.

Impact: None.

v1.1.4 (Jan. 17, 2005)
======================
Fixes:
------
1. Problem: 5706S does not reliably detect link up or down.

Cause: hardware problem.

Change: Enabled hardware workaround which is effective in
A2 and newer chips only.

Impact: None.

v1.1.3 (Jan. 13, 2005)
======================
Fixes:
------
1. Problem: netdump does not work.

Cause: poll_controller routine does not work in NAPI mode.

Change: Fixed poll_controller routine for NAPI mode.

Impact: None.

Enhancements:
-------------
1. Change: Added the new mmiowb macro which is used mainly in NUMA
machines to guarantee PCI ordering.

Impact: None.

2. Change: Added OEM product name strings.

Impact: None.

3. Change: Changed ONE_TDMA workaround on systems with P64H bridge to
PING_PONG_DMA on all systems using PCI.

Impact: Better performance and better compatibility on all PCI
systems.

4. Change: Added "disable_msi" parameter to allow disabling MSI.

Impact: None.

5. Change: Reduced default tx coalescing parameters for better
tx only performance such as ttcp.

Impact: None.

6. Change: Changed NIC detection console message to display more
information.

Impact: None.

7. Change: Cleaned up some Linux .h files that are not needed.

Impact: None.

8. Change: Cleaned up the nvram routines.

Impact: None.

v1.1.2 (Nov. 11, 2004)
======================
Fixes:
------
1. Problem: Unable to load the driver on more than 2 or 3 devices.

Cause: Default register space is too big. System fails to map
the register space on the 3rd or 4th device.

Change: Changed driver to map a smaller register space as the higher
registers are not needed for standard operations.

Impact: None.

v1.1.1 (Nov. 9, 2004)
======================
Fixes:
------
1. Problem: (CQTO656) One remaining ethtool parameter can be set out of
range.

Cause: Wrong upper bounds in code.

Change: Fixed upper bound.

Impact: None.

1. Problem: 5706 A1 cannot be run on a PCI bus.

Cause: Hardware errata.

Change: Added workaround to detect 5706 A1 on PCI bus and abort.

Impact: Driver will not load 5706 A1 on PCI bus.

v1.1.0 (Oct. 29, 2004)
======================
Fixes:
------
1. Problem: (CQTO663) No link on fiber NIC set to autoneg when
the link partner is set to forced speed.

Cause: No code to handle this case.

Change: Added code to check SIGNAL DETECT when autoneg fails,
and turn off autoneg when appropriate. Also added code
to force a link down when speed settings are changed.

Impact: None.

2. Problem: (CQTO649) ifconfig up/down can cause system to
hang on 2.6 kernels using mmconfig.

Cause: Dummy read in the kernel's pci_mmcfg_write routine
may cause system to hang during D3hot -> D0
transition. The PLL may lose lock during the internal
D0 transition chip reset and cause the dummy read to
hang.

Change: The PLL problem will be fixed in A2. Meanwhile, the
driver is changed to go into D3hot only if wol is
enabled.

Impact: Minor impact in increased power consumption when
the driver is shutdown with wol disabled.

3. Change: Changed to use pci_get_device as pci_find_device
will be deprecated soon.

Impact: None.

4. Problem: (CQTO656) Some ethtool parameters can be set out of range.

Cause: Wrong upper bounds in code or documentation.

Change: Fixed code and documentation.

Impact: None.

v1.0.15 (Oct. 15, 2004)
======================
Fixes:
------
1. Problem: (CQTO644) Data corruption when sending FTP traffic on
Dell Precision 530MT.

Cause: PCI bridge errata.

Change: Added code to enable ONE_TDMA workaround when P64H
PCI bridge is detected.

Impact: Slower tx performance on systems using P64H bridge.

2. Problem: (CQTO643) Driver allows MTU to be set up to 9004.

Cause: Driver used the wrong upper bound limit.

Change: Fixed the upper bound.

Impact: None.

3. Problem: Driver does not support forced speed on 5706S.

Cause: Missing software logic.

Change: Added code to support forced 1000 Full and Half duplex.

Impact: None.

4. Change: Added workaround to disable PERR generation on
5706 A1 when it is in PCI 64-bit slot.

Impact: None.

v1.0.14 (Oct. 05, 2004)
======================
Fixes:
------
1. Problem: Driver load/unload hangs on some machines.

Cause: Transition delay required during D3hot -> D0 transition.

Change: Added necessary delay.

Impact: None.

v1.0.12 (Oct. 04, 2004)
======================
Fixes:
------
1. Problem: (CQTO609) New flow control parameter does not take
effect until ifdown/ifup or link down/up.

Cause: New flow control settings are only configured during
link up. The driver did not check flow control
advertisement changes and therefore no re-negotiation
and no link down.

Change: Fixed logic so that link will always go down whenever
there is a change a flow control advertisement.

Impact: None.

2. Problem: (CQTO612) VLAN packet reception not working.

Cause: VLAN #define not setup properly.

Change: Fixed #define for VLAN.

Impact: None.

3. Problem: (CQTO628) WoL not functioning correctly.

Cause: Multiple problems in the WoL code.

Change: Fixed by:
1. using sort mode.
2. setting up mac address correctly.

Impact: None.

Enhancements:
-------------
1. Change: Added support for non-dword and non-aligned write access
to eeprom, allowing ethtool -E to work.

Impact: None.

v1.0.11 (Sep. 24, 2004)
======================
Fixes:
------
1. Problem: (CQTO600) Kernel panic when attempting to ftp on
Fedora kernel.

Cause: skbuffs are 4-byte aligned on Fedora, causing
the rx headers to be misaligned. skbuffs are
16-byte aligned on other standard kernels.

Change: Removed any assumptions about skbuff alignment
and added code to align all rx skbuffs to 8-byte
boundaries.

Impact: None.

Enhancements:
-------------
1. Change: Added netif_carrier_off to Driver init code so that
the initial link state is off.

Impact: None.

v1.0.10 (Sep. 23, 2004)
======================
Fixes:
------
1. Problem: (CQTO599) Driver fails to compile on RH 3.0ES.

Cause: Bug in poll_bcm5706 where bp is referenced without
being defined.

Change: Fixed the minor bug.

Impact: None.

v1.0.9 (Sep. 23, 2004)
======================
Fixes:
------
1. Problem: Jumbo frames not working reliably.

Cause: Bug in bcm5706_reuse_rx_skb.

Change: Fixed the bug so that the host address is properly
copied from one BD to the other.

Impact: None.

Enhancements:
-------------
1. Change: Change the locking scheme for more reliable open/close/ioctl
operations where the spinlock is needed.

Impact: None.

2. Change: Added minimum MTU size check for MTU changes.

Impact: None.

v1.0.8 (Sep. 20, 2004)
======================
Fixes:
------
1. Problem: (CQTO561) Kernel panic on RH30EL after repeated
driver load/unload.

Cause: Occasionally, the system is unable to map device
registers, causing subsequent register access to fail.

Change: Added check for the return value from ioremap, and exit
gracefully if it fails.

Impact: None.

2. Problem: (CQTO574) NETDEV WATCHDOG when running 5706 A1 on
PCIX 133MHz slot.

Cause: Some hw register setup required for 133 Mhz.

Change: Added the register setup code.

Impact: None.

3. Problem: (CQTO468) Link does not go down after changing from
10Mbps full (forced) to 10Mbps half (forced) and vice versa
when the link partner is also using forced speed.

Cause: Delay not long enough for the link to go down.

Change: Not practical to increase delay as a very long delay is
needed for the link to go down. Added code to record the
proper link speed and duplex when speed is forced so that
ethtool will return the proper speed without the link going
down. Note that the link will go down if the link partner
has autoneg turned on, ensuring that the link partner will
see the link change.

Impact: None.

Enhancements:
-------------
1. Change: Added power management and WOL during device close. This
will allow WOL to work after Linux shutdown.

Impact: None.

2. Change: Changed driver so that ethtool will report invalid
speed after ifdown.

Impact: None.

3. Change: Updated tpatfw.h

Impact: None.

v1.0.7 (Sep. 14, 2004)
======================
Fixes:
------
1. Problem: (CQTO523) 5706 A1 hangs after a thousand iterations of
load/ifup/ifdown/unload.

Cause: The driver may be servicing an interrupt
within 15 msec of chip reset, causing the chip to hang.
The problem was aggravated by the timer mode
coalescing which created an excessive number of
interrupts (hardware problem).

The Driver may also occasionally see
the wrong firmware signature that will cause it to abort.

Change: Added synchronization to make sure all pending interrupts
are serviced before resetting the chip. Also changed to
collect mode coalescing. The firmware signature problem
will be fixed in boot code.

Impact: The use of collect mode coalescing may affect performance.

2. Problem: (CQTO558) Unable to load driver on some early 2.6 kernels.

Cause: pci_dma_sync_single_for_* routines not defined on early
2.6 kernels.

Change: Added compatibility defines for earlier kernels.

Impact: None.

v1.0.6 (Sep. 08, 2004)
======================
Fixes:
------
1. Problem: (CQTO523) 5706 A1 hangs during repeated driver ifup/down.

Cause: No delay after chip reset for A1.

Change: Added 15 msec delay after chip reset for A1.

Impact: None.

2. Problem: (CQTO468) Link does not go down after changing from
10Mbps full (forced) to 10Mbps half (forced) and vice versa.

Cause: Not enough delay after forcing link down.

Change: Added proper delay for link to go down.

Impact: None.

v1.0.5 (Sep. 02, 2004)
======================
Enhancements:
-------------
1. Change: Added support for ethtool -c, ethtool -C, ethtool -p,
and firmware version for ethtool -i.

Impact: None.

Fixes:
------
1. Problem: 5706C not advertising 1000 half duplex.

Cause: 1000 full duplex overwrites 1000 half duplex.

Change: Fixed the bug so that the 2 bits are or'ed together.

Impact: None.

2. Problem: ethtool -A does not change the flow control settings
in all cases.

Cause: Flow control settings not zeroed out before setting new
values.

Change: Minor bug fix to zero out the value.

Impact: None.

v1.0.4 (Sep. 02, 2004)
======================
Fixes:
------
1. Problem: (CQTO504) Multiple NFS transfers will hang some
connections.

Cause: Driver discards some receive packets when the
error status is non-zero.

Change: Changed the driver to only discard receive packets
when the defined error bits in the error status are
non-zero.

Impact: None.

v1.0.3 (Sep. 01, 2004)
======================
Enhancements:
-------------
1. Problem: Driver does not support ethtool -t self test and
ethtool -S statistics.

Change: Added ethtool self test and statistics.

Impact: None.

Fixes:
------
1. Problem: (CQTO478) Kernel still panics when transmitting certain
files using NFS after many iterations

Cause: Tx DMA stalls on certain UDP packets, causing NFS
client to stall.

Change: More fixes made in firmware.

Impact: None.

v1.0.2 (Aug. 26, 2004)
======================
Enhancements:
-------------
1. Problem: Driver does not work on big endian machines.

Change: Ported and tested on SPARC64 machine.

Impact: None.

Fixes:
------
1. Problem: (CQTO478) Kernel panics when transmitting certain
files using NFS.

Cause: Tx DMA stalls on certain UDP packets, causing NFS
client to stall.

Change: Fixed in firmware.

Impact: None.

2. Problem: (CQTO469) Unable to modify flow control parameters

Cause: Did not call setup_phy after the parameters are changed.

Change: Added call to setup_phy after parameters are changed.

Impact: None.

3. Problem: (CQTO467) 5706 does not autonegotiate properly after
changing settings with ethtool.

Cause: This is an ethtool limitation as the proper advertising
parameters are not passed to the driver properly.

Change: Implemented a new scheme to work around the problem to
allow users to specify full autoneg, single speed autoneg,
and fixed speed.

Impact: None.

4. Problem: ethtool -e does not work.

Cause: Various bugs in the nvram routines.

Change: Fixed and tested nvram routines on little endian and big endian
machines.

Impact: None.

v1.0.1 (Aug. 18, 2004)
======================
Fixes:
------
1. Problem: (CQTO459) 5706 NIC does not get link.

Cause: Boot code timing out in WAIT2 state before driver is ready.

Change: Moved the WAIT2 state ahead in the driver reset sequence
as a temporary workaround until it is fixed in boot code.

Impact: None.

2. Problem: (CQTO463) Kernel panics when loading the driver on
RH30EL (2.4.21-4.EL)

Cause: Older kernel used different API to allocate and register
netdev.

Change: Added older APIs to be used on older kernels.

Impact: None.

v1.0.0 (Aug. 13, 2004)
======================
Initial release
brcm_dd_nic_nx2-2_2_3f-1_74_22_rhel6_32-64_chg