		      QLogic Driver Release Notes

		       QLogic Corporation
		       All rights reserved


Table of Contents

1. Change History
2. Known Issues
3. Notices
4. Contacting Support


1. Change History

This section contains:

 * 1.1 Hardware Support
 * 1.2 Software Component
 * 1.3 Bug Fixes


1.1 Hardware Support

Initial Drop 3.1.1.0:

 * Support for 2400/2500/2600/2700/2800 Series Fibre Channel adapters
 * Support for 8100/8200/8300 Series Converged Network Adapters
 * Mt. Rainier support.

Between versions 3.1.1.0 and 3.1.8.0:

 * None

1.2 Software Components

Between versions 3.1.1.0 and 3.1.3.0:

 * None

Between versions 3.1.3.0 and 3.1.4.0:

 * End-to-End QoS fabric priority support
 * Update ISP25XX fw version to 8.08.01.

Between versions 3.1.4.0 and 3.1.6.0:

 * None

Between versions 3.1.6.0 and 3.1.7.0:

 * Revert update ISP25XX fw version to 8.08.01.
   FW version is now back to 8.07.00

Between versions 3.1.7.0 and 3.1.8.0:

 * None

1.3 Bug Fixes

Between versions 3.1.1.0 and 3.1.2.0:

Problem Description:
Improvements
Solution:
Various Mach-related fixes uncovered during testing.

Problem Description:
Failing during unload testing for ESX 6.7
Solution:
Proper cleanup during detach function. 

Between versions 3.1.2.0 and 3.1.3.0:

Problem Description:
Issue with Mach adapter fw dump
Solution:
Fix firmware dump template entry to not
insert extra dword of info.

Between versions 3.1.3.0 and 3.1.4.0:

Problem Description:
Secure flash requires that the driver only writes to flash through
MB Cmds for Qlipper and newer adapters.
Solution:
Patch up holes in write flash routine that could cause the driver to use register access.

Problem Description:
Driver was advertising Application Services support in the RFT_ID command
regardless if enabled or not.
Solution:
Only enable Application Services if ql2xvmidsupport is turned on.

Problem Description:
Target devices are temporariry not accessible when the link toggle occurs on one of the target device paths.
Solution:
Clear the "login needed" bit when the initial login attempt fails. This login will get
retried in the relogin dpc call. This prevents target ports remaining in a "login needed"
state despite disappearing from the fabric entirely.

Problem Description:
Driver was not handling ABTS received IOCB in response to a PUREX IOCB failure.
Solution:
Code was implemented to handle ABTS received.

Problem Description:
Driver would not send the full RDP response with a switch port that was not in the logged in state.
Solution:
Remove the limitation as the new firmware now supports splitting up the RDP response payload over multiple frames
This will be based on a check of the supported firmware versions.

Problem Description:
Code improvement.
Solution:
Move ql2xvmidsupport check to module_init routine

Problem Description:
VMID information was not getting displayed for the NPIV key value in the vmkmgmt interface.
Solution:
Added VMID information to NPIV vmkmgmt output

Problem Description:
Code improvement
Solution:
DPORT improvement - return mb1 and mb2 contents after execution.
Also added more info in DPORT AEN messages.

Problem Description:
ESX 6.7 IOVP DDV testing was failing.
Solution:
Use proper cleanup of driver resources in error paths

Between versions 3.1.4.0 and 3.1.5.0:

Problem Description:
Flash writes were failing.
Solution:
Ensure dword count and byte count were used correctly in flash write routine.

Between versions 3.1.5.0 and 3.1.6.0:

Problem Description:
Driver read incorrectly from flash for E2E QoS values,
leading to invalid table readings and disabling of feature.
Solution:
Pass in byte count instead of dword count to flash read function.

Problem Descriptoin:
RDP response payload was not formatted correctly, leading to missing
contents or response frame not transmitted.
Solution:
Properly populate link services attribute and implement correct check
of firmware version and login state when building payload.

Problem Description: 
Driver was advertising 1G speed support for 8G adapters.
Solution:
Remove 1G speed support for 8G adapters.
Also, cleaned up supported speed code for various features and adapters.

Problem Description:
FDMI info showing incorrect supported speeds for 16G mezz adapters in FDMI.
Solution
Remove 4G supported speed if NVRAM parameter indicates to do so.

Between versions 3.1.6.0 and 3.1.7.0:

None 

Between versions 3.1.7.0 and 3.1.8.0:

Problem Description:
When E2E QoS solution was disabled on a LUN, driver was still populating
the priority field in the CS_CTL for I/O to that LUN.
Solution:
Don't fall back to standard fabric priority QoS unless the fabric priority
bit in the NVRAM is set.


2. Known Issues
None


3. Notices

Information furnished in this document is believed to be accurate and
reliable. However, Cavium, Inc. assumes no responsibility for
its use, nor for any infringements of patents or other rights of
third parties which may result from its use.  Cavium, Inc. 
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.  Cavium, Inc. 
makes no representation nor warranty that such applications are
suitable for the specified use without further testing or
modification. Cavium, Inc. assumes no responsibility for any
errors that may appear in this document.


4. Contacting Support

   For further assistance, contact QLogic Technical Support at:
   http://support.qlogic.com


Trademarks

Accelera, Accelerating Cluster Performance, InfiniCon Systems,
InfiniNIC, InfiniPath, InfiniView, QLA, QLogic, the QLogic logo,
ReadyPath, SANdoctor, SANsurfer, and SilverStorm are registered
trademarks of QLogic Corporation. All other brand and product names
are trademarks or registered trademarks of their respective owners.



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