<?xml version="1.0" encoding="UTF-8"?>
<manifest schema_version="2.0.0.0">
  <revision_history>
    <product_version>
      <id product="4dace5a803344041ad392f9b2b571002" version="07e3933067a04e7e85679535a8b4f00f" lucid_version="HPE_MR932i-p@8.16.1.0-01003-00004-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="8.16.1.0-01003-00004" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, UncorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for UBM11 backplane</li>
	<li>Refine the message on HII prereview configuration for the foreign import</li>
	<li>Standardize PSoC printing versioning info as 2 digit major/2 digit minor for Hardware and Firmware</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, UncorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for UBM11 backplane</li>
	<li>Refine the message on HII prereview configuration for the foreign import</li>
	<li>Standardize PSoC printing versioning info as 2 digit major/2 digit minor for Hardware and Firmware</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00157381en_us Advisory: HPE MR932i-p Storage Controller - Incorrect Controller Port Number To Box Number Mapping in iLO GUI</li>
	<li>Fix a00157199en_us Advisory: HPE MR932i-p Storage Controller - The &quot;StorageDevice.1.2.BatteryOK&quot; Event Is Not Consistently Generated When the Energy Pack Is Reconnected to an HPE MR932i-p Storage Controller</li>
	<li>Fix a00157775en_us Advisory: HPE MR932i-p Storage Controller - Cache-Offload Event Is Not Reported in the Integrated Management Log (IML) Via Redfish</li>
	<li>Fix an issue that backplane firmware update fails if more than 16 slots are connected to the MR932i-p controller.</li>
	<li>Fix an issue that Redfish POST ResetToDefaults.PreserveVolumes operation fails with Unsupported Operation.</li>
	<li>Fix an issue that &quot;Controller status changes to failed&quot; event is generated when doing firmware update. Please note the event may still happen when downgrading firmware to 8.15.1.0-01003-00001 since the fix is not available in the old version</li>
	<li>Fix an issue that DriveOffline and DriveOfflineCleared events are logged when auto rebuild start on the re-inserted drive</li>
	<li>Fix an issue that Energy Pack temperature sensor thresholds are reported incorrectly</li>
	<li>Fix an issue that SCSI Device ModeSense failures with format corruption warnings on ESXI9.0 OS after boot</li>
	<li>Fix an issue that firmware may not identify the drive properly to puncture when more than one rebuild/copyback tasks running.</li>
	<li>Fix a rare issue that controller is stuck at DDR SPD i2c read during reboot test</li>
	<li>Fix a rare issue that controller may hang in cache offload module after factory repurpose command issued followed by a power cycle</li>
	<li>Fix an issue that arbitrary firmware image size value used in platform measurement when reading data</li>
	<li>Fix a rare issue that drives might be marked as failed with phy toggling after creating volume.</li>
	<li>Fix a rare issue that Energy Pack communication fail does not reflect, and causes cache offload failed</li>
	<li>Fix a rare issue that firmware hang caused by the NAND flash hardware entering a bad state after a program failure while doing factory repurpose</li>
	<li>Fix an issue that changing LKM to EKM encryption mode using Redfish fails</li>
	<li>Fix an issue that controller status shows &quot;Need Attention&quot; in RBSU menu when drives are connected to controller</li>
	<li>Fix an issue that auto assignment is not applied on the auto-configured JBOD in a fresh boot.</li>
	<li>Remove &ldquo;Encrypted@Redfish.AllowableValues&quot; to match Boolean type behavior</li>
	<li>Fix an issue that controller firmware fault might be observed when partial-capacity volumes are assigned to different physical functions and moved to Offline.</li>
	<li>Fix a rare case that controller may fault when the foreign drive&#39;s primary DDF record is invalid</li>
	<li>Fix a potential controller fault triggered by frequent drive medium errors during Online Capacity Expansion</li>
	<li>Fix a rare issue that particular NVMe drive model state changes to Unusable with drive hotplug</li>
	<li>Fix a rare issue that SED may fail to reprovision if the drive is removed during import and controller reset</li>
	<li>Fix a potential controller fault triggered by IO counter mismatches during overlapping FLR (Function Level Reset) and task management operations</li>
	<li>Fix a rare issue that firmware fault may occur if a drive takes too long (over 70s) to fix errors, especially during task management</li>
	<li>Fix a potential issue that alternative boot chain recovery fails to trigger if secure boot authentication has failed</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00157381en_us Advisory: HPE MR932i-p Storage Controller - Incorrect Controller Port Number To Box Number Mapping in iLO GUI</li>
	<li>Fix a00157199en_us Advisory: HPE MR932i-p Storage Controller - The &quot;StorageDevice.1.2.BatteryOK&quot; Event Is Not Consistently Generated When the Energy Pack Is Reconnected to an HPE MR932i-p Storage Controller</li>
	<li>Fix a00157775en_us Advisory: HPE MR932i-p Storage Controller - Cache-Offload Event Is Not Reported in the Integrated Management Log (IML) Via Redfish</li>
	<li>Fix an issue that backplane firmware update fails if more than 16 slots are connected to the MR932i-p controller.</li>
	<li>Fix an issue that Redfish POST ResetToDefaults.PreserveVolumes operation fails with Unsupported Operation.</li>
	<li>Fix an issue that &quot;Controller status changes to failed&quot; event is generated when doing firmware update. Please note the event may still happen when downgrading firmware to 8.15.1.0-01003-00001 since the fix is not available in the old version</li>
	<li>Fix an issue that DriveOffline and DriveOfflineCleared events are logged when auto rebuild start on the re-inserted drive</li>
	<li>Fix an issue that Energy Pack temperature sensor thresholds are reported incorrectly</li>
	<li>Fix an issue that SCSI Device ModeSense failures with format corruption warnings on ESXI9.0 OS after boot</li>
	<li>Fix an issue that firmware may not identify the drive properly to puncture when more than one rebuild/copyback tasks running.</li>
	<li>Fix a rare issue that controller is stuck at DDR SPD i2c read during reboot test</li>
	<li>Fix a rare issue that controller may hang in cache offload module after factory repurpose command issued followed by a power cycle</li>
	<li>Fix an issue that arbitrary firmware image size value used in platform measurement when reading data</li>
	<li>Fix a rare issue that drives might be marked as failed with phy toggling after creating volume.</li>
	<li>Fix a rare issue that Energy Pack communication fail does not reflect, and causes cache offload failed</li>
	<li>Fix a rare issue that firmware hang caused by the NAND flash hardware entering a bad state after a program failure while doing factory repurpose</li>
	<li>Fix an issue that changing LKM to EKM encryption mode using Redfish fails</li>
	<li>Fix an issue that controller status shows &quot;Need Attention&quot; in RBSU menu when drives are connected to controller</li>
	<li>Fix an issue that auto assignment is not applied on the auto-configured JBOD in a fresh boot.</li>
	<li>Remove &ldquo;Encrypted@Redfish.AllowableValues&quot; to match Boolean type behavior</li>
	<li>Fix an issue that controller firmware fault might be observed when partial-capacity volumes are assigned to different physical functions and moved to Offline.</li>
	<li>Fix a rare case that controller may fault when the foreign drive&#39;s primary DDF record is invalid</li>
	<li>Fix a potential controller fault triggered by frequent drive medium errors during Online Capacity Expansion</li>
	<li>Fix a rare issue that particular NVMe drive model state changes to Unusable with drive hotplug</li>
	<li>Fix a rare issue that SED may fail to reprovision if the drive is removed during import and controller reset</li>
	<li>Fix a potential controller fault triggered by IO counter mismatches during overlapping FLR (Function Level Reset) and task management operations</li>
	<li>Fix a rare issue that firmware fault may occur if a drive takes too long (over 70s) to fix errors, especially during task management</li>
	<li>Fix a potential issue that alternative boot chain recovery fails to trigger if secure boot authentication has failed</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.16.1.0-01003-00004" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, UncorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>DriveMetrics: BadBlockCount, ReadIOKiBytes, WriteIOKiBytes, PowerOnHours, NVMeSMART (MVMeSMART attributes are supported for NVMe drive only)</li>
			<li>EnvironmentMetrics for Drive Resource: TemperatureCelsius.Reading</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for UBM11 backplane</li>
	<li>Refine the message on HII prereview configuration for the foreign import</li>
	<li>Standardize PSoC printing versioning info as 2 digit major/2 digit minor for Hardware and Firmware</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, UncorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>DriveMetrics: BadBlockCount, ReadIOKiBytes, WriteIOKiBytes, PowerOnHours, NVMeSMART (MVMeSMART attributes are supported for NVMe drive only)</li>
			<li>EnvironmentMetrics for Drive Resource: TemperatureCelsius.Reading</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for UBM11 backplane</li>
	<li>Refine the message on HII prereview configuration for the foreign import</li>
	<li>Standardize PSoC printing versioning info as 2 digit major/2 digit minor for Hardware and Firmware</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00157381en_us Advisory: HPE MR932i-p Storage Controller - Incorrect Controller Port Number To Box Number Mapping in iLO GUI</li>
	<li>Fix a00157199en_us Advisory: HPE MR932i-p Storage Controller - The &quot;StorageDevice.1.2.BatteryOK&quot; Event Is Not Consistently Generated When the Energy Pack Is Reconnected to an HPE MR932i-p Storage Controller</li>
	<li>Fix a00157775en_us Advisory: HPE MR932i-p Storage Controller - Cache-Offload Event Is Not Reported in the Integrated Management Log (IML) Via Redfish</li>
	<li>Fix an issue that backplane firmware update fails if more than 16 slots are connected to the MR932i-p controller.</li>
	<li>Fix an issue that Redfish POST ResetToDefaults.PreserveVolumes operation fails with Unsupported Operation.</li>
	<li>Fix an issue that &quot;Controller status changes to failed&quot; event is generated when doing firmware update. Please note the event may still happen when downgrading firmware to 8.15.1.0-01003-00001 since the fix is not available in the old version</li>
	<li>Fix an issue that DriveOffline and DriveOfflineCleared events are logged when auto rebuild start on the re-inserted drive</li>
	<li>Fix an issue that Energy Pack temperature sensor thresholds are reported incorrectly</li>
	<li>Fix an issue that SCSI Device ModeSense failures with format corruption warnings on ESXI9.0 OS after boot</li>
	<li>Fix an issue that firmware may not identify the drive properly to puncture when more than one rebuild/copyback tasks running.</li>
	<li>Fix a rare issue that controller is stuck at DDR SPD i2c read during reboot test</li>
	<li>Fix a rare issue that controller may hang in cache offload module after factory repurpose command issued followed by a power cycle</li>
	<li>Fix an issue that arbitrary firmware image size value used in platform measurement when reading data</li>
	<li>Fix a rare issue that drives might be marked as failed with phy toggling after creating volume.</li>
	<li>Fix a rare issue that Energy Pack communication fail does not reflect, and causes cache offload failed</li>
	<li>Fix a rare issue that firmware hang caused by the NAND flash hardware entering a bad state after a program failure while doing factory repurpose</li>
	<li>Fix an issue that changing LKM to EKM encryption mode using Redfish fails</li>
	<li>Fix an issue that controller status shows &quot;Need Attention&quot; in RBSU menu when drives are connected to controller</li>
	<li>Fix an issue that auto assignment is not applied on the auto-configured JBOD in a fresh boot.</li>
	<li>Remove &ldquo;Encrypted@Redfish.AllowableValues&quot; to match Boolean type behavior</li>
	<li>Fix an issue that controller firmware fault might be observed when partial-capacity volumes are assigned to different physical functions and moved to Offline.</li>
	<li>Fix a rare case that controller may fault when the foreign drive&#39;s primary DDF record is invalid</li>
	<li>Fix a potential controller fault triggered by frequent drive medium errors during Online Capacity Expansion</li>
	<li>Fix a rare issue that particular NVMe drive model state changes to Unusable with drive hotplug</li>
	<li>Fix a rare issue that SED may fail to reprovision if the drive is removed during import and controller reset</li>
	<li>Fix a potential controller fault triggered by IO counter mismatches during overlapping FLR (Function Level Reset) and task management operations</li>
	<li>Fix a rare issue that firmware fault may occur if a drive takes too long (over 70s) to fix errors, especially during task management</li>
	<li>Fix a potential issue that alternative boot chain recovery fails to trigger if secure boot authentication has failed</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00157381en_us Advisory: HPE MR932i-p Storage Controller - Incorrect Controller Port Number To Box Number Mapping in iLO GUI</li>
	<li>Fix a00157199en_us Advisory: HPE MR932i-p Storage Controller - The &quot;StorageDevice.1.2.BatteryOK&quot; Event Is Not Consistently Generated When the Energy Pack Is Reconnected to an HPE MR932i-p Storage Controller</li>
	<li>Fix a00157775en_us Advisory: HPE MR932i-p Storage Controller - Cache-Offload Event Is Not Reported in the Integrated Management Log (IML) Via Redfish</li>
	<li>Fix an issue that backplane firmware update fails if more than 16 slots are connected to the MR932i-p controller.</li>
	<li>Fix an issue that Redfish POST ResetToDefaults.PreserveVolumes operation fails with Unsupported Operation.</li>
	<li>Fix an issue that &quot;Controller status changes to failed&quot; event is generated when doing firmware update. Please note the event may still happen when downgrading firmware to 8.15.1.0-01003-00001 since the fix is not available in the old version</li>
	<li>Fix an issue that DriveOffline and DriveOfflineCleared events are logged when auto rebuild start on the re-inserted drive</li>
	<li>Fix an issue that Energy Pack temperature sensor thresholds are reported incorrectly</li>
	<li>Fix an issue that SCSI Device ModeSense failures with format corruption warnings on ESXI9.0 OS after boot</li>
	<li>Fix an issue that firmware may not identify the drive properly to puncture when more than one rebuild/copyback tasks running.</li>
	<li>Fix a rare issue that controller is stuck at DDR SPD i2c read during reboot test</li>
	<li>Fix a rare issue that controller may hang in cache offload module after factory repurpose command issued followed by a power cycle</li>
	<li>Fix an issue that arbitrary firmware image size value used in platform measurement when reading data</li>
	<li>Fix a rare issue that drives might be marked as failed with phy toggling after creating volume.</li>
	<li>Fix a rare issue that Energy Pack communication fail does not reflect, and causes cache offload failed</li>
	<li>Fix a rare issue that firmware hang caused by the NAND flash hardware entering a bad state after a program failure while doing factory repurpose</li>
	<li>Fix an issue that changing LKM to EKM encryption mode using Redfish fails</li>
	<li>Fix an issue that controller status shows &quot;Need Attention&quot; in RBSU menu when drives are connected to controller</li>
	<li>Fix an issue that auto assignment is not applied on the auto-configured JBOD in a fresh boot.</li>
	<li>Remove &ldquo;Encrypted@Redfish.AllowableValues&quot; to match Boolean type behavior</li>
	<li>Fix an issue that controller firmware fault might be observed when partial-capacity volumes are assigned to different physical functions and moved to Offline.</li>
	<li>Fix a rare case that controller may fault when the foreign drive&#39;s primary DDF record is invalid</li>
	<li>Fix a potential controller fault triggered by frequent drive medium errors during Online Capacity Expansion</li>
	<li>Fix a rare issue that particular NVMe drive model state changes to Unusable with drive hotplug</li>
	<li>Fix a rare issue that SED may fail to reprovision if the drive is removed during import and controller reset</li>
	<li>Fix a potential controller fault triggered by IO counter mismatches during overlapping FLR (Function Level Reset) and task management operations</li>
	<li>Fix a rare issue that firmware fault may occur if a drive takes too long (over 70s) to fix errors, especially during task management</li>
	<li>Fix a potential issue that alternative boot chain recovery fails to trigger if secure boot authentication has failed</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2522b2b7c798433d9256ae5329bc884d" version="a9cc9b5abc834d9da562fa62a13ca4ce" lucid_version="Gen12_StorCLI_AV2.win@8.16.0.11__sc-windows_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="8.16.0.11" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 RC1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 RC1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.15.0.11" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="049ca173304042ae9feccac41164d4f3" version="d8e17ba042bf4a7dbd973dd233f57e0b" lucid_version="matrox.G200eH5.win2025.x64@9.15.1.271(E)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="9.15.1.271" revision="E" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="9.15.1.271 (D)" revision="D" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported&nbsp;environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported&nbsp;environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b8bfd68496a643cdaece510776fb4ad2" version="3119d5cadfcc43c7ad4f3bffb49d7fa9" lucid_version="broadcom_nxe.w2k22@235.1.122.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="235.1.122.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances the Windows driver to support PCIe compliance configuration by enabling pass-through firmware commands with long input message sizes.</li>
	<li>This product enhances adding new event log warning message.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances the Windows driver to support PCIe compliance configuration by enabling pass-through firmware commands with long input message sizes.</li>
	<li>This product enhances adding new event log warning message.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="233.0.148.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances to improve user mode RDMA abortive cleanup.</li>
	<li>This product enhances FW logging to host to work across device reset.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances to improve user mode RDMA abortive cleanup.</li>
	<li>This product enhances FW logging to host to work across device reset.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes issue where packet drops is seen when jumbo frame is enabled.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes issue where packet drops is seen when jumbo frame is enabled.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f907a07a90884dc7b70bfe96abed1e23" version="6db42c3af36b4bdebb1e3fe4f789c401" lucid_version="FWPKG-P45641-H24@28.48.1000__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="28.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong> When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong> When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ff59337dd3ff4f44928eba3219e493a5" version="46c24384109040aea7a6064e47696122" lucid_version="FWPKG_VK000960KYDPT_VK001920KYDPU_VK003840KYDPV@HPK6__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW release modifies drive&#39;s behavior from &quot;returning error&quot; to &quot;silently discard&quot; if a request is received by drive from the host during FLR.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW release modifies drive&#39;s behavior from &quot;returning error&quot; to &quot;silently discard&quot; if a request is received by drive from the host during FLR.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK5" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW update contains the fix for false ILO message of temporary drive &quot;degraded&quot; status.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW update contains the fix for false ILO message of temporary drive &quot;degraded&quot; status.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2c18773ff76b45029d6e287070cf21ae" version="b629bc47f6bc40718c09b25e14853c30" lucid_version="UBM11_FWPKG@1.04__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.04" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Remove the 0xC2 address to allow iLO to handle the MCTP discovery workaround.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Remove the 0xC2 address to allow iLO to handle the MCTP discovery workaround.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="82fd00d58ad545188ccd0ab41b66633b" version="05971723b4464e358a81d2c05d275d48" lucid_version="FWPKG-P45641-B23@28.48.1000-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="28.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="28.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="29a000381a7c4ec8a72063a155821a0a" version="9771c6a4d4534bf7be368c5507723b07" lucid_version="ice.sles15@2.4.5-1-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.4.5-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.4.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7cb9f47fb1de402da9399ef94a8426a5" version="6927e5439b7746e3bda2359045abc5bb" lucid_version="FWPKG_MB006000JWZVQ_MB008000JWZVR@HPD3(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions..</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions..</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1b8e2109d79c4e8981f5e56d6ed20102" version="aa92fa9c5ac34fd18dc35669ec196e2a" lucid_version="emulex_storport_x64.w2k22_rt_gen12@14.4.624.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.624.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.624.0</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.624.0</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.393.20" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.393.20</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.393.20</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="77057f17d85c42018e33e3454cf6ece5" version="602639d355fd43f18b42a7d4d7693567" lucid_version="mlnx_OFED_Driver@25.4.50020.0(d)__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="25.4.50020.0" revision="d" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version 25.4.50020.0</p>

<p>Added Azure local 24H2 support</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version 25.4.50020.0</p>

<p>Added Azure local 24H2 support</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Installer Digital signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Installer Digital signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.4.50020.0 (c)" revision="c" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version 25.4.50020.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version 25.4.50020.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Installer Digital signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Installer Digital signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c94878ce1a3442eca368e62460770912" version="a4baff443cfe4f1fb1bd88340daf8418" lucid_version="bnxt_roce.rhel10u0@235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="39676e9bd8d74e11b8837e3f6ebabd5c" version="50cd52f793c142a59934e609300224e8" lucid_version="ssa.linux.x64@6.60.8.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>RC drop 6.60.8.0.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>RC drop 6.60.8.0.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.50.11.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="49ba1819ef2342f6bfa838b14f08b28e" version="1213ae8fe5a64d9ba2702648dccd1a89" lucid_version="qla2xxx.rhel10.x86_64_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="75ec3f6c44d740a990fdc3e7ad94aab7" version="2daf3958afc7404d9fecce001950fabf" lucid_version="sierraforest-graniterapids.win.x64@10.1.19928.8615(G)__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.1.19928.8615" revision="G" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated installer library to detect reboot flag.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated installer library to detect reboot flag.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="10.1.19928.8615 (F)" revision="F" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated installer library to detect reboot flag.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated installer library to detect reboot flag.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a5b53b4bfa36450dafe72d3912e27c73" version="97b039db4584420b85bdb193c2effa00" lucid_version="ice.rhel9@2.4.5-1-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.4.5-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 9.7</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 9.7</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.4.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 9.7</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 9.7</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6e4df08455db4ce3a3b07b6eecea6280" version="0b525994e9d040ab8968ba959bb37602" lucid_version="amsd_rhel9@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.6.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="799a5476ba934d049a4150e04e75c398" version="598a471de19b4292a91b0bdd450b8133" lucid_version="FWPKG_MB002000GYDNK_MB004000GYDPD@HPG4__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for FIPS code release and one assert fix</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for FIPS code release and one assert fix</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG2" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>1.Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.<br />
2. Adding other logging and FW enhancements.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>1.Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.<br />
2. Adding other logging and FW enhancements.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d0bba068f7ca4e978bcc6d2bf9e8abf7" version="83ab6972351c42d3b0ce1fc4cf3585d6" lucid_version="FWPKG_MB12000JYESN_MB16000JYEVC_MB20000JYEVD@HPD3__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RPM data missing from iLO GUI</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RPM data missing from iLO GUI</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW fix on assert, time-out, error log several fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW fix on assert, time-out, error log several fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD1 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="188764648e874fd98523f669c6e5a042" version="bb3447a059d64fbba936fb336cf6f42c" lucid_version="intel_cvl.w2k22@1.20.39.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.20.39.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.18.71.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhanced traffic flow in queue map rebalance.</li>
	<li>This product enhanced &nbsp;media type detection over PHY logic.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhanced traffic flow in queue map rebalance.</li>
	<li>This product enhanced &nbsp;media type detection over PHY logic.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed the system event logging.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed the system event logging.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8e8482d9e6e6494a8e54ec40143d190a" version="556f22f571aa44958d24b4b56cbc3bf3" lucid_version="tg3.sles15@3.139w-2__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="3.139w-2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="3.139t-2" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes issue where link disconnected with the latest Out-of-Box (OOB) Driver.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes issue where link disconnected with the latest Out-of-Box (OOB) Driver.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="953a26b89c654d5fa1a3dc9dc11d72aa" version="abad6ea88132481db02691f5f8854cd0" lucid_version="FWPKG_MB008000JWWQP_MB006000JWWQN@HPD8__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD8" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b50552ebf09d445294b0b81e162643cf" version="ba7d8ce8c9444440b2fabed4f0887ce2" lucid_version="FWPKG-P42044-B21@26.48.1000__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="26.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 26.48.1000:</strong></p>

<ul>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 26.48.1000:</strong></p>

<ul>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.48.1000:</strong></p>

<ul>
	<li>An issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.48.1000:</strong></p>

<ul>
	<li>An issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="26.46.3048" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version&nbsp;26.46.3048:</strong></p>

<ul>
	<li>Added support for RSS with crypto offload enabling the NIC to parallelize packet processing across CPU cores while performing encryption/decryption in hardware. Additionally, introduced a new l4_type_ext parameter with values: 0 (None), 1 (TCP), 2 (UDP), 3 (ICMP).</li>
	<li>Added an extra validation for the payload_len field in incoming NC-SI messages. Previously, invalid packets might have been accepted; now, such packets are silently dropped.</li>
	<li>This release contains important reliability improvements and security hardening enhancements. HPE recommends upgrading your devices firmware to this release to improve the devices&rsquo; firmware security and reliability.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version&nbsp;26.46.3048:</strong></p>

<ul>
	<li>Added support for RSS with crypto offload enabling the NIC to parallelize packet processing across CPU cores while performing encryption/decryption in hardware. Additionally, introduced a new l4_type_ext parameter with values: 0 (None), 1 (TCP), 2 (UDP), 3 (ICMP).</li>
	<li>Added an extra validation for the payload_len field in incoming NC-SI messages. Previously, invalid packets might have been accepted; now, such packets are silently dropped.</li>
	<li>This release contains important reliability improvements and security hardening enhancements. HPE recommends upgrading your devices firmware to this release to improve the devices&rsquo; firmware security and reliability.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.46.3048:</strong></p>

<ul>
	<li>Configuring a small MTU led to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discarded these packets, causing the PXE boot to fail.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.46.3048:</strong></p>

<ul>
	<li>Configuring a small MTU led to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discarded these packets, causing the PXE boot to fail.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0ae09abcdcdd47d48ae1261f18aaa796" version="4b7cd4d82ffd4a73bab95a207f74c098" lucid_version="FWPKG_VV003840KXWBF_VV007680KXWBL_VV015360KXWBN@HPK8__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK8" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPK8 is a planned maintenance release that follows HPK5. This is a recommended FW release that provides bug fixes for the P5430 15.36T, 7.68T, 3.84T (4K IU) Solid State Drives.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPK8 is a planned maintenance release that follows HPK5. This is a recommended FW release that provides bug fixes for the P5430 15.36T, 7.68T, 3.84T (4K IU) Solid State Drives.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK5" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPK5 is a planned maintenance release that follows HPK2. This is a recommended FW release that provides bug fixes for the&nbsp; 4K IU Solid State Drives.</li>
	<li>Noted this FW change require a system power cycle after installation for it to take effect.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPK5 is a planned maintenance release that follows HPK2. This is a recommended FW release that provides bug fixes for the&nbsp; 4K IU Solid State Drives.</li>
	<li>Noted this FW change require a system power cycle after installation for it to take effect.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a1223957986d460eb877211bd19bf881" version="acee0f9fcf0e4d91891bd91a5388d820" lucid_version="FWPKG_MB001000GWJAN_MB002000GWFWA_MB004000GWFWB@HPG1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPG1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fd79732b69c747a4ba4278e32ef12a49" version="299e3fe8b55e4a29be6501b2933e902a" lucid_version="broadcom_nxe.w2k25@235.1.122.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="235.1.122.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances the Windows driver to support PCIe compliance configuration by enabling pass-through firmware commands with long input message sizes.</li>
	<li>This product enhances adding new event log warning message.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances the Windows driver to support PCIe compliance configuration by enabling pass-through firmware commands with long input message sizes.</li>
	<li>This product enhances adding new event log warning message.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="233.0.148.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances to improve user mode RDMA abortive cleanup.</li>
	<li>This product enhances FW logging to host to work across device reset.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhances to improve user mode RDMA abortive cleanup.</li>
	<li>This product enhances FW logging to host to work across device reset.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes issue where BSOD (Blue Screen of Death) occurs when install Windows Server 2025 OS on ISCSI LUN.</li>
	<li>This product fixes issue where packet drops is seen when jumbo frame is enabled.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes issue where BSOD (Blue Screen of Death) occurs when install Windows Server 2025 OS on ISCSI LUN.</li>
	<li>This product fixes issue where packet drops is seen when jumbo frame is enabled.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3d4b3948a2e7454589365f36eee4d988" version="3f52ab4febe74549a2c97fc625b32d8c" lucid_version="FWPKG_VR000480KXLXF@HPK4-rev2__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW update contains the fix for false ILO message of temporary drive &quot;degraded&quot; status.</li>
	<li>After the FW update, if the latest drive FW version is not correctly reflected in iLO under the scenarios outlined below, a system reboot or iLO reset may be required.
	<ul style="list-style-type:circle">
		<li>HPK2 -&gt; HPK4 (or later version)</li>
		<li>HPK3 -&gt; HPK4 (or later version)</li>
	</ul>
	</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW update contains the fix for false ILO message of temporary drive &quot;degraded&quot; status.</li>
	<li>After the FW update, if the latest drive FW version is not correctly reflected in iLO under the scenarios outlined below, a system reboot or iLO reset may be required.
	<ul style="list-style-type:circle">
		<li>HPK2 -&gt; HPK4 (or later version)</li>
		<li>HPK3 -&gt; HPK4 (or later version)</li>
	</ul>
	</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW update contains the fix for false ILO message of temporary drive &quot;degraded&quot; status.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This FW update contains the fix for false ILO message of temporary drive &quot;degraded&quot; status.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="e9a39e503f934c9b9e368c25f2781cd9" version="6b3b127aee524ccf9d4fd905297fa967" lucid_version="FWPKG-P79114-H21@40.48.1000-rev3__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="40.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="40.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6e47868a4c52411285405d34ddf4456a" version="f7850debc2b6433e8f6bf8acee218095" lucid_version="Gen10P_Gen11_MR_Controller.sles16.x86_64.rpm@07.736.04.00-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="07.736.04.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="07.736.04.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="923bb6bba3254a6d80257c1bf056f39d" version="a8fa943c5e2c47098e12c288641108f2" lucid_version="UBM6_FWPKG@1.06(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.06" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Update proudction name</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Update proudction name</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.06" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Disable UBM long reset</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Disable UBM long reset</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7a0e2103ab3d449ea173c873ce94c871" version="b655bf12f1ec45248db5262428b859da" lucid_version="ssaducli.linux.x64@6.60.8.0__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>RC drop 6.60.8.0.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>RC drop 6.60.8.0.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.50.11.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
	<li>Fixed an issue where the last failure reason was not listing on physical drives.&nbsp;</li>
	<li>Fixed an issue where SSAScripting failed to create an encrypted volume while in express local mode.&nbsp;</li>
	<li>Fixed an issue where an error/warning message was not being generated correctly while expanding a RAID 1+0 volume.&nbsp;</li>
	<li>Fixed an issue where a duplicate entry for the physical drive was displayed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
	<li>Fixed an issue where the last failure reason was not listing on physical drives.&nbsp;</li>
	<li>Fixed an issue where SSAScripting failed to create an encrypted volume while in express local mode.&nbsp;</li>
	<li>Fixed an issue where an error/warning message was not being generated correctly while expanding a RAID 1+0 volume.&nbsp;</li>
	<li>Fixed an issue where a duplicate entry for the physical drive was displayed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3ab4de78da484144892d6ddcd8fd9b97" version="55170dbd6ff54dc09aa6e5397965262c" lucid_version="ixgbe.sles15@6.3.4-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.3.4-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.2.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added PHY-based PTP for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added PHY-based PTP for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed Intel E610 OCP Firmware OROM version display in Linux environment.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed Intel E610 OCP Firmware OROM version display in Linux environment.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a2de689e83194577b466d6bba414e984" version="2d86498422a741f9af9b9013b6f31dec" lucid_version="Gen12_MR_Controller_AV2.rhel10.x86_64.rpm@8.16.1.0.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="8.16.1.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 GCA</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 GCA</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.15.1.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="575b91de95af482eb3a08ed94402e2c3" version="dcecd48f644944afa9df234dfe1d0fe8" lucid_version="FWPKG_MB24000GYEVK@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW fix on assert, time-out, error log several fixes.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW fix on assert, time-out, error log several fixes.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>FW assert fix and other regular maintenance release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>FW assert fix and other regular maintenance release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0134d053d49b43b1add04e5a51f6ff18" version="47516fe2805f4e9ab3bc3e01fb96aba6" lucid_version="nicfwpkg_intel_e810_xxv2@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7d1726c966b744859b8999f1d5c61622" version="eb2f5ba888cc487c817d6b72b1bd37de" lucid_version="Gen12_MR_Controller_AV2.win2022@8.16.4.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="8.16.4.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 (AV2 PR2 RC1)</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 (AV2 PR2 RC1)</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.15.7.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2c6711088bca48d8a5963e48aa925230" version="29e6ae4ce2094dd1b0051446fb4ad807" lucid_version="nicfwpkg_bcm_bcm5719ocp@20.35.41-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="20.35.41" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="20.35.41" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where unique serial number in VPD (Vital Product Data) will be altered to a dummy serial number</li>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where unique serial number in VPD (Vital Product Data) will be altered to a dummy serial number</li>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6ac4c1fb52734dc69d27fd9966ff92b4" version="d7bbe445fa974deea9403874ffbe832e" lucid_version="ixgben.vmware80@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSpp2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSpp2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.11.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8927cfd49bdd4662a4005f15b8eb6847" version="40bbed5bc9b4407e9f9fe2ae77e30982" lucid_version="ubuntu2604amsd@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="39cff1d9c55641a8a5495e9c755fc456" version="d756031e46334c08a77fc0049d523b08" lucid_version="FWPKG_MO001600PZWSH_MO003200PZWSK@HPD4-rev1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPD4" revision="" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us" style="color:#467886; text-decoration:underline">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us" style="color:#467886; text-decoration:underline">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD4" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us" style="color:#467886; text-decoration:underline">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>&nbsp;which will be active on 18-Aug-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us" style="color:#467886; text-decoration:underline">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>&nbsp;which will be active on 18-Aug-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="e0d3905a13b74f06a63b96091e3a0b13" version="0be86abeb599456ea5c1845fc69ef581" lucid_version="FWPKG_MB006000GYDNL_MB008000GYDPE_MB010000GYDNN@HPG4__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for FIPS code release and one assert fix</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for FIPS code release and one assert fix</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG2" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>1) Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.<br />
2) Adding other logging and FW enhancements.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>1) Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.<br />
2) Adding other logging and FW enhancements.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="acccc3a79b934a56bc23c6e1a1b8169b" version="9f078413ab6e4fb6aeab7cecca2f01a6" lucid_version="FWPKG_VO000960RZWUP_VO000960RZWUQ_VO001920RZWUR@HPD1(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD1" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This fix is for unrecovered errors may occur on the targeted Blocks of Wear-leveling process when host issues Read command.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This fix is for unrecovered errors may occur on the targeted Blocks of Wear-leveling process when host issues Read command.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6792e601e784404b8b27e1297a68223e" version="02859ac29430461593ee92cdbde4dc9b" lucid_version="FWPKG_MK000480GXNXB_MK000960GXNZK_MK001920GXNZL@HPG1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improve FW handling on capacitor charge timeout mechanism</li>
	<li>Change the sense code during download microcode (0E)</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improve FW handling on capacitor charge timeout mechanism</li>
	<li>Change the sense code during download microcode (0E)</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This is initial release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This is initial release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a6830ae5a0164a2791c4b777337e9547" version="d8d576b5c7a64fa483768cbcde70dc97" lucid_version="FWPKG-P65333-B21@28.48.1000-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="28.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="28.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="37b6e65ded4e403daf3c081820ceaac6" version="b4015d65270c4f34b6c284001b42c845" lucid_version="nicfwpkg_intel_e610_it4ocp@1.40__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.40" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.30" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed RDE PATCH for WakeOnLANEnabled property.</li>
	<li>This product fixed Firmware OROM version display in VMware ESXi environment.</li>
	<li>This product fixed Firmware OROM version display in Linux environment.</li>
	<li>This product fixed NVM Version display with double digits under NIC Configuration in HPE RBSU menu.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed RDE PATCH for WakeOnLANEnabled property.</li>
	<li>This product fixed Firmware OROM version display in VMware ESXi environment.</li>
	<li>This product fixed Firmware OROM version display in Linux environment.</li>
	<li>This product fixed NVM Version display with double digits under NIC Configuration in HPE RBSU menu.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="170904304ebe46f7b8e03ed332702548" version="c44fa072ec034868932c66d0a84c6661" lucid_version="U72.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="43699ba116594728bcf30612b7c6f5f5" version="25de805a4fb64ddbb381a6e1259c2315" lucid_version="nicfwpkg_bcme_57504_4p25@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a4dfe483f7df4c3993a498bb13f08613" version="f16d6604fc9649d4b2bfea072a3bc652" lucid_version="nicfwpkg_bcme_57414_2p25ocp@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="41fa8420de8d497db38df0b5cd7ea429" version="7656525f40b04d9fb5c50bf0a8729b0a" lucid_version="ubuntu2204amsd@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.6.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="72ea764b3e854ca0a2685dc47421a4a8" version="c5e17f1865ec4cffba2ba7f67b76daa3" lucid_version="U68.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected” in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration” error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected” in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration” error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9f3475ef292446178bcd5370d0abfc12" version="0b72bc8e7d1442dab4e534876f658b6d" lucid_version="qla2xxx.sles15.x86_64_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="10.02.14.00-k1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>SuSE Linux Enterprise Server 15.7</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>SuSE Linux Enterprise Server 15.7</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fb411db299064ad3bfef436571766340" version="a9fd18aeeb554ea68841e5f02dbf9154" lucid_version="Gen12_MR_Controller_AV2.rhel9.x86_64.rpm@8.16.1.0.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="8.16.1.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 GCA</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 GCA</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.15.1.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b902adf94cea4a0abb9a86aae94c9318" version="b3ac2dd86a7d4e9aa3340410288c5fcb" lucid_version="FWPKG_MO000800KXPRV_MO001600KXPTR@HPK2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code improvements for CAP.TO and LED behavior.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code improvements for CAP.TO and LED behavior.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>&nbsp;This is an initial FW.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>&nbsp;This is an initial FW.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1d4bdf01ac864288af51e73784711598" version="3ec471e24dfc409bb3e1c84690e8ac7d" lucid_version="mlnx_en_roce_mlx5.rhel10.x86_64.rpm@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.07-0.9.7.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="27053985f2354572a6633cc6a63bb7ef" version="44ffce87ed0447a39042c477864b4c57" lucid_version="FWPKG-P42041-B21@26.48.1000__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="26.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 26.48.1000:</strong></p>

<ul>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 26.48.1000:</strong></p>

<ul>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.48.1000:</strong></p>

<ul>
	<li>An issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.48.1000:</strong></p>

<ul>
	<li>An issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="26.46.3048" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version&nbsp;26.46.3048:</strong></p>

<ul>
	<li>Added support for RSS with crypto offload enabling the NIC to parallelize packet processing across CPU cores while performing encryption/decryption in hardware. Additionally, introduced a new l4_type_ext parameter with values: 0 (None), 1 (TCP), 2 (UDP), 3 (ICMP).</li>
	<li>Added an extra validation for the payload_len field in incoming NC-SI messages. Previously, invalid packets might have been accepted; now, such packets are silently dropped.</li>
	<li>This release contains important reliability improvements and security hardening enhancements. HPE recommends upgrading your devices firmware to this release to improve the devices&rsquo; firmware security and reliability.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version&nbsp;26.46.3048:</strong></p>

<ul>
	<li>Added support for RSS with crypto offload enabling the NIC to parallelize packet processing across CPU cores while performing encryption/decryption in hardware. Additionally, introduced a new l4_type_ext parameter with values: 0 (None), 1 (TCP), 2 (UDP), 3 (ICMP).</li>
	<li>Added an extra validation for the payload_len field in incoming NC-SI messages. Previously, invalid packets might have been accepted; now, such packets are silently dropped.</li>
	<li>This release contains important reliability improvements and security hardening enhancements. HPE recommends upgrading your devices firmware to this release to improve the devices&rsquo; firmware security and reliability.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.46.3048:</strong></p>

<ul>
	<li>Configuring a small MTU led to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discarded these packets, causing the PXE boot to fail.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.46.3048:</strong></p>

<ul>
	<li>Configuring a small MTU led to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discarded these packets, causing the PXE boot to fail.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ec20938f2dbe43099ae9347f73dc19f7" version="778bc34e162746eba64a0f912c77f4d4" lucid_version="mlnx_en_roce_mlx5.rhel10u1x86_64.rpm@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="66cb80b1d5d040ff8edbcf313b0e2f9d" version="cb947df2b7494b02a1ae11bb036e5d53" lucid_version="FWPKG_MB004000JWZVU@HPD3(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>

<p>&nbsp;</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>

<p>&nbsp;</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="df57af7543b34ffbb722ca05255bf445" version="bc8e3b1eb8804b47acb76ad46bb94011" lucid_version="UBM3_FWPKG@1.24(G)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.24" revision="G" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Support new Gen12 servers.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Support new Gen12 servers.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.24 (F)" revision="F" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Support new ML110 and DL560 Gen11 servers</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Support new ML110 and DL560 Gen11 servers</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6d4e51e8b4c040cc80275ae447831403" version="025dcd5ad1234463a055d4da8b53f5fe" lucid_version="Gen10P_Gen11_StorCLI.win@7.3604.0.0__sc-windows_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="7.3604.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="7.3212.0.0 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>
	<p>Fix windows tool cert expire issue.</p>
	</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>
	<p>Fix windows tool cert expire issue.</p>
	</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="aa57601c0db347e68c835baf96f72938" version="39e78da9fa98457683e5343e1131981f" lucid_version="HPE_MR408i-o_Gen11@52.36.3-6584__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="52.36.3-6584" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="52.32.3-6333" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="614a0c688deb4def90dafbe34fab64bb" version="2ddbb9895d1240bd95290044d55545dd" lucid_version="smartpqi.esxi8.0_bundle@2026.01.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.01.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.10.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed PSOD indicates a divide-by-zero happened.&nbsp;</li>
	<li>Fixed an issue where the driver&#39;s controller structure field was too small for the full ASCII firmware version.&nbsp;</li>
	<li>Fixed an issue where a message from a periodic check on the controller heartbeat appeared as a&nbsp;system error instead of an informational message.&nbsp;</li>
	<li>Fixed an issue where firmware versioning information was incorrect or blank on some of the controllers.&nbsp;</li>
	<li>Fixed an issue where in a specific scenario, the device removal handler attempts to remove a device that has already been removed by the normal device discovery flow.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed PSOD indicates a divide-by-zero happened.&nbsp;</li>
	<li>Fixed an issue where the driver&#39;s controller structure field was too small for the full ASCII firmware version.&nbsp;</li>
	<li>Fixed an issue where a message from a periodic check on the controller heartbeat appeared as a&nbsp;system error instead of an informational message.&nbsp;</li>
	<li>Fixed an issue where firmware versioning information was incorrect or blank on some of the controllers.&nbsp;</li>
	<li>Fixed an issue where in a specific scenario, the device removal handler attempts to remove a device that has already been removed by the normal device discovery flow.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d5dd0878f5bc46a1b2bda19d450bbffe" version="773c466c982042fea8769d7ddbc070dd" lucid_version="FWPKG_MO001600PXMTN_MO003200PXMTV_MO006400PXMUA@HPD4__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPD4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>To fix 1) chip kill -The host IO CMD may get timed out and shows SNS=04/40/C2 and 2) garbage collection checking for performance recovery.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>To fix 1) chip kill -The host IO CMD may get timed out and shows SNS=04/40/C2 and 2) garbage collection checking for performance recovery.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD3" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Added fix to address a rare case where drive health queries can trigger false drive predictive failure.</li>
	<li>For more information, refer to HPE Customer Advisory at the following URL: <a href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us" id="menur2cjc" rel="noreferrer noopener" target="_blank" title="https://support.hpe.com/hpesc/public/docdisplay?docid=emr_na-a00146367en_us">https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us</a> which will be active on 20-Mar-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Added fix to address a rare case where drive health queries can trigger false drive predictive failure.</li>
	<li>For more information, refer to HPE Customer Advisory at the following URL: <a href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us" id="menur2cjc" rel="noreferrer noopener" target="_blank" title="https://support.hpe.com/hpesc/public/docdisplay?docid=emr_na-a00146367en_us">https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us</a> which will be active on 20-Mar-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="da9ff49af6c74b6d969bca700eb095c0" version="661b77094d7a4165ba8b290b69494735" lucid_version="ixgbe.rhel10@6.3.4-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.3.4-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.2.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added PHY-based PTP for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added PHY-based PTP for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed Intel E610 OCP Firmware OROM version display in Linux environment.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed Intel E610 OCP Firmware OROM version display in Linux environment.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b128d4dc8ad141c48e822f1c86fe722d" version="e839c64e139945bbb3b30883a5ed4407" lucid_version="qla2xxx.driver.esx91.zip_rt_gen12@2026.03.01-rev1__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 91.5.5.86.0<br />
This driver is only supported on VMware ESXi 9.1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 91.5.5.86.0<br />
This driver is only supported on VMware ESXi 9.1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 91.5.5.86.0<br />
This driver is only supported on VMware ESXi 9.1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 91.5.5.86.0<br />
This driver is only supported on VMware ESXi 9.1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a07f8ac11b4a440d99aa61ea5fb0b63f" version="2726ab012ef34fed81d4afe7df3657cd" lucid_version="bnxtnet.vmware80@2025.11.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2025.11.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.05.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where ESXi Datastore not seen when NPAR is enabled.</li>
	<li>This product fixes the issue where PSOD is seen when enable NPAR using 2 NICs.</li>
</ul>

<p>&nbsp;</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where ESXi Datastore not seen when NPAR is enabled.</li>
	<li>This product fixes the issue where PSOD is seen when enable NPAR using 2 NICs.</li>
</ul>

<p>&nbsp;</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="cb50e456662942af91a87d5e0217de4b" version="8e4ccb088185475e806dfe7a5adbf4a7" lucid_version="intel_lkv.w2k22@1.6.25.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.6.25.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.4.73.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="adefe97a484140f28ccdb1e9dfb3903c" version="3b50c8b0a8594143bd43ac3e1ddeb4c5" lucid_version="icen.vmware90@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.11.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product VMware ESXi 9 supported.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product VMware ESXi 9 supported.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3f9b8c29a79d478ca9fefec4fcc3cff7" version="06e5033b3e714cbba795f155f6a2fc0a" lucid_version="Gen12_Storcli-sut_AV2.esxi90@2026.04.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.04.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 RC1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 AV2 PR2 RC1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ce8b7e2d14a74bb5815bd807cefd3dc0" version="2114c4e00055457fb7cee59ed6609fc3" lucid_version="A66.fwpkg@1.50_03-06-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.50_03-06-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0.A for AMD 5th Generation EPYC processors.</p><p>Enhanced Asset Tag functionality to support up to 64 bytes.</p><p>Added support for ASIX USB to Ethernet adapter driver version 3.3.2, resolving PXE boot stability issues with ASIX AX88179A chipset adapters and eliminating system reboot loops during PXE operations.</p><p>Improved device name display for storage controllers and other devices in Japanese language mode. </p><p></p><p>Added PCIe prefetchable MMIO support and its default setting is Disabled . When enabled, the system will allocate both prefetchable and non-prefetchable MMIO resources for PCIe devices. This feature can also be controlled via Redfish at: /redfish/v1/systems/1/bios/oem/hpe/service/settings/PciPrefetchableMMIO</p><p>Note: With the prefetchable MMIO option enabled, downgrading to previous BIOS versions may cause the system to hang or reboot continuously. Users must disable the prefetchable MMIO option before downgrading. If the system becomes unstable after a downgrade, restore Manufacturing Defaults to recover.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0.A for AMD 5th Generation EPYC processors.</p><p>Enhanced Asset Tag functionality to support up to 64 bytes.</p><p>Added support for ASIX USB to Ethernet adapter driver version 3.3.2, resolving PXE boot stability issues with ASIX AX88179A chipset adapters and eliminating system reboot loops during PXE operations.</p><p>Improved device name display for storage controllers and other devices in Japanese language mode. </p><p></p><p>Added PCIe prefetchable MMIO support and its default setting is Disabled . When enabled, the system will allocate both prefetchable and non-prefetchable MMIO resources for PCIe devices. This feature can also be controlled via Redfish at: /redfish/v1/systems/1/bios/oem/hpe/service/settings/PciPrefetchableMMIO</p><p>Note: With the prefetchable MMIO option enabled, downgrading to previous BIOS versions may cause the system to hang or reboot continuously. Users must disable the prefetchable MMIO option before downgrading. If the system becomes unstable after a downgrade, restore Manufacturing Defaults to recover.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0A for AMD 5th Generation EPYC processors.

This revision of the System ROM includes mitigations for CVE-2026-22796 and CVE-2024-38798 security vulnerabilities.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed a time zone configuration issue causing "266 - Non-Volatile Memory Corruption Detected" loop when BIOS timezone was "Unspecified" and Windows time synchronization was enabled.</p><p>Fixed Asset Tag protection lock for 64-byte Asset Tags. </p><p>Fixed an issue where C1 and C6 state settings were not properly applied</p><p>Updated RBSU power management help text for DF P-states to remove unsupported "P3" entry for AMD platforms.</p><p>Corrected network device name display in Embedded UEFI Shell.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0A for AMD 5th Generation EPYC processors.

This revision of the System ROM includes mitigations for CVE-2026-22796 and CVE-2024-38798 security vulnerabilities.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed a time zone configuration issue causing "266 - Non-Volatile Memory Corruption Detected" loop when BIOS timezone was "Unspecified" and Windows time synchronization was enabled.</p><p>Fixed Asset Tag protection lock for 64-byte Asset Tags. </p><p>Fixed an issue where C1 and C6 state settings were not properly applied</p><p>Updated RBSU power management help text for DF P-states to remove unsupported "P3" entry for AMD platforms.</p><p>Corrected network device name display in Embedded UEFI Shell.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.40_01-09-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0.9 for AMD 5th Generation EPYC processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0.9 for AMD 5th Generation EPYC processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p><p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0.9 for AMD 5th Generation EPYC processors.</p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
</p><p><strong>Firmware Dependencies:</strong></p><p>None</p><p><strong>Problems Fixed:</strong></p><p>Addressed an issue where reverting an Opal drive to factory default using PSID after previously selecting it in the "Encrypted Devices" menu caused an error when navigating back to "Encrypted Devices."</p><p>Addressed an issue where, after an AC cycle with Secure Boot enabled, the SecureBootCurrentBoot setting became disabled, causing the iLO web interface to incorrectly display Secure Boot as disabled.</p><p>Addressed an issue where boot time was not consistently reported to boot progress in all states. </p><p>Addressed an issue where changes made in the RBSU were not persisting when using OpenBMC.</p><p>Addressed an issue where the RBSU menu displayed an option to log in using iLO credentials even when OpenBMC was detected. </p><p>Addressed an issue where the virtual USB device name was incorrectly shown as "iLO Virtual USB" instead of "BMC Virtual USB" when OpenBMC was detected.</p><p><strong>Known Issues:</strong></p><p>None</p>]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p><p>This revision of the System ROM includes AMD reference code TurinPI 1.0.0.9 for AMD 5th Generation EPYC processors.</p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
</p><p><strong>Firmware Dependencies:</strong></p><p>None</p><p><strong>Problems Fixed:</strong></p><p>Addressed an issue where reverting an Opal drive to factory default using PSID after previously selecting it in the "Encrypted Devices" menu caused an error when navigating back to "Encrypted Devices."</p><p>Addressed an issue where, after an AC cycle with Secure Boot enabled, the SecureBootCurrentBoot setting became disabled, causing the iLO web interface to incorrectly display Secure Boot as disabled.</p><p>Addressed an issue where boot time was not consistently reported to boot progress in all states. </p><p>Addressed an issue where changes made in the RBSU were not persisting when using OpenBMC.</p><p>Addressed an issue where the RBSU menu displayed an option to log in using iLO credentials even when OpenBMC was detected. </p><p>Addressed an issue where the virtual USB device name was incorrectly shown as "iLO Virtual USB" instead of "BMC Virtual USB" when OpenBMC was detected.</p><p><strong>Known Issues:</strong></p><p>None</p>]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3924ecdb619749ea97fc87aad33f7ca6" version="f90813d1eebe42b7b6d997f18f8d03ca" lucid_version="FWPKG_MB002000JYDNE_MB004000JYDPB@HPD6__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for future FIPS code release and one assert fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for future FIPS code release and one assert fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.</li>
	<li>Adding other logging and FW enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.</li>
	<li>Adding other logging and FW enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ddc8bdca3abc4ab8823e820be1ed4dfd" version="fa241aa0a39b4f01acb7dcad24b81808" lucid_version="smartpqi.sles15.x86_64.rpm@2.1.38-022__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.1.38-022" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC drop.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC drop.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.1.36-026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added a timeout value to RAID path requests to physical devices.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added a timeout value to RAID path requests to physical devices.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where the kernel call trace when calling smp_processor_id() in real-time kernel.&nbsp;</li>
	<li>Fixed an issue of accessing NULL SCSI device pointer caused by a rare race condition.&nbsp;</li>
	<li>Fixed a system crash issue caused by a divide-by-zero condition.&nbsp;</li>
	<li>Fixed an issue where after a device has been removed, it&#39;s possible for a previously scheduled work item for a LUN reset to be executed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where the kernel call trace when calling smp_processor_id() in real-time kernel.&nbsp;</li>
	<li>Fixed an issue of accessing NULL SCSI device pointer caused by a rare race condition.&nbsp;</li>
	<li>Fixed a system crash issue caused by a divide-by-zero condition.&nbsp;</li>
	<li>Fixed an issue where after a device has been removed, it&#39;s possible for a previously scheduled work item for a LUN reset to be executed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1c46045c33184d1799f444fdcc47fcfb" version="ab788be41104476ca3dd5b1a27360ac4" lucid_version="U77.fwpkg@1.40_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.40_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logos across all boot screens (early POST, late POST, System Utility, and BGRT) to reflect the new HPE corporate identity.</p><p>
Added multi-language support (Chinese and Japanese) for RBSU setup menus, Boot Configuration, NVMe-oF configuration, Secure Boot configuration, Key Manager, and Factory Options.</p><p>
Added logic to prevent personally identifiable information (PII) from being written to AHS logs while retaining visibility on the serial console.</p><p>
Added BootNext and CQTBOOTNEXT synchronization to ensure the iLO One-Time Boot option is cleared after the selected UEFI target has been launched, preventing unintended repeat boots.</p><p>
Updated SMBIOS Type 9, Type 16, and Type 203 records to report CXL 2.X devices, enabling iLO and management tools to identify CXL memory controllers and slots.</p><p>
Added a new RBSU option to configure the Intel Platform Communications Technology (PCT) feature.</p><p>
Updated integrated NIC firmware.</p><p></p><p>Ported C-state ACPI table generation to align behavior across Gen12 platforms.</p><p>
Updated SMBIOS Type 4 Maximum Processor Speed to 3500 MHz for DL110 Gen12 per specification.</p><p>
Updated SMBIOS Type 234 to carry DPLL module serial and part number from FRU data for Rev.B modules on DL110/EL140 Gen12.</p><p>Improved device name display: RBSU now falls back to the English device name for option ROMs that do not provide multi-language strings.</p><p>
Updated GPIO specification support to version 18 for Gen12 platforms.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logos across all boot screens (early POST, late POST, System Utility, and BGRT) to reflect the new HPE corporate identity.</p><p>
Added multi-language support (Chinese and Japanese) for RBSU setup menus, Boot Configuration, NVMe-oF configuration, Secure Boot configuration, Key Manager, and Factory Options.</p><p>
Added logic to prevent personally identifiable information (PII) from being written to AHS logs while retaining visibility on the serial console.</p><p>
Added BootNext and CQTBOOTNEXT synchronization to ensure the iLO One-Time Boot option is cleared after the selected UEFI target has been launched, preventing unintended repeat boots.</p><p>
Updated SMBIOS Type 9, Type 16, and Type 203 records to report CXL 2.X devices, enabling iLO and management tools to identify CXL memory controllers and slots.</p><p>
Added a new RBSU option to configure the Intel Platform Communications Technology (PCT) feature.</p><p>
Updated integrated NIC firmware.</p><p></p><p>Ported C-state ACPI table generation to align behavior across Gen12 platforms.</p><p>
Updated SMBIOS Type 4 Maximum Processor Speed to 3500 MHz for DL110 Gen12 per specification.</p><p>
Updated SMBIOS Type 234 to carry DPLL module serial and part number from FRU data for Rev.B modules on DL110/EL140 Gen12.</p><p>Improved device name display: RBSU now falls back to the English device name for option ROMs that do not provide multi-language strings.</p><p>
Updated GPIO specification support to version 18 for Gen12 platforms.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Kaseyville Granite Rapids-D XCC PV & HCC PLR4 BKC update.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Resolved an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Resolved an issue where the OCP PCIe Auxiliary Power slot option in RBSU displayed the wrong OCP slot number on platforms where CPLD and PCA OCP numbering are reversed.</p><p>Resolved an issue where Crash Log binaries could not be exported from AHS logs due to a structure alignment mismatch. Byte-packed structure definitions now match the Intel specification offsets.</p><p>
Resolved an issue where USB 3.0 NIC adapters with ASIX chips did not display USB device information in RBSU when connected to certain rear USB ports. The SMBIOS Type 238/239 record creation logic now correctly traverses all host controllers for USB 3.0 ports.</p><p>
Resolved an intermittent issue where the CQTDISC EV and property values could fall out of synchronization between iLO and BIOS across boots. The translate handler is now unconditionally executed on every boot.</p><p>
Resolved an issue where the DIMM MapOut reason field in SMBIOS Type 232 displayed 0x00 after reboot on Kaseyville platforms. The HOB-first priority algorithm now correctly persists MapOut reason data across resets.</p><p>
Resolved an issue where the VerifyMode setting had no display value in the Embedded UEFI Shell due to a string buffer allocation that did not account for the null terminator.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Kaseyville Granite Rapids-D XCC PV & HCC PLR4 BKC update.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Resolved an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Resolved an issue where the OCP PCIe Auxiliary Power slot option in RBSU displayed the wrong OCP slot number on platforms where CPLD and PCA OCP numbering are reversed.</p><p>Resolved an issue where Crash Log binaries could not be exported from AHS logs due to a structure alignment mismatch. Byte-packed structure definitions now match the Intel specification offsets.</p><p>
Resolved an issue where USB 3.0 NIC adapters with ASIX chips did not display USB device information in RBSU when connected to certain rear USB ports. The SMBIOS Type 238/239 record creation logic now correctly traverses all host controllers for USB 3.0 ports.</p><p>
Resolved an intermittent issue where the CQTDISC EV and property values could fall out of synchronization between iLO and BIOS across boots. The translate handler is now unconditionally executed on every boot.</p><p>
Resolved an issue where the DIMM MapOut reason field in SMBIOS Type 232 displayed 0x00 after reboot on Kaseyville platforms. The HOB-first priority algorithm now correctly persists MapOut reason data across resets.</p><p>
Resolved an issue where the VerifyMode setting had no display value in the Embedded UEFI Shell due to a string buffer allocation that did not account for the null terminator.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.30_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled support for Digital Phase-Locked Loop (DPLL) module working in 8 hours hold-over to provide a precise time synchronization feature.</p><p>Updated vRAN workload profile settings in align with Intel FlexRAN Reference Guide specifications 2.4.1.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled support for Digital Phase-Locked Loop (DPLL) module working in 8 hours hold-over to provide a precise time synchronization feature.</p><p>Updated vRAN workload profile settings in align with Intel FlexRAN Reference Guide specifications 2.4.1.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p><p>This version of the System ROM contains updates aligned with Intel Kaseyville Granite Rapids-D XCC PV & HCC PLR4 BKC update.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
</p><p><strong>Firmware Dependencies:</strong></p><p>None</p><p><strong>Problems Fixed:</strong></p><p>Addressed an issue where OS driver may have intermittent instability issue when system is using GNSS module via UART interface.</p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p><strong>Known Issues:</strong></p><p>None</p>]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p><p>This version of the System ROM contains updates aligned with Intel Kaseyville Granite Rapids-D XCC PV & HCC PLR4 BKC update.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
</p><p><strong>Firmware Dependencies:</strong></p><p>None</p><p><strong>Problems Fixed:</strong></p><p>Addressed an issue where OS driver may have intermittent instability issue when system is using GNSS module via UART interface.</p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p><strong>Known Issues:</strong></p><p>None</p>]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="e8f02987fae14861a37eb27a43adf117" version="da9ea0f674284c5bb3e75189abfbfa55" lucid_version="Gen10P_Gen11_Gen12_hpemrsa.win.x64@8.16.13.0__sc-windows_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="8.16.13.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16&nbsp;AV2 PR2&nbsp;GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16&nbsp;AV2 PR2&nbsp;GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.12.52.0 (C)" revision="C" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated component metadata.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated component metadata.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="cf8da25238034e5cba8fbcf0ad388e5d" version="1af382361a0949ed9078332ccecf47e6" lucid_version="FWPKG_MV003200KYFFK_MV006400KYFFA_MV012800KYFFB@HPK4__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>will udpate when release note is available</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>will udpate when release note is available</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>will udpate when release note is available</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>will udpate when release note is available</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7f5cc2735e814d67a516e6e72cb03eec" version="6c1e95ec13354cdd998cd911da77c3d9" lucid_version="SmartPqi.win2022.2025@1016.30.0.1014__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1016.30.0.1014" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1016.24.0.1002 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0a1bd2e7b61541c2bab363dfb955ff0b" version="d51ecf4c308749148cf685f20b723f7e" lucid_version="bnxtnet.vmware91@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2497303b5659412db6fee133d90bad29" version="70dcca6837ab4f8682b7c79b0b47badc" lucid_version="FWPKG_MB018000JXMTH_MB020000JXMTP@HPD3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Assert fixes, current firmware improvements and bug fixes.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Assert fixes, current firmware improvements and bug fixes.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c96c291d559642349eed747cd15c1eb4" version="c5024bc4e06f4553aff4a5169fe8aa1b" lucid_version="FWPKG_MB004000GWKGV@HPG1-rev1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG1" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes potential data integrity risk found during supplier ongoing testing.</li>
	<li>Corrects conditions which could cause the drive to become inaccessible.</li>
	<li>Includes improvements to enhance drive reliability.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes potential data integrity risk found during supplier ongoing testing.</li>
	<li>Corrects conditions which could cause the drive to become inaccessible.</li>
	<li>Includes improvements to enhance drive reliability.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="eef97edd40804b979a1b1784aa704e78" version="18fafe624bd44e6ca778fde474c04ecb" lucid_version="FWPKG_VV003840KXNTH_VV007680KXNTN_VV015360KXNTP@HPK6__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware maintenance release of Samsung PM1743 NVMe SSD with HPK6</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware maintenance release of Samsung PM1743 NVMe SSD with HPK6</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK5" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Modify Power State modes (25/18/16/14W) which can be enabled as an option.</li>
	<li>Improved on TTR requirement&nbsp;to fix device temporarily not found issue after hot-plug.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Modify Power State modes (25/18/16/14W) which can be enabled as an option.</li>
	<li>Improved on TTR requirement&nbsp;to fix device temporarily not found issue after hot-plug.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f2a63f15af75433da30e835b983f61c7" version="8e44d864accc44da867b3c2d769983b5" lucid_version="U70.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="93312d51d8f7459ba48a2a8cbf6722a2" version="1decdc7a90514de49ce94757cbae9943" lucid_version="ssacli.vmware8.0.sc@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>New drop for 6.60.8.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>New drop for 6.60.8.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.09.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
	<li>Fixed an issue where the last failure reason was not listing on physical drives.&nbsp;</li>
	<li>Fixed an issue where SSAScripting failed to create an encrypted volume while in express local mode.&nbsp;</li>
	<li>Fixed an issue where an error/warning message was not being generated correctly while expanding a RAID 1+0 volume.&nbsp;</li>
	<li>Fixed an issue where a duplicate entry for the physical drive was displayed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
	<li>Fixed an issue where the last failure reason was not listing on physical drives.&nbsp;</li>
	<li>Fixed an issue where SSAScripting failed to create an encrypted volume while in express local mode.&nbsp;</li>
	<li>Fixed an issue where an error/warning message was not being generated correctly while expanding a RAID 1+0 volume.&nbsp;</li>
	<li>Fixed an issue where a duplicate entry for the physical drive was displayed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="509f54411aaa488d8ade3254836debf4" version="5c536fa4fdef41e08d38b08ff10d54da" lucid_version="FWPKG_MO001600KXVYH_MO003200KXVZD_MO006400KXVZE@HPK4__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release for sanitize, DRAM and log page fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release for sanitize, DRAM and log page fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix for PCIe link length drop in AMD x2 system configuration</li>
	<li>Fix for drive detection after hot re-insert on Windows</li>
	<li>Fix for other regular FW patch release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix for PCIe link length drop in AMD x2 system configuration</li>
	<li>Fix for drive detection after hot re-insert on Windows</li>
	<li>Fix for other regular FW patch release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="75b226eeea7c4059b46a8ebaf1741729" version="fb0aa12c83184b04a71456cef38dc8e6" lucid_version="ssacli.vmware9.1.sc@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9e8e27c635aa4ebbbd9d4b00de424938" version="df78cf397a054aa8ac19a5be9847dec6" lucid_version="Gen12_Storcli-sut_AV2.esxi91@2026.04.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.04.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initinal version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initinal version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="39c8fff4d1c349b2a42d407b521a997e" version="6c5e0612a90e4c148393fa0e47e2799d" lucid_version="FWPKG_VV030720KYNYP@HPK6__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPK6 is a planned maintenance release that follows the HPK3 FW release for the P5430, 30.72TB (8K IU) Solid State Drive. This is a recommended FW release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPK6 is a planned maintenance release that follows the HPK3 FW release for the P5430, 30.72TB (8K IU) Solid State Drive. This is a recommended FW release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1ce0e74c5e434304b12135f5c4b5fc88" version="2cf2420717ec4ad9b92dc32684a071d5" lucid_version="nicfwpkg_intel_e825_ien1@4.03__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.03" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c0b32e18323043a4bc753357766ed2a1" version="e523283fa82f46b89234046df100021c" lucid_version="STMGen12.Fwpkg@1.1.0__fwpkg-power_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.1.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>

<p>None</p>

<p><strong>Firmware Dependencies:</strong></p>

<p>None</p>

<p><strong>Enhancements/New Features:</strong></p>

<p>This is the initial verison of the firmware.</p>

<p><strong>Known Issues:</strong></p>

<p>None</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>

<p>None</p>

<p><strong>Firmware Dependencies:</strong></p>

<p>None</p>

<p><strong>Enhancements/New Features:</strong></p>

<p>This is the initial verison of the firmware.</p>

<p><strong>Known Issues:</strong></p>

<p>None</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7fc78ba6f4174eae8b7e06638191844b" version="cf0615bbfbbd47ed854ab307d9a173f5" lucid_version="FWPKG_MO001600KYFFF_MO003200KYFET_MO006400KYFEU@HPK2__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements. Upgrading from HPK1 to HPK2 requires power cycle.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements. Upgrading from HPK1 to HPK2 requires power cycle.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1fd7960ad8c54c2e9fd2338f4b22990b" version="0bc85e12168f40a39ba72db670955e59" lucid_version="FWPKG_MB006000GWKGR@HPG1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware fixes an issue where the drive can become inaccessible after an emergency power off, and corrects a potential verification issue during read recovery.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="79949863b3a5452487d1035ae487743e" version="5f513eeaa56341f499c99db39a2efe03" lucid_version="FWPKG_MB12000GYESP_MB16000GYEVF_MB20000GYEVH@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Regular FW fix on assert, time-out, error log several fixes.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Regular FW fix on assert, time-out, error log several fixes.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix FW assert and other regular fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix FW assert and other regular fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="435031f572ea43b79bd116d63a99a58a" version="2b965028c8404b848ffa9d7f56cf8f4e" lucid_version="nicfwpkg_bcme_57414_2p25@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="41b320ad66f042c0996f23c6087a171e" version="7119986212bc4928a0c2b52ab982490d" lucid_version="nicfwpkg_bcme_57412_2p10@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="32e70edc717a4f199fb4d966f5a2ab73" version="96c18a3cdac44b61aa2e328d135be76c" lucid_version="ssacli.ubuntu@6.60.8.0(B)__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.60.8.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="773dda1e7dc047bcafe62fe7d6a4999a" version="bc12caf59c4d47ccb90746b1bc562789" lucid_version="FWPKG_VK000480GZCNE_VK000960GZCNF_VK001920GZCNH@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improve the FW about data mismatch after SPL</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improve the FW about data mismatch after SPL</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4e3802b484324394ada6924af481323b" version="6aec0619ce4e437692d7574f735b7911" lucid_version="intel_cvl.w2k25@1.20.43.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.20.43.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.18.86.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhanced traffic flow in queue map rebalance.</li>
	<li>This product enhanced &nbsp;media type detection over PHY logic.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product enhanced traffic flow in queue map rebalance.</li>
	<li>This product enhanced &nbsp;media type detection over PHY logic.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed the system event logging.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed the system event logging.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6d5b098230e341e9881e9381bf19ba96" version="431bcf46da794f4b882c6a8f1cfb176b" lucid_version="iavf.rhel9@4.13.20-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.13.20-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.13.16-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="25ce2a20c3994616bfbadbd7f26aa875" version="7d75a3880a7741a7aab127f888f5fd01" lucid_version="lpfc.sles16.x86_64_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>SUSE Linux Enterprise Server 16</p>

<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>SUSE Linux Enterprise Server 16</p>

<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fc90f99dec3d4432a73ac738a336cdc1" version="44d3b0b01c1f481aa71f46f0b41ea42b" lucid_version="amsd_rhel10@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.6.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="80ea6cb0c7d14159a1a37d37866e5b0c" version="49e6c99f43004489b7e90043d5d9952d" lucid_version="nicfwpkg_bcme_57412_2p10ocp@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixed the issue where PCIe Negotiated Link Width is displaying as x4 instead of x8.</li>
	<li>This product fixed the issue where NICs with LR cables and transceivers showing SR mode.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a00e6ed1db904ebf80004d7820172e46" version="283804e10b744386918b8ec6ad804f0a" lucid_version="ice.rhel10@2.4.5-1-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.4.5-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 10.1</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 10.1</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.4.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 10.1</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product add support for RHEL 10.1</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="50cf5a257282415691232875f3bae146" version="116080298d524355a0632a79dfe030ea" lucid_version="iLO7.fwpkg@1.21.00__fwpkg-ilo_en"/>
      <revision_history>
        <revision>
          <version value="1.21.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Refer to&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007695en_us&amp;docLocale=en_US" rel="noopener noreferrer" target="_blank">iLO 7 v1.21.00 Release Notes</a>&nbsp;for the Enhancements done in release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Refer to&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007695en_us&amp;docLocale=en_US" rel="noopener noreferrer" target="_blank">iLO 7 v1.21.00 Release Notes</a>&nbsp;for the Enhancements done in release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Refer to&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007695en_us&amp;docLocale=en_US" rel="noopener noreferrer" target="_blank">iLO 7 v1.21.00 Release Notes</a>&nbsp;for the Fixes done in release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Refer to&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007695en_us&amp;docLocale=en_US" rel="noopener noreferrer" target="_blank">iLO 7 v1.21.00 Release Notes</a>&nbsp;for the Fixes done in release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.20.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added support for:&nbsp;
	<ul>
		<li>Configuring server boot order during POST with changes applied on the next system reboot</li>
		<li>Nvidia RTX4500 Accelerator support in iLO 7</li>
		<li>PLDM File Transfer Specification (DSP0242) from iLO 7</li>
		<li>Intel 830NIC support in iLO 7</li>
		<li>HPE Cassini Slingshot SS11 and HPE Slingshot SA410S Thermal and Inventory information in iLO 7</li>
		<li>Micron &amp; Samsung root CA for SPDM authentication</li>
		<li>OS log redirection into the Virtual Serial Port console for Ubuntu 24.04 OS</li>
		<li>Support for server AssetTag length up to 63 characters. This requires a compatible BIOS FW to be installed. For BIOS support, refer to the latest BIOS Release Notes</li>
		<li>Informational message in the iLO web interface to install AMS and enable Virtual NIC when AMS status displays Not installed</li>
		<li>Prevent Duplicate key mode in HTML IRC to avoid duplicate keystrokes on high‑latency networks</li>
		<li>iLO IML event support for new RDE Storage Alerts.</li>
		<li>Single NVMe drive erase using Redfish API</li>
	</ul>
	</li>
	<li>Enabled Clipboard support from HTML IRC to allow copying and pasting text</li>
	<li>Enabled Boot Menu support from HTML IRC</li>
	<li>Enabled support for PowerWatts and InputPowerWatts metrics in EnvironmentMetrics and PowerSupplyMetrics</li>
	<li>Enabled USB management and Timing Sync support for CEM6 and CEM7 for PCIe from iLO 7</li>
	<li>Enabled TPM‑1 measurements‑related Redfish URI support</li>
	<li>Enabled Domain Name support from iLO 7 web interface for Thales CipherTrust Manager.</li>
	<li>Added support for minimum password length of 4 characters for iLO users</li>
	<li>Ported the Properties under the Power schema to the PowerSubsystem schema to align with DMTF standards</li>
	<li>Enhanced handling of invalid virtual media URLs with graceful failure messaging</li>
	<li>Support for configuring Direct-Attached Self-Encrypting Drives (SED) using iLO web interface</li>
	<li>Enhanced Node Wipe Password Recovery option. iLO Service Port is now used to obtain the nonce for default administrator password recovery process. iLO web interface displays the nonce expiry period and option to regenerate the nonce</li>
	<li>Enabled iLO 7 support for UBM11 with a storage controller</li>
	<li>Replaced power-sensor property PowerCapacityWatts with Reading and set the ReadingUnits property as W</li>
	<li>Enhanced error reporting for dual signing validation failures to improve troubleshooting</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added support for:&nbsp;
	<ul>
		<li>Configuring server boot order during POST with changes applied on the next system reboot</li>
		<li>Nvidia RTX4500 Accelerator support in iLO 7</li>
		<li>PLDM File Transfer Specification (DSP0242) from iLO 7</li>
		<li>Intel 830NIC support in iLO 7</li>
		<li>HPE Cassini Slingshot SS11 and HPE Slingshot SA410S Thermal and Inventory information in iLO 7</li>
		<li>Micron &amp; Samsung root CA for SPDM authentication</li>
		<li>OS log redirection into the Virtual Serial Port console for Ubuntu 24.04 OS</li>
		<li>Support for server AssetTag length up to 63 characters. This requires a compatible BIOS FW to be installed. For BIOS support, refer to the latest BIOS Release Notes</li>
		<li>Informational message in the iLO web interface to install AMS and enable Virtual NIC when AMS status displays Not installed</li>
		<li>Prevent Duplicate key mode in HTML IRC to avoid duplicate keystrokes on high‑latency networks</li>
		<li>iLO IML event support for new RDE Storage Alerts.</li>
		<li>Single NVMe drive erase using Redfish API</li>
	</ul>
	</li>
	<li>Enabled Clipboard support from HTML IRC to allow copying and pasting text</li>
	<li>Enabled Boot Menu support from HTML IRC</li>
	<li>Enabled support for PowerWatts and InputPowerWatts metrics in EnvironmentMetrics and PowerSupplyMetrics</li>
	<li>Enabled USB management and Timing Sync support for CEM6 and CEM7 for PCIe from iLO 7</li>
	<li>Enabled TPM‑1 measurements‑related Redfish URI support</li>
	<li>Enabled Domain Name support from iLO 7 web interface for Thales CipherTrust Manager.</li>
	<li>Added support for minimum password length of 4 characters for iLO users</li>
	<li>Ported the Properties under the Power schema to the PowerSubsystem schema to align with DMTF standards</li>
	<li>Enhanced handling of invalid virtual media URLs with graceful failure messaging</li>
	<li>Support for configuring Direct-Attached Self-Encrypting Drives (SED) using iLO web interface</li>
	<li>Enhanced Node Wipe Password Recovery option. iLO Service Port is now used to obtain the nonce for default administrator password recovery process. iLO web interface displays the nonce expiry period and option to regenerate the nonce</li>
	<li>Enabled iLO 7 support for UBM11 with a storage controller</li>
	<li>Replaced power-sensor property PowerCapacityWatts with Reading and set the ReadingUnits property as W</li>
	<li>Enhanced error reporting for dual signing validation failures to improve troubleshooting</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>There are no fixes in the current HPE iLO7 release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>There are no fixes in the current HPE iLO7 release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="23c569ea92fb47f091a7a0c891acff72" version="6a7332dbeacd418a9cb8b8ece729e4e7" lucid_version="FWPKG-P25960-B21@22.48.1000__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="22.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 22.48.1000:</strong></p>

<ul>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 22.48.1000:</strong></p>

<ul>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version&nbsp;22.48.1000:</strong></p>

<ul>
	<li>An issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version&nbsp;22.48.1000:</strong></p>

<ul>
	<li>An issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="22.46.3048" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version&nbsp;22.46.3048:</strong></p>

<ul>
	<li>Added support for RSS with crypto offload enabling the NIC to parallelize packet processing across CPU cores while performing encryption/decryption in hardware. Additionally, introduced a new l4_type_ext parameter with values: 0 (None), 1 (TCP), 2 (UDP), 3 (ICMP).</li>
	<li>Added an extra validation for the payload_len field in incoming NC-SI messages. Previously, invalid packets might have been accepted; now, such packets are silently dropped.</li>
	<li>This release contains important reliability improvements and security hardening enhancements. HPE recommends upgrading your devices firmware to this release to improve the devices&rsquo; firmware security and reliability.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version&nbsp;22.46.3048:</strong></p>

<ul>
	<li>Added support for RSS with crypto offload enabling the NIC to parallelize packet processing across CPU cores while performing encryption/decryption in hardware. Additionally, introduced a new l4_type_ext parameter with values: 0 (None), 1 (TCP), 2 (UDP), 3 (ICMP).</li>
	<li>Added an extra validation for the payload_len field in incoming NC-SI messages. Previously, invalid packets might have been accepted; now, such packets are silently dropped.</li>
	<li>This release contains important reliability improvements and security hardening enhancements. HPE recommends upgrading your devices firmware to this release to improve the devices&rsquo; firmware security and reliability.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version&nbsp;22.46.3048:</strong></p>

<ul>
	<li>Configuring a small MTU led to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discarded these packets, causing the PXE boot to fail.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version&nbsp;22.46.3048:</strong></p>

<ul>
	<li>Configuring a small MTU led to fragmentation of packets critical for the PXE boot process. As a result, the PXE boot filters mistakenly discarded these packets, causing the PXE boot to fail.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d22b64be5c5a4b6ba7275ccc0b26fa26" version="06e5d28c078f4733ab90d2fa60e2ea22" lucid_version="lpfc.sles15.x86_64_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.473.26" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>SuSE Linux Enterprise 15 SP&nbsp;7</p>

<p>Updated to&nbsp;version 14.4.473.26</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>SuSE Linux Enterprise 15 SP&nbsp;7</p>

<p>Updated to&nbsp;version 14.4.473.26</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8737ae26e7954415ac1ce9fe455fdd07" version="913462c97f3b4427bfabd689d93cea7f" lucid_version="HPE_MR216i-o_Gen11@52.36.3-6584__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="52.36.3-6584" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="52.32.3-6333" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="923962bdfca34182b6d15e9c5f837c3b" version="6d6afe1040c748ab8921b0ab1f830219" lucid_version="intelqat.win.x64@2.7.0.37__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="2.7.0.37" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported products&nbsp;</li>
	<li>Update setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported products&nbsp;</li>
	<li>Update setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Intel is releasing software updates to mitigate some&nbsp;potential vulnerabilities covered in&nbsp;<a href="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01373.html">INTEL-SA-01373</a>, which&nbsp;includes&nbsp;CVE-2025-33000, CVE-2025-27713, CVE-2025-32732, CVE-2025-32446, CVE-2025-27710, CVE-2025-3193, CVE-2025-266947, CVE-2025-30509 and CVE-2025-32088.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Intel is releasing software updates to mitigate some&nbsp;potential vulnerabilities covered in&nbsp;<a href="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01373.html">INTEL-SA-01373</a>, which&nbsp;includes&nbsp;CVE-2025-33000, CVE-2025-27713, CVE-2025-32732, CVE-2025-32446, CVE-2025-27710, CVE-2025-3193, CVE-2025-266947, CVE-2025-30509 and CVE-2025-32088.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.6.0.30" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported products&nbsp;</li>
	<li>Update setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported products&nbsp;</li>
	<li>Update setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Intel is releasing software updates to mitigate some&nbsp;potential vulnerabilities covered in&nbsp;<a href="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01373.html">INTEL-SA-01373</a>, which&nbsp;includes&nbsp;CVE-2025-33000, CVE-2025-27713, CVE-2025-32732, CVE-2025-32446, CVE-2025-27710, CVE-2025-3193, CVE-2025-266947, CVE-2025-30509 and CVE-2025-32088.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Intel is releasing software updates to mitigate some&nbsp;potential vulnerabilities covered in&nbsp;<a href="https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01373.html">INTEL-SA-01373</a>, which&nbsp;includes&nbsp;CVE-2025-33000, CVE-2025-27713, CVE-2025-32732, CVE-2025-32446, CVE-2025-27710, CVE-2025-3193, CVE-2025-266947, CVE-2025-30509 and CVE-2025-32088.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7c445f8c9d154bbcba7f0d5e95e97aa1" version="43a67feb2d1f443ebf8f2e21cbc93ae4" lucid_version="qla2xxx.driver.esx80.zip_rt_gen12@2026.03.01-rev1__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.4.86.0<br />
This driver is only supported on VMware ESXi 8.0u3</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.4.86.0<br />
This driver is only supported on VMware ESXi 8.0u3</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.4.86.0<br />
This driver is only supported on VMware ESXi 8.0u3</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.4.86.0<br />
This driver is only supported on VMware ESXi 8.0u3</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f9e9bf117a0d4feaa432fa83be337cd8" version="05c51a3c4d8d4915ada8a9950db969f8" lucid_version="FWPKG_MB012000GZYVT_MB014000GZYVU_MB016000GZYVV@HPG6__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Function implement</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Function implement</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This maintenance revision improves data integrity. The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions. Several maintenance items are included in this firmware revision that reduce the probability of hangs and provide a minor performance improvement.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This maintenance revision improves data integrity. The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions. Several maintenance items are included in this firmware revision that reduce the probability of hangs and provide a minor performance improvement.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improves data integrity.&nbsp;</li>
	<li>The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.&nbsp;</li>
	<li>Several maintenance items are included in this firmware revision that reduce the probability of hangs and provide a minor performance improvement.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improves data integrity.&nbsp;</li>
	<li>The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.&nbsp;</li>
	<li>Several maintenance items are included in this firmware revision that reduce the probability of hangs and provide a minor performance improvement.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9117053fed1245019c94aab3982b0102" version="3499ad24a1394d098cf83303fba5de87" lucid_version="smartpqi.sles16.x86_64.rpm@2.1.38-022(B)__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.1.38-022" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>N/A.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>N/A.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.1.38-022" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>N/A.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>N/A.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="51c32f839fa74377ae52ffa2a8edc0ea" version="a790c8d9f231488f98a113f26bd63901" lucid_version="FWPKG_MB006000JYDNF_MB008000JYDPC@HPD5__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD5" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for future FIPS code release and one assert fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Firmware changes aligned for future FIPS code release and one assert fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.</li>
	<li>Adding other logging and FW enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes the logic bug in the media cache cleaning abort handling that caused the drive to choose and execute the R/W command before the Request Sense to prevent assert.</li>
	<li>Adding other logging and FW enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9adece559a5e4fcf8de67cd47aa7d7c7" version="e4dd77efe5874d5182f4c9320fb8bada" lucid_version="FWPKG_VO000960PZWSL_VO001920PZWSN@HPD4-rev1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPD4" revision="" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD4" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>&nbsp;which will be active on 18-Aug-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a firmware maintenance release. It addresses a potential data loss issue, along with other bug fixes and improvements.</li>
	<li>For more information, refer to HPE Customer Bulletin at the following URL:&nbsp;<a href="https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us">https://support.hpe.com/hpsc/doc/public/display?docId=a00150711en_us</a>&nbsp;which will be active on 18-Aug-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4ebaaedffb0243f8b4f50ed7cc2ad62c" version="afa28ddd81554a0ca72de91218fc9034" lucid_version="FWPKG_VK000240GZXRU_VK000480GZXRF_VK000960GZXQU@HPG1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix contains optimization to increase the time for Recovery operation and few checks for maintenance</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix contains optimization to increase the time for Recovery operation and few checks for maintenance</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="85a59acb7d634eb691745a6c9906ad03" version="f938549da08643888919a5c57a12883c" lucid_version="ssacli.vmware9.0.sc@2026.03.01-rev1__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a83500e26a4d4bb89a4eb5821b7b2ca6" version="77c0abf6e6e340938e331cc9e83e5a7f" lucid_version="amdpshed.win2022.x64@1.0.0.51(E)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="1.0.0.51" revision="E" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility&nbsp;dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility&nbsp;dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.0.0.51 (D)" revision="D" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Software Category</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Software Category</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Updated installer.dll</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Updated installer.dll</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3d51e7d6b8674f16bd8f67bee278e11a" version="c1a1e73eca0649aba8389a70d7e7b502" lucid_version="HPE_SR_Gen10_SR308i_Gen11@8.00__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="8.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>For Jan 2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>For Jan 2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="7.81" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added SSD life expectancy monitoring.&nbsp;</li>
	<li>Added support to require privileged operations token for all RDE ACTION operations, including Drive.Reset and Storage.SetEncryptionKey, improving security for data-destructive actions.&nbsp;</li>
	<li>Added support to provide meaningful updateInterval values for Numeric Sensor PDRs, setting 5 seconds for controller temperature and 60 seconds for drive temperature sensors.&nbsp;</li>
	<li>Enhanced the calculation of CapacityBytes@Redfish.AllowableNumbers for Volume Capabilities. The maximum allowable value is now set to the larger of (a) the largest free space range on any existing array, or (b) the sum of unassigned drives with a common interface and media type.&nbsp;</li>
	<li>Enhanced DriveMetrics support by updating the schema version from 1.0.0 to 1.2.0, adding reporting for ReadIOKiBytes and WriteIOKiBytes properties.&nbsp;</li>
	<li>Added an enhancement to display drive vendor and model name as separate fields in the Disk Information menu, improving clarity and ease of drive identification.&nbsp;</li>
	<li>Added support to securely transfer encryption keys in remote key management mode.&nbsp;</li>
	<li>Enhanced drive writes cache status reporting in HII.&nbsp;</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added SSD life expectancy monitoring.&nbsp;</li>
	<li>Added support to require privileged operations token for all RDE ACTION operations, including Drive.Reset and Storage.SetEncryptionKey, improving security for data-destructive actions.&nbsp;</li>
	<li>Added support to provide meaningful updateInterval values for Numeric Sensor PDRs, setting 5 seconds for controller temperature and 60 seconds for drive temperature sensors.&nbsp;</li>
	<li>Enhanced the calculation of CapacityBytes@Redfish.AllowableNumbers for Volume Capabilities. The maximum allowable value is now set to the larger of (a) the largest free space range on any existing array, or (b) the sum of unassigned drives with a common interface and media type.&nbsp;</li>
	<li>Enhanced DriveMetrics support by updating the schema version from 1.0.0 to 1.2.0, adding reporting for ReadIOKiBytes and WriteIOKiBytes properties.&nbsp;</li>
	<li>Added an enhancement to display drive vendor and model name as separate fields in the Disk Information menu, improving clarity and ease of drive identification.&nbsp;</li>
	<li>Added support to securely transfer encryption keys in remote key management mode.&nbsp;</li>
	<li>Enhanced drive writes cache status reporting in HII.&nbsp;</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where SEDs reverting to foreign after controller reboot due to the otherwise owned flag not being saved to the datastore.&nbsp;</li>
	<li>Fixed an issue where firmware crash/lockup during NDSR (Non-Disruptive Software Reset) due to a NULL pointer reference when handling a failed drive during logical drive rebuilt.&nbsp;</li>
	<li>Fix 4Kn foreign SED being imported into a 512B logical drive due to incorrect failure handling, which could start a rebuild on an incompatible drive and ultimately fail.&nbsp;</li>
	<li>Fixed an issue where multiple logical drives incorrectly showing REBUILDING simultaneously due to rebuild status not being updated properly during queued transformation and rebuild processes&nbsp;</li>
	<li>Fixed an issue where master key change failure on Managed SED logical drives due to LU cache flush requests conflicting with the password update process.&nbsp;</li>
	<li>Fixed an issue where physical drive Predictive Failure status not reported correctly by tools and iLO.&nbsp;</li>
	<li>Fixed an issue where controller lockup during surface scan caused by stale internal resources when handling Unrecoverable Read Errors (UREs) in unmapped logical drive regions.&nbsp;</li>
	<li>Fixed an issue where uncorrectable DDR ECC errors could be reported at boot due to cache being accessed before initialization.&nbsp;</li>
	<li>Fixed an issue where the controller could lock up (0x3120C) when enabling MCP due to duplicate routing entries from flooded BMC requests.&nbsp;</li>
	<li>Fixed an issue where SATA drives could be incorrectly reported as hot-removed during spin-up by adjusting the dampen timer to align with vendor-specified TTR values.&nbsp;</li>
	<li>Fixed an issue where the controller could lock up (0x1E30) under high I/O workloads when configuration changes occurred simultaneously with a LUN reset.&nbsp;</li>
	<li>Fixed an issue where RAID 0 could hang with I/O timeouts and LUN resets during Predictive Spare Rebuild.&nbsp;</li>
	<li>Fixed an issue where the RAID controller could incorrectly report Online Firmware Activation as enabled. Firmware now checks support during PQI initialization and sets or clears the feature flags accordingly.&nbsp;</li>
	<li>Fixed an issue where drives in some enclosures could show bay number 255 after the enclosure was powered on and hot-plugged, by adding handling for additional SCSI not ready status codes until the enclosure becomes ready.&nbsp;</li>
	<li>Fixed an issue where Micron 6550 SED drives could fail to create a Secured Volume due to insufficient timeout during the TCG Revert process.&nbsp;</li>
	<li>Fixed an issue where the controller Health state from PLDM PDRs could differ from the Storage.Status.HealthRollup value in RDE, by synchronizing the reporting logic.&nbsp;</li>
	<li>Fixed an issue where SSD firmware updates could fail in dual path configurations due to PLDM errors, by sending Test Unit Ready commands to clear check conditions before SCSI passthrough operations.&nbsp;</li>
	<li>Fixed an issue where Battery Redfish Alerts contained an incorrect OriginOfCondition pointing to a StorageController instead of the Battery resource.&nbsp;</li>
	<li>Fixed an issue where RDE UPDATE operations on a Volume&rsquo;s ReadCachePolicy could incorrectly appear successful during a CBE rekey, by adjusting the cache update logic to return accurate results regardless of cache status.&nbsp;</li>
	<li>Fixed an issue where the HotspareActivationPolicy allowable values incorrectly included OnDriveFailure for RAID 0 volumes with a dedicated spare, by adding configuration checks to ensure only valid values are shown.&nbsp;</li>
	<li>Fixed an issue where there is a mismatch in Overall Health State and Logical Volume State during RPI, with sensors reporting Warning (Overall Health) while RDE READs ( Logical Volume State) showed OK; reporting OK during RPI is exxpected behavior.&nbsp;</li>
	<li>Fixed an issue where ProtectedWriteBack could incorrectly appear as an allowable WriteCachePolicy in RDE READs even without a backup power source, by requiring the power source to be connected and fully charged before publishing the option.&nbsp;</li>
	<li>Fixed an issue where an RDE READ on certain unsupported Drive resources could cause a controller lockup, by adding bounds checking in the firmware API.&nbsp;</li>
	<li>Fixed an issue where deleting volumes through PLDM Type 6 could cause a controller lockup if other PLDM commands were sent simultaneously. These commands now return NOT_READY when a long-running RDE operation is in progress.&nbsp;</li>
	<li>Fixed an issue where disk utilities could display an invalid box number for drives after failing over to an alternative path, by ensuring only valid controller-provided information is shown.&nbsp;</li>
	<li>Fixed an issue where an incorrect error message was shown in HII when creating a logical drive on a locked SED, by updating the error message to correctly reflect SED encryption.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where SEDs reverting to foreign after controller reboot due to the otherwise owned flag not being saved to the datastore.&nbsp;</li>
	<li>Fixed an issue where firmware crash/lockup during NDSR (Non-Disruptive Software Reset) due to a NULL pointer reference when handling a failed drive during logical drive rebuilt.&nbsp;</li>
	<li>Fix 4Kn foreign SED being imported into a 512B logical drive due to incorrect failure handling, which could start a rebuild on an incompatible drive and ultimately fail.&nbsp;</li>
	<li>Fixed an issue where multiple logical drives incorrectly showing REBUILDING simultaneously due to rebuild status not being updated properly during queued transformation and rebuild processes&nbsp;</li>
	<li>Fixed an issue where master key change failure on Managed SED logical drives due to LU cache flush requests conflicting with the password update process.&nbsp;</li>
	<li>Fixed an issue where physical drive Predictive Failure status not reported correctly by tools and iLO.&nbsp;</li>
	<li>Fixed an issue where controller lockup during surface scan caused by stale internal resources when handling Unrecoverable Read Errors (UREs) in unmapped logical drive regions.&nbsp;</li>
	<li>Fixed an issue where uncorrectable DDR ECC errors could be reported at boot due to cache being accessed before initialization.&nbsp;</li>
	<li>Fixed an issue where the controller could lock up (0x3120C) when enabling MCP due to duplicate routing entries from flooded BMC requests.&nbsp;</li>
	<li>Fixed an issue where SATA drives could be incorrectly reported as hot-removed during spin-up by adjusting the dampen timer to align with vendor-specified TTR values.&nbsp;</li>
	<li>Fixed an issue where the controller could lock up (0x1E30) under high I/O workloads when configuration changes occurred simultaneously with a LUN reset.&nbsp;</li>
	<li>Fixed an issue where RAID 0 could hang with I/O timeouts and LUN resets during Predictive Spare Rebuild.&nbsp;</li>
	<li>Fixed an issue where the RAID controller could incorrectly report Online Firmware Activation as enabled. Firmware now checks support during PQI initialization and sets or clears the feature flags accordingly.&nbsp;</li>
	<li>Fixed an issue where drives in some enclosures could show bay number 255 after the enclosure was powered on and hot-plugged, by adding handling for additional SCSI not ready status codes until the enclosure becomes ready.&nbsp;</li>
	<li>Fixed an issue where Micron 6550 SED drives could fail to create a Secured Volume due to insufficient timeout during the TCG Revert process.&nbsp;</li>
	<li>Fixed an issue where the controller Health state from PLDM PDRs could differ from the Storage.Status.HealthRollup value in RDE, by synchronizing the reporting logic.&nbsp;</li>
	<li>Fixed an issue where SSD firmware updates could fail in dual path configurations due to PLDM errors, by sending Test Unit Ready commands to clear check conditions before SCSI passthrough operations.&nbsp;</li>
	<li>Fixed an issue where Battery Redfish Alerts contained an incorrect OriginOfCondition pointing to a StorageController instead of the Battery resource.&nbsp;</li>
	<li>Fixed an issue where RDE UPDATE operations on a Volume&rsquo;s ReadCachePolicy could incorrectly appear successful during a CBE rekey, by adjusting the cache update logic to return accurate results regardless of cache status.&nbsp;</li>
	<li>Fixed an issue where the HotspareActivationPolicy allowable values incorrectly included OnDriveFailure for RAID 0 volumes with a dedicated spare, by adding configuration checks to ensure only valid values are shown.&nbsp;</li>
	<li>Fixed an issue where there is a mismatch in Overall Health State and Logical Volume State during RPI, with sensors reporting Warning (Overall Health) while RDE READs ( Logical Volume State) showed OK; reporting OK during RPI is exxpected behavior.&nbsp;</li>
	<li>Fixed an issue where ProtectedWriteBack could incorrectly appear as an allowable WriteCachePolicy in RDE READs even without a backup power source, by requiring the power source to be connected and fully charged before publishing the option.&nbsp;</li>
	<li>Fixed an issue where an RDE READ on certain unsupported Drive resources could cause a controller lockup, by adding bounds checking in the firmware API.&nbsp;</li>
	<li>Fixed an issue where deleting volumes through PLDM Type 6 could cause a controller lockup if other PLDM commands were sent simultaneously. These commands now return NOT_READY when a long-running RDE operation is in progress.&nbsp;</li>
	<li>Fixed an issue where disk utilities could display an invalid box number for drives after failing over to an alternative path, by ensuring only valid controller-provided information is shown.&nbsp;</li>
	<li>Fixed an issue where an incorrect error message was shown in HII when creating a logical drive on a locked SED, by updating the error message to correctly reflect SED encryption.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fbb53cf22a594dbb99b8c7f89e562124" version="f35925bfc51f45d1bd846ca78d19ca43" lucid_version="nicfwpkg_intel_e810_xxv2ocp@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="17cdb6c5103e4532a4f395d5ca5c6867" version="47c51ae5fec54f399c902368af7d4ad9" lucid_version="lpfc.rhel9.x86_64_legacy_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.473.24" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1065be4a2b444fe1b0060c3a91fcbde2" version="82ef6e94843345229b78d9dd416640b3" lucid_version="ixgbevf.rhel9@5.2.2-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="5.2.2-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="5.1.6-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an intermittent traffic failure issue from a virtual function.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an intermittent traffic failure issue from a virtual function.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6f38004b166d42068a292e455179565f" version="8ae279136d1146d9a07e0ced51a7a9cd" lucid_version="FWPKG_MK000480GYCNT_MK000960GYCNP_MK001920GYCNF@HPG4__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a planned maintenance release covering bug fixes. This firmware includes updates to improve PLI circuit reliability.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a planned maintenance release covering bug fixes. This firmware includes updates to improve PLI circuit reliability.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPG3 is a planned maintenance release covering bug fixes for 2.5&rdquo; and M.2.&nbsp;There are no critical functional updates, and risk is low for customers who do not upgrade, especially if drives are not stored without power for a long period of time (~2 years).</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>HPG3 is a planned maintenance release covering bug fixes for 2.5&rdquo; and M.2.&nbsp;There are no critical functional updates, and risk is low for customers who do not upgrade, especially if drives are not stored without power for a long period of time (~2 years).</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d473378e1f2847f48383c6be4c105511" version="aae60f5f3c27471e93887588c376e7da" lucid_version="isut-esxi@2026.05.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.05.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes</a> for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes</a> for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes</a> for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes</a> for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ef1bc7c351c4439cbfa57f557a362e59" version="ef508d000e044335b7e14985704ba1f8" lucid_version="FWPKG_VR000480KYXPQ_VR000960KYXQA_VR001920KYXQB@HPK2__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>RSOD issue fixed. RSOD was occurred during server power-on if enable the VROC.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>RSOD issue fixed. RSOD was occurred during server power-on if enable the VROC.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ad3fba5acbb54355b6ab78730e8d2635" version="27e0af300e254765a9b481eb030268f2" lucid_version="intel_vf.w2k25@1.18.158.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.18.158.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.17.63.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes an issue where the VM traffic may not working when VF driver disabled or not installed.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes an issue where the VM traffic may not working when VF driver disabled or not installed.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="15698eb1529646ec8ffe029388a40fea" version="4180e3928a07496182ad95557039ed89" lucid_version="ice.sles16@2.4.5-1-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.4.5-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product added support for SLES16</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product added support for SLES16</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.4.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product added support for SLES16</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product added support for SLES16</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed the &ldquo;Failed to apply Tx scheduling configuration, err ‑17&rdquo; issue caused by incorrect topology detection.</li>
	<li>This product fixed a kernel NULL‑pointer dereference that occurred during reset after NVM update when transmit balancing was enabled.</li>
	<li>This product fixed an issue where the VF RDMA virtual device was not created when SR‑IOV LAG dependencies were misdetected.</li>
	<li>This product fixed failures related to PTP_PIN_SETFUNC2 on Linux 6.16 and later kernels.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ec9be2d62b6d4bb78b41f4e500d70240" version="2087ae0c509a4375b1e87fbc7bc1c3d4" lucid_version="smartpqi.esxi9.0_bundle@2026.01.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.01.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.09.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed PSOD indicates a divide-by-zero happened.&nbsp;</li>
	<li>Fixed an issue where the driver&#39;s controller structure field was too small for the full ASCII firmware version.&nbsp;</li>
	<li>Fixed an issue where a message from a periodic check on the controller heartbeat appeared as a&nbsp;system error instead of an informational message.&nbsp;</li>
	<li>Fixed an issue where firmware versioning information was incorrect or blank on some of the controllers.&nbsp;</li>
	<li>Fixed an issue where in a specific scenario, the device removal handler attempts to remove a device that has already been removed by the normal device discovery flow.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed PSOD indicates a divide-by-zero happened.&nbsp;</li>
	<li>Fixed an issue where the driver&#39;s controller structure field was too small for the full ASCII firmware version.&nbsp;</li>
	<li>Fixed an issue where a message from a periodic check on the controller heartbeat appeared as a&nbsp;system error instead of an informational message.&nbsp;</li>
	<li>Fixed an issue where firmware versioning information was incorrect or blank on some of the controllers.&nbsp;</li>
	<li>Fixed an issue where in a specific scenario, the device removal handler attempts to remove a device that has already been removed by the normal device discovery flow.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3d28404b009047cd9c6ade47efd24ca6" version="eb93d80bd5624648b0ca4bca05228c97" lucid_version="nicfwpkg_bcme_57504_4p25ocp@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where, in breakout mode, a cable remove or insert failed to bring the link up because the module did not exit the DPDeactivated (Data Path Deactivated) state in time.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8fe22752c5324386870794853904b4ba" version="c8bd39758b0847a287bcd760f1f32b36" lucid_version="isut.windows_64@6.7.0.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="6.7.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.6.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c62f3aae4b654b8e8cc34f8ece3cbd16" version="e088a1365a2a4edab4deb6707e0a89e8" lucid_version="UBM10_FWPKG@1.04__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.04" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>New version.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>New version.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.02" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Fixed Secure boot not enable.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Fixed Secure boot not enable.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6adb26c5fc564f219877ab6a448e709b" version="df7b7b39b7ad460b81b893a773d6831e" lucid_version="nicfwpkg_intel_e810_xxv4ocp@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a50dbf35ae04440f80416650198e13ad" version="83c73b10694e4f28bc76948c71cdb3f2" lucid_version="FWPKG_MB016000JWXKH@HPDC__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPDC" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity. &nbsp;The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity. &nbsp;The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7353be093cb54810a8866396a0d8bfd9" version="7c0b4d2392f54478b79574236d3363b6" lucid_version="Gen12_StorCLI_AV2.linux.rpm@008.0016.0000.0011__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="008.0016.0000.0011" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2 RC1</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2 RC1</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="008.0015.0000.0011" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="58dd146b67a34b2492cfd64a1feceec4" version="d4aa3d00e1e34dccbb8740f00844aded" lucid_version="mlnx_en_roce_mlx5.sles15sp6.x86_64.rpm@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01</strong><strong>:</strong></p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01</strong><strong>:</strong></p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.07-0.9.7.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="433948a8153940e29abc6b63454b0d4e" version="4926ddf749864ad5b1f1647fab3a5362" lucid_version="nicfwpkg_intel_e825_ien2@4.03__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.03" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="163971813d65441fb10908957d409424" version="db2c0b89ab6c442e9fbbc933ec767db1" lucid_version="FWPKG-S5R60A@28.48.1000-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="28.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="28.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="79f6cf622f8844bf86357be0149ed2f6" version="d73cbde6e08f426b8572dd4a57441b47" lucid_version="FWPKG_VV001920KYMLU_VV003840KYMME@HPK5__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK5" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular maintenance release + aligning Max LBA with SFF-8447 for 15.36TB model (only applies if entire volume is formatted with PI feature enabled).</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular maintenance release + aligning Max LBA with SFF-8447 for 15.36TB model (only applies if entire volume is formatted with PI feature enabled).</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3013cefa4fe14260a6f6811796f9b1c0" version="d9082dc816c54769bf2fbe1cc35ac182" lucid_version="Gen10P_Gen11_Gen12_hpemrsa.rhel10@8.16.13.0__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="8.16.13.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2&nbsp;GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2&nbsp;GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.12.52.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Change the backplane bay count information to the actual bay that is connected to controller.</li>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation</li>
	<li>Re-order LSA GUI buttons
	<ul>
		<li>Move the Rebuild button to the top before Make Online button</li>
		<li>Add the Rebuild button in the Offline Drive warning session</li>
	</ul>
	</li>
	<li>Change the recommended action for Degarded Volume to &ldquo;Make sure all the&nbsp;participating drives are connected and rebuild is complete&rdquo;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Change the backplane bay count information to the actual bay that is connected to controller.</li>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation</li>
	<li>Re-order LSA GUI buttons
	<ul>
		<li>Move the Rebuild button to the top before Make Online button</li>
		<li>Add the Rebuild button in the Offline Drive warning session</li>
	</ul>
	</li>
	<li>Change the recommended action for Degarded Volume to &ldquo;Make sure all the&nbsp;participating drives are connected and rebuild is complete&rdquo;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix MRSA issue in a00150411en_us Advisory: HPE Compute MR Controllers - HPE MR Storage Administrator (MRSA) Launch Issue and Storage Command Line Interface&nbsp;(StorCLI) Installation Warning Message Observed With Red Hat Enterprise Linux Server&nbsp;10</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix MRSA issue in a00150411en_us Advisory: HPE Compute MR Controllers - HPE MR Storage Administrator (MRSA) Launch Issue and Storage Command Line Interface&nbsp;(StorCLI) Installation Warning Message Observed With Red Hat Enterprise Linux Server&nbsp;10</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3b175f364fc14c6da598ff868e4cfb48" version="03cdf815345f4efd94751eaefd47e77f" lucid_version="UBM2_FWPKG@1.20(F)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.20" revision="F" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Support new Gen12 servers.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Support new Gen12 servers.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.20 (E)" revision="E" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Support both Gen10P and Gen11 servers</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Support both Gen10P and Gen11 servers</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="23452ce6ae6f410f8e11e448b677d128" version="31e159c4f47f4f6ea06ca59bb182517d" lucid_version="HPE_MR416i-o_Gen11@52.36.3-6584__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="52.36.3-6584" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="52.32.3-6333" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5521a7a96ce64d8a92b5aab1a6147b6e" version="698b806535e54899a0d8cfa4fae3990c" lucid_version="FWPKG_MO000960RXKRC_MO001920RXKRH_MO003840RXKRK@HPD5(B)__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPD5" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD5" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware version fixes a bug with the unmap command that may cause a drive hang</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware version fixes a bug with the unmap command that may cause a drive hang</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5f87cfcaa78847d59e1bfff7203034fc" version="a11e2b841a61400ea5dbbb30416951bb" lucid_version="mlnx_en_roce_mlx5.rhel9u6.x86_64.rpm@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.07-0.9.7.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ce9f91a90e53444d84d0e7a4367d6fd4" version="21aa2066d8ea4cb6b8ed6a9cb6398ce4" lucid_version="icen.vmware80@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.11.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed the failed while setting LFC for PF.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed the failed while setting LFC for PF.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4fce61f8e9404561a9ecffaf7d9f1938" version="70212491801743d2a2355d3f15b732df" lucid_version="FWPKG_MK000480GZXRA_MK000960GZXRB_MK001920GZXRC@HPG1__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix contains optimization to increase the time for Recovery operation and few checks for maintenance</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix contains optimization to increase the time for Recovery operation and few checks for maintenance</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1a5464bd86004f8a8654872675e82a40" version="1797ae23900948e1b037ca509ce56122" lucid_version="FWPKG_MB010000JYDKK_MB012000JYCJF_MB014000JYCJV@HPD6__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>A Drive Firmware enhancement has been made for&nbsp;&nbsp;Primera 600 products&nbsp;to reduce the probability of infrequent, unexpected power loss on some backed drives.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>A Drive Firmware enhancement has been made for&nbsp;&nbsp;Primera 600 products&nbsp;to reduce the probability of infrequent, unexpected power loss on some backed drives.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c95f4d7a58974d93b986769dc66be359" version="09062d3010ac4d20aea9e39a0a4c6f32" lucid_version="FWPKG_MB018000GXMTK_MB020000GXMTQ@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Assert fixes, current firmware improvements and bug fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Assert fixes, current firmware improvements and bug fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ea54045e376e4b2ba3a50ebd9d55a9a5" version="4691d6d97ad14b04b51d012ce2158bab" lucid_version="mlnx_en_roce_mlx5.sles16.x86_64@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01</strong><strong>:</strong></p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01</strong><strong>:</strong></p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="58f3059c65eb403984076353b9f058af" version="351d50a2bba345ebbd72893c5d1e177f" lucid_version="FWPKG_MO000960RXRQK_MO001920RXRRH_MO003840RXRRK@HPD4(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD4" revision="B" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD4" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>To fix - Frequent insertion of low priority commands during IO execution may lead to drive offline randomly.</li>
</ul>

<p>For more information, refer to HPE Customer Advisory at the following URL:&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=a00141941en_us">https://support.hpe.com/hpesc/public/docDisplay?docId=a00141941en_us&nbsp;</a></p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>To fix - Frequent insertion of low priority commands during IO execution may lead to drive offline randomly.</li>
</ul>

<p>For more information, refer to HPE Customer Advisory at the following URL:&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=a00141941en_us">https://support.hpe.com/hpesc/public/docDisplay?docId=a00141941en_us&nbsp;</a></p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8cf1ad038d0041138bca0e81fbfc4764" version="8a3507cf3e914166b8879955e946e215" lucid_version="mlnx_en_roce_mlx5.rhel9u7.x86_64.rpm@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01:</strong><br />
&nbsp;</p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f753d0d85d5c40278c0a50daf001c162" version="48aca792bb5f49a8bea429185350764b" lucid_version="HPE_MR408i-p_Gen11@52.36.3-6584__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="52.36.3-6584" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="52.32.3-6333" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="38ed4a06a93d4f528109cbfb58421372" version="02f87f09479c47c8978da9100dcc6c4f" lucid_version="genoa-bergamo-siena-turin.win2022.x64@8.3.16.641__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="8.3.16.641" revision="" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Merge AMD hsmp driver into chipset.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Merge AMD hsmp driver into chipset.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="7.12.1.2248" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated AMD&nbsp;PSP Driver</li>
	<li>Updated&nbsp;AMD Interface Driver</li>
	<li>Updated&nbsp;AMD EPYC DRTM Boot Driver</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated AMD&nbsp;PSP Driver</li>
	<li>Updated&nbsp;AMD Interface Driver</li>
	<li>Updated&nbsp;AMD EPYC DRTM Boot Driver</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="955cffa0d4fe4b76923c0ea7afeca0bf" version="081aedd3c74d4f6ba6a7d66111ca7300" lucid_version="nicfwpkg_intel_e810_xxv4@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fe4795544ccd499089abbda20812ee7b" version="0e767af061814a01854d29987d762714" lucid_version="Gen12_MR_Controller_AV2.sles15.x86_64.rpm@8.16.1.0.0-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="8.16.1.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.16.1.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="48e3c12aac8f459bb51ccd417f154f98" version="6220f9cf082a45cb9b2a2cbfb69c6dec" lucid_version="FWPKG_VV001920LYDTT_VV003840LYDTU_VV007680LYDTV@HPK6__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>To eliminate the risk of gen drop issue.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>To eliminate the risk of gen drop issue.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>FW update to eliminate the risk of Drive missing issue.</li>
	<li>Fixed low sequential write performance in Windows 2022</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>FW update to eliminate the risk of Drive missing issue.</li>
	<li>Fixed low sequential write performance in Windows 2022</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="908c5860d0c04e9c9a697d02c94d7749" version="81df1194998e445fb3eeed7ed3fea825" lucid_version="FWPKG_MB010000GYDKP_MB012000GYCJL_MB014000GYCJT@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Regular Firmware changes included:</p>

<ul>
	<li>&nbsp;&nbsp;&nbsp; corner case performance enhance.</li>
	<li>&nbsp;&nbsp;&nbsp; Servo change that resolves issue with early heat application from Idle sweep seek terminated that may cause read errors</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Regular Firmware changes included:</p>

<ul>
	<li>&nbsp;&nbsp;&nbsp; corner case performance enhance.</li>
	<li>&nbsp;&nbsp;&nbsp; Servo change that resolves issue with early heat application from Idle sweep seek terminated that may cause read errors</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG2" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Update maximum continuous operation temperature values for host thermal management and reporting.</li>
	<li>Assert fixes, logging enhancements and all current firmware improvements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Update maximum continuous operation temperature values for host thermal management and reporting.</li>
	<li>Assert fixes, logging enhancements and all current firmware improvements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6e38b06c1a974b7e8978c0c3b1dd56d2" version="6e77bb2d457d491db94e8f29f6fadca6" lucid_version="FWPKG_EG000600JWJNP_EG001200JWJNQ_EG001200MXJQU@HPD9__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD9" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD8" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b4a175282d544f9a81122819fe562859" version="59434882aab842ef8e13c2e42c16da79" lucid_version="FWPKG_MV001600LYCBT_MV003200LYCBA_MV006400LYCBB@HPK3(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK3" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix FW force update from iLO GUI or SPP (HPK3 --&gt; HPK3)</li>
	<li>The FW address: PCIe link drop and 0ther regular FW patches release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix FW force update from iLO GUI or SPP (HPK3 --&gt; HPK3)</li>
	<li>The FW address: PCIe link drop and 0ther regular FW patches release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>The FW address: PCIe link drop and 0ther regular FW patches release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>The FW address: PCIe link drop and 0ther regular FW patches release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fb6c6d2bd14f4d43b22c64ebbd0b9b71" version="8a42ba052e284875b3481dd48e3d7a48" lucid_version="qla2xxx.driver.esx90.zip_rt_gen12@2026.03.01-rev1__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.5.85.0<br />
This driver is only supported on VMware ESXi 9.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.5.85.0<br />
This driver is only supported on VMware ESXi 9.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.5.85.0<br />
This driver is only supported on VMware ESXi 9.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Driver version 5.5.85.0<br />
This driver is only supported on VMware ESXi 9.0</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8c4f7b25cd054f74b804a271ef25619f" version="13f5a57fd4bb451c85bc523068e5002b" lucid_version="smartpqi.rhel10_x86_64.rpm@2.1.38-022__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.1.38-022" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC drop.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC drop.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.1.36-026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added a timeout value to RAID path requests to physical devices.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added a timeout value to RAID path requests to physical devices.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where the kernel call trace when calling smp_processor_id() in real-time kernel.&nbsp;</li>
	<li>Fixed an issue of accessing NULL SCSI device pointer caused by a rare race condition.&nbsp;</li>
	<li>Fixed a system crash issue caused by a divide-by-zero condition.&nbsp;</li>
	<li>Fixed an issue where after a device has been removed, it&#39;s possible for a previously scheduled work item for a LUN reset to be executed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where the kernel call trace when calling smp_processor_id() in real-time kernel.&nbsp;</li>
	<li>Fixed an issue of accessing NULL SCSI device pointer caused by a rare race condition.&nbsp;</li>
	<li>Fixed a system crash issue caused by a divide-by-zero condition.&nbsp;</li>
	<li>Fixed an issue where after a device has been removed, it&#39;s possible for a previously scheduled work item for a LUN reset to be executed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="20e8272651c0421db480e44b69d4a77a" version="46c907c739294cb58c63e50b8a0c7181" lucid_version="trinity.asr.win2025.x64@4.7.2.0(G)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="4.7.2.0" revision="G" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.7.2.0 (F)" revision="F" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="e6bb5c297d78402ab079f188773b5efc" version="72ffec95c5fc40e8a73c7c76603092c0" lucid_version="mellanox_winof2.w2k22@26.1.27016.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="26.1.27016.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.7.26882.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an issue where the Relaxed Ordering feature was incorrectly disabled when using firmware versions newer than XX.36.2024.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an issue where the Relaxed Ordering feature was incorrectly disabled when using firmware versions newer than XX.36.2024.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5373c16feb6444f5add5e7de11e158d0" version="2ce09f2fe00643b39cb42139d3b93add" lucid_version="FWPKG-P45642-H23@28.48.1000-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="28.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="28.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="15bbffaaaa27488a8c4a494c0491d838" version="ff1d4fb514544c44b07cfd4a6f467d4d" lucid_version="U74.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4899e6b54e3941a4b9c3090a539cf6db" version="2933eb4cd94144adb521f0300cd2a420" lucid_version="Gen10P_Gen11_Storcli-sut.esxi80@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.08.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation
	<ul>
		<li>Command: storcli /cx set factory repurpose</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation
	<ul>
		<li>Command: storcli /cx set factory repurpose</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="dd380568cb3d423fbf23f2184fadff66" version="eef12f916a1c4f469868a0c2a7a4b621" lucid_version="qla2xxx.sles15.x86_64_legacy_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="10.02.14.00-k1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="270849c2dba647ceb1f5f641d466f681" version="108c2c6c505e48f1a6dd0e16f4cb61d5" lucid_version="bnxtnet.vmware90@2025.11.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2025.11.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.05.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where ESXi Datastore not seen when NPAR is enabled.</li>
	<li>This product fixes the issue where PSOD is seen when enable NPAR using 2 NICs.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where ESXi Datastore not seen when NPAR is enabled.</li>
	<li>This product fixes the issue where PSOD is seen when enable NPAR using 2 NICs.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5b36200ffa3640839369c39ca58c8134" version="21dbae1890804e0a855212de38f1588b" lucid_version="FWPKG_VO000960KXNXD_VO001920KXNZQ@HPS7__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPS7" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:square">
	<li>Disabled Latency Tolerance Reporting Feature&nbsp;</li>
	<li>Drop MCTP command when interrupted by a Function Level Reset (FLR)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:square">
	<li>Disabled Latency Tolerance Reporting Feature&nbsp;</li>
	<li>Drop MCTP command when interrupted by a Function Level Reset (FLR)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Changes have been made in the 7450 firmware HPS7 over the previous firmware release to address Uncorrectable PCIe errors that are reported as ACS violations when Function Level Resets (FLR) are issued to the drive.<br />
If this firmware is not updated, errors will be reported in HPE&rsquo;s iLO logging but there is no risk to user data or drive reliability.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Changes have been made in the 7450 firmware HPS7 over the previous firmware release to address Uncorrectable PCIe errors that are reported as ACS violations when Function Level Resets (FLR) are issued to the drive.<br />
If this firmware is not updated, errors will be reported in HPE&rsquo;s iLO logging but there is no risk to user data or drive reliability.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPS3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improvements to our out-of-band message handling to ensure robust device management capabilities</li>
	<li>Changes to improve our PCIe link compatibility as well as device reliability</li>
	<li>This firmware update is recommended as it improves our system interoperability and prevents specific scenarios that could cause the drive to become unresponsive.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improvements to our out-of-band message handling to ensure robust device management capabilities</li>
	<li>Changes to improve our PCIe link compatibility as well as device reliability</li>
	<li>This firmware update is recommended as it improves our system interoperability and prevents specific scenarios that could cause the drive to become unresponsive.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7a201554eb654a4fa5bf0b9e23666148" version="a2c5105a57a74840af432657928cad01" lucid_version="nicfwpkg_bcme_57416_2p10ocp@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixes the issue where the Firmeare update failed on BCM57416 4 MB flash cards .</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixes the issue where the Firmeare update failed on BCM57416 4 MB flash cards .</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixes the issue where the Firmeare update failed on BCM57416 4 MB flash cards .</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where iLO BMC shared &nbsp;IP on OCP NIC, link flap occurred during OS reboot.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixed the issue where the System cannot power on and IML log shows Critical Temperature Threshold Exceeded.</li>
	<li>This product fixes the issue where the Firmeare update failed on BCM57416 4 MB flash cards .</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="57ad67618acc4e6a9f909275cf7b0173" version="7fb447e067164cbfbebb3df460febad1" lucid_version="FWPKG_MB012000JZYVN_MB014000JZYVP_MB016000JZYVQ@HPD6__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This maintenance revision improves data integrity. The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This maintenance revision improves data integrity. The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ee7ffaf216e8420c95c2cb6ae599f129" version="def8bce53324460a9a2bc0375d921cbf" lucid_version="sanjac.chif.win2025.x64@4.8.0.0(F)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="4.8.0.0" revision="F" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.8.0.0 (E)" revision="E" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0300daf553df4e699178bc1f12267a1f" version="b56236f7b43f42acbc43a51ff5c3bf4d" lucid_version="Gen10P_Gen11_Storcli-sut.esxi90@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.08.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation
	<ul>
		<li>Command: storcli /cx set factory repurpose</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation
	<ul>
		<li>Command: storcli /cx set factory repurpose</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="378cdf1de2de48e7bfb2a8d18ef9e12e" version="e4a9611fcf284038abe9701bb7a836a0" lucid_version="HPE_MR216i-p_Gen11@52.36.3-6584__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="52.36.3-6584" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="52.32.3-6333" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a97585904133422cb1c458c1fa560f04" version="e7cae46baff54255a1e66a57ba732f68" lucid_version="matrox.G200eH3.win2025.x64@9.15.1.268(F)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="9.15.1.268" revision="F" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="9.15.1.268 (E)" revision="E" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="cd4b5a9c9ed9405abbc5be7a9f037870" version="04fe871c55c6491ea8373a2789ff4804" lucid_version="amsd_sles15@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.6.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="e8c4dad6ddeb44b28ee9e585282be624" version="8781f80c5fb4457c9644593baac058e4" lucid_version="qlogic_storport_x64.w2k22_rt_gen12@9.4.11.20(c)__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="9.4.11.20" revision="c" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Driver and installer Digital Signature Validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Driver and installer Digital Signature Validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="9.4.11.20 (b)" revision="b" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9e8f198dd1774302856c06d477f3cfe6" version="da1bb99c1c984309991a056a2d9eb89b" lucid_version="lpfc.sles15.x86_64_legacy_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.473.24" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="62021655cc7a4243bff40ebe6e1c46ab" version="e92f18b442974aed89680b2e601e9fcc" lucid_version="trinity.chif.win2022.x64@4.7.1.0(I)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="4.7.1.0" revision="I" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.7.1.0 (H)" revision="H" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8967fc04450e4fe2abe70a018cd5bb23" version="400e960fffdd47dc8d0f53758acf393e" lucid_version="Gen12_MR_Controller_AV2.sles16.x86_64.rpm@8.16.1.0.0-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="8.16.1.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.16.1.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Make the driver compliable with 6.14 kernel</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that SLES16 DUD (Driver Update Disk) not working</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="722704a324824ff9a85feca8189e3f95" version="05305a25c6a641c486ad47c300cf4243" lucid_version="U69.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fade5b11c713406a8e9c5f691c073fe5" version="fa5d6e746ec14924820d25c3c7f17e3e" lucid_version="ixgben.vmware90@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.11.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product VMware ESXi 9 supported.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product VMware ESXi 9 supported.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="930ec7c21c864080921bd1f4201e5153" version="ccb85424cab3452096c091c19eb8fc01" lucid_version="ssa.ubuntu@6.60.8.0(B)__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.60.8.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ae86717eaef841a7919ea42f85ca3fe7" version="1bee086dba7449cbb397135184317107" lucid_version="Gen10P_Gen11_MR_Controller.win2025@7.736.3.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="7.736.3.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 PA3)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 PA3)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="7.732.3.0 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added Azure Local 24H2 OS support</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added Azure Local 24H2 OS support</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>
	<p>Fix windows tool cert expire issue.</p>
	</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>
	<p>Fix windows tool cert expire issue.</p>
	</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9797527c9a7541debadf0b96aae4c9b3" version="9077ed7856b1465a8395a8ce4b5e9a97" lucid_version="FWPKG_MB004000GWZVT@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp;&nbsp;The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp;&nbsp;The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a9383545373b4e27bc2668b44fbabf57" version="7ac0959dc5234be68c18daed94de8ffa" lucid_version="U66.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f724e16e8d864d8e83739edbeda8aea6" version="f2111f331b0e4ccfbc192aa21f33ce37" lucid_version="U71.fwpkg@1.70_04-02-2026__fwpkg-sys_en"/>
      <revision_history>
        <revision>
          <version value="1.70_04-02-2026" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated HPE branding logo to reflect the new HPE corporate identity.</p><p>Added new RBSU option to configure the Intel Platform Communications Technology (PCT) feature for PCT-capable processors.</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel Birch Stream UPLR3 and UPLR3.5 BKC updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Addressed an issue where the system might hang at the memory initialization stage when reading crash logs.</p><p>Addressed an issue where the power-off action initiated from OneView could fail, causing the server profile not to be processed as expected.</p><p>Addressed an issue where NVMe drives could produce duplicate boot option entries after OS installation due to physical location information being incorrectly included in the structured string.</p><p>Addressed an issue where the iLO One-Time Boot option was not cleared after the selected boot target was launched.</p><p>Addressed an issue where the Intel PTAT tool could fail to launch. </p><p>Addressed an issue where system crash log–related information could not be exported from AHS logs.</p><p>Addressed an issue where system device names in RBSU might be incorrect in Japanese-language mode.</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.62_02-06-2026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Enabled Priority Core Turbo (PCT) feature support,</p>]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>This version of the System ROM contains updates aligned with Intel VROC v.9.3 updates.<p><p>Details about reported security vulnerabilities and their mitigation can be found at the following link <a href="https://support.hpe.com/connect/s/securitybulletinlibrary?language=en_US">Security Bulletin Library | HPE Support</a>.</p></p>
<p><p>To streamline content and avoid duplication across documents, starting the Gen12 platform, the UEFI Workload Based Profiles and Tuning Guide has been deprecated, and the contents of this document are now available as part of the current UEFI System Utilities User Guide for HPE Compute Gen12 servers based on iLO7 (<a href="https://hpe.com/support/UEFIG12-iLO7-UG-en">https://hpe.com/support/UEFIG12-iLO7-UG-en</a>).</p></p><p><strong>Firmware Dependencies:</strong></p>None<p><strong>Problems Fixed:</strong></p><p>Address an issue where the system reports “266 – Non-Volatile Memory Corruption Detected in the IML logs.</p><p></p><p>Address an issue where the system Asset Tag can be modified even when Asset Tag Protection is set to Locked.</p><p></p><p>Address an issue where the system logs correctable errors as Uncorrectable Machine Check Exceptions in the IML and AHS.</p><p></p><p>Address an issue where the system reports incorrect slot information for NVMe devices when the PCIe link cannot train to its maximum supported speed.  </p><p></p><p>Address an issue where the system cannot enter the RBSU menu after Intel VMD/VROC is enabled.</p><p></p><p>Address an issue where the system reports an “Unsupported DIMM Configuration error when Granite Rapids XCC processors are installed with a 2-DIMM configuration.</p><p></p><p>Address an issue where certain devices are incorrectly configured with 10-bit TLP tags even though they do not support this feature.</p><p></p><p>Address an issue where incorrect OCP E610 NIC information is displayed in the RBSU one-time boot menu and PCIe device information (DL380a).</p><p><strong>Known Issues:</strong></p>None]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="594618f566cc4fbca055e8866278e53d" version="505b38c67605470996f78145939919a0" lucid_version="ssa.win_64@6.60.8.0__sc-windows_cn,de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RC drop 6.60.8.0</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RC drop 6.60.8.0</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.50.13.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b42e83e7a63a4069bcf7067444417f68" version="b1e6f40c009f4f949ab948bf322814e0" lucid_version="Gen12_MR_Controller_AV2.win2025@8.16.4.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="8.16.4.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 (AV2 PR2 RC1)</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 (AV2 PR2 RC1)</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.15.7.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="84f4d8cbba034646b75e0fce6c455870" version="65dc772cca1e40df9753ff841de74c49" lucid_version="broadcom_nx1.win64@221.0.8.0(C)__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="221.0.8.0" revision="C" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhances to update PNP ID table（Plug and Play Identifier）</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhances to update PNP ID table（Plug and Play Identifier）</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="221.0.8.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhances to update PNP ID table. (Plug and Play Identifier)</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhances to update PNP ID table. (Plug and Play Identifier)</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6d5a1aeeae494301bad7ba821d92f1ea" version="926916f8f3d1410c9ebef618cdd35dac" lucid_version="FWPKG_MK000480GWXFF_MK000960GWXFH_MK001920GWXFK@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improve the FW about data mismatch after SPL issued.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Improve the FW about data mismatch after SPL issued.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c3dec9bf83314dd0bd404d6da0a84032" version="a5ffd532d4cc48c8abb9f680d209c26f" lucid_version="lpfc.rhel10.x86_64_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.1</p>

<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.1</p>

<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.473.24" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f85aacf9018c4fbdadcdb2b9bbf03fed" version="b8cf44de46d94ae9b0f6781016022a00" lucid_version="FWPKG_VR000480KXNXE_VR000960KXNZU_VS001920KXNXF@HPK4-rev2__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Changes and improvements that have been made in the firmware HPK4 which disable MCTP over PCIe VDM over the previous firmware.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Changes and improvements that have been made in the firmware HPK4 which disable MCTP over PCIe VDM over the previous firmware.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Changes and improvements that have been made in the firmware HPK4 which disable MCTP over PCIe VDM over the previous firmware.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Changes and improvements that have been made in the firmware HPK4 which disable MCTP over PCIe VDM over the previous firmware.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b27e4086749b43a09022b1ccf9b6e0c0" version="ee3b0819b2024a92830837bbe2407e67" lucid_version="ixgbe.rhel9@6.3.4-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.3.4-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.2.5-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added PHY-based PTP for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added PHY-based PTP for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed Intel E610 OCP Firmware OROM version display in Linux environment.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed Intel E610 OCP Firmware OROM version display in Linux environment.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d2033cd72bd449c8a4079a95ba920a5a" version="f9d5f8010bbf4a928c6a04fcb3c28c53" lucid_version="qlogic_storport_x64.w2k25_rt_gen12@9.4.11.20(e)__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="9.4.11.20" revision="e" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>

<p dir="LTR">Added support for:</p>

<p dir="LTR">Azure Local 24H2</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>

<p dir="LTR">Added support for:</p>

<p dir="LTR">Azure Local 24H2</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Driver and Installer Digital Signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Driver and Installer Digital Signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="9.4.11.20 (d)" revision="d" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">Updated&nbsp;to&nbsp;version&nbsp;9.4.11.20</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Driver and Installer Digital Signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Updated Driver and Installer Digital Signature validity</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="be42e2211b11406e90471c520058561b" version="45ea948c83474313a9a5608119c29199" lucid_version="FWPKG_MV003200LYJKH_MV006400LYJKK_VV007680LYJKF@HPK4__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release for sanitize, DRAM,DMA transfer and log page fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release for sanitize, DRAM,DMA transfer and log page fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Adding 15T model number support and MCU code fix in FW release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Adding 15T model number support and MCU code fix in FW release.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ae57ff279aab4e628b9d7923b0985d81" version="54c9602889d54d00bfe7cae757318823" lucid_version="FWPKG_MB24000JYEVE@HPD3__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RPM data missing from iLO GUI</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RPM data missing from iLO GUI</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW fix on assert, time-out, error log several fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW fix on assert, time-out, error log several fixes</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD1 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5aad4922b5f54198b1d9a8e400dcfdda" version="2a756b63d2e040fb99d837295c5421bb" lucid_version="Gen10P_Gen11_MR_Controller.sles15.x86_64.rpm@07.736.04.00-rev1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="07.736.04.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="07.736.04.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Improved handling of dma_alignment and the NVMe boundary mask for better<br />
	compatibility across kernel versions</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix an issue that NVMe device properties function lacks NULL checks before using&nbsp;request_queue-&gt;limits</li>
	<li>Fix IOMMU exceptions for some commands. The affected commands are
	<ul>
		<li>REPORT ZONES (opcode 0x95, service action 0x00)</li>
		<li>GET PHYSICAL ELEMENT STATUS (opcode 0x9E, service action 0x17)</li>
		<li>SECURITY PROTOCOL IN (opcode 0xA2)</li>
	</ul>
	</li>
	<li>Fixed an issue where zero-length ATA VPD inquiry commands were not handled<br />
	correctly and failed with a non-standard status code (0xF0)</li>
	<li>Fix SCSI host template callback for kernel 6.12</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b00b4afad66b4dd386d098e91550601d" version="980bc003e1324c0089fc7f56d030bb97" lucid_version="bnxt_roce.sles15sp6@235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0883e4abd7344c9b834b5e5585107933" version="174fd416142d4649aa647bf3a8479dc7" lucid_version="Gen10P_Gen11_StorCLI.linux@007.3604.0000.0000__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="007.3604.0000.0000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="007.3212.0000.0000 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added new OS support for&nbsp;SUSE Linux Enterprise Server 16.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added new OS support for&nbsp;SUSE Linux Enterprise Server 16.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f16d90ade0634ca7a042edbb72eabef3" version="4223c12911654ef182b8649305221d67" lucid_version="qla2xxx.rhel10.x86_64_legacy_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="10.02.14.00-k1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="01e0939311154208bbd5b8d9e5157a9c" version="ce76dc9b3af14383b0c03a0be0be0bb7" lucid_version="ssacli.win_x64@6.60.8.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RC drop 6.60.8.0</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RC drop 6.60.8.0</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.50.13.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a77901ff235c43f18df58616eefb654e" version="7319fd82a07c4804b3f42bdb8e099c29" lucid_version="FWPKG-P46603-B21@22.45.1020__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="22.45.1020" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Upgraded to version&nbsp;22.45.1020</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Upgraded to version&nbsp;22.45.1020</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="26.43.1014" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Upgraded to version&nbsp;26.43.1014</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Upgraded to version&nbsp;26.43.1014</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3ac61ed209fd49fb908341fa7b77c3ea" version="bca28cc15a484d30b263b703e9e833ce" lucid_version="ssaducli.win_x64@6.60.8.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RC drop 6.60.8.0</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>RC drop 6.60.8.0</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.50.13.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4f647319868f48cbaf207ad5f8a354e4" version="d4becc904fc14b5d9220f7bff038421b" lucid_version="intel_lkv.w2k25@1.6.25.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.6.25.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.4.73.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="58259b45dec7469580dfbddb76171768" version="36a348b50cb5497993fd8778729f6c78" lucid_version="ixgbevf.sles15@5.2.2-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="5.2.2-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="5.1.6-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an intermittent traffic failure issue from a virtual function.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an intermittent traffic failure issue from a virtual function.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="248b9fc15e184cfd81372011cd8ee662" version="b3086f55b95f443ba95347b850ffd9ae" lucid_version="qla2xxx.rhel9.x86_64_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="10.02.14.00-k1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b8cab2acffab4f63833f5213954deee9" version="88c91b35200f48c9859426ecf3d2836f" lucid_version="HPE_MR416i-p_Gen11@52.36.3-6584__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="52.36.3-6584" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 Aero PR11 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="52.32.3-6333" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>DMTF PLDM Redfish Device Enablement enhancements
	<ul>
		<li>Redfish Volume Transformation Support
		<ul>
			<li>POST #Volume.ChangeRAIDLayout: RAID Layout Change. Change in the RAID Layout is achieved by providing the target RAIDType and the list of the drives in the input JSON body.</li>
			<li>POST #Volume.ChangeRAIDLayout: Resize. ChangeRAIDLayout can be used to resize the volume by adding new Unconfigured Good drives without changing the RAIDType. In such cases RAIDType must not be provided in the input JSON body but the full drive list must be provided accordingly.</li>
			<li>PATCH Volume[CapacityBytes]: This operation is used for resizing the volume when there is unused size available in the volume. There is no scope for adding any new drives here</li>
			<li>POST #Volume.CheckConsistency: This operation starts Consistency Check operation on the volume. No input is expected for this operation.</li>
		</ul>
		</li>
		<li>Redfish Metrics GET Support
		<ul>
			<li>StorageControllerMetrics: UncorrectableECCErrorCount, CorrectableECCErrorCount, CorrectableParityErrorCount, StateChangeCount</li>
			<li>PortMetrics: SAS.InvalidDwordCount, SAS.LossOfDwordSynchronizationCount, SAS.RunningDisparityErrorCount, PCIeErrors.CorrectableErrorCount, PCIeErrors.FatalErrorCount, PCIeErrors.NonFatalErrorCount</li>
			<li>Each counter can hold a value up to 65535. Once the counter reaches the maximum value the value is not reset.</li>
			<li>Metrics are cleared when user performs Controller NVRAM clear or Redfish ResetToDefaults.ResetAll.</li>
		</ul>
		</li>
	</ul>
	</li>
	<li>Add support for users to clear NVRAM using MRSA and storcli Factory Repurpose operation.
	<ul>
		<li>Clear NVRAM operation is not allowed if there is any configuration present on the controller or if there is any pinned cache.</li>
		<li>After clearing NVRAM, controller FW performs Online Controller Reset (OCR). If for some reason OCR cannot be performed, then the user will be notified to perform a system reboot.</li>
		<li>The Clear NVRAM operation is equivalent to Redfish ResetToDefaults.ResetAll operation functionally.</li>
	</ul>
	</li>
	<li>Change the backplane bay count information to the actual bay that is connected to controller. For non-hotplug configuration, controller always shows 16 bays.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00143124en_us Advisory: HPE MR Gen11 Controller - MR Gen11 Controllers on HPE Gen11 Servers May Fail to Generate &quot;WriteCacheDataLoss&quot; in the IML</li>
	<li>Fix a00148035en_us Advisory: HPE MR Gen11 Controllers - The Bay And Box NVMe Drive Location Is Not Displayed in the One-Time Boot Menu</li>
	<li>Fix an issue that Read/Write transfers over 128KB on LTO fail in Linux OS</li>
	<li>Fix an issue that Backup Exec doesn&rsquo;t work with LTO</li>
	<li>Fix an issue that controller might be dropped by the iLO in server boot up when there are 240 Logical Drives are configured</li>
	<li>Fix a rare issue that server health shows critical temporally when remove drive continuously.</li>
	<li>Fix an issue that unexpected PCIConfiglink page events, Task management to the virtual SES device time out messages are logged in snapdump</li>
	<li>Fix an issue that Slot capable protocol is missing for empty bay</li>
	<li>Fix an issue that Link Speed for LTO connected to controller shows Unknown</li>
	<li>Fix an issue that Request Sense command causes task management on the drive where sanitization is in progress.</li>
	<li>Fix an issue that Redfish PATCH StorageController[ControllerRates] silently sets random values when the value beyond 255 is used.</li>
	<li>Fix an issue that incorrect controller error event may be logged when controller is configured as passthrough and do vm reboot</li>
	<li>Fix an issue that active width, current speed are wrong in Redfish Fabric port when two backplanes connected to same storage port.</li>
	<li>Fix a rare issue that NVMe drive link status may fail after reboot&nbsp;</li>
	<li>Fix a rare issue that controller may assert when there are multiple drives removed and inserted in a short time</li>
	<li>Fix an issue that sanitize percentage does not progress on SATA drives if there is SATA passthrough command running</li>
	<li>Fix an issue that sanitize percentage does not progress on NVMe drives</li>
	<li>Fix a rare issue that IO timeout and device reset may occur with stress test of Read/Write and Non-Read/Write commands</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="96378e2061d845f3850110a4f2a6ae57" version="d84f28affb894a66b91e00fd038e62d1" lucid_version="trinity.chif.win2025.x64@4.7.2.0(G)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="4.7.2.0" revision="G" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility&nbsp;dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility&nbsp;dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.7.2.0 (F)" revision="F" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="015fb436dd2948789e37f0213e4e8ee0" version="776acf16b7cb4651b5fbd3e97d099240" lucid_version="Gen10P_Gen11_MR_Controller.rhel10.x86_64.rpm@07.736.04.00__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="07.736.04.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2f9cefc3934e4e93835fb42cb71a4161" version="739e07fb385e4106b6105dff3be1990c" lucid_version="ssaducli.ubuntu@6.60.8.0(B)__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.60.8.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>Modified the SSACLI component version format to meet the new requirement from VMware ESXi for 9.1</li>
	<li>Added spare type decoding in Array Diagnostic Utility (ADU) reports to indicate whether a logical drive uses dedicated or auto-replace spares</li>
	<li>Modified the default strip size for NVMe drives based on the Maximum Data Transfer Size (MDTS), and tools will set the default strip size to the minimum supported MDTS value when creating or migrating a logical drive</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2432f89456d4439e8b4887185dba490d" version="85fb6e7602004da28173b4dbc52c1cc6" lucid_version="intel_lkv_vf.w2k25@2.3.7.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="2.3.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.3.2.4 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6a4f9209b5474891beaf50886f41470e" version="90afaf91d183433597dbb4d307804d85" lucid_version="nicfwpkg_intel_e810_xxv4t@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3126d8d47de5417a878b30ed83f0673f" version="d532712810154a58b955eafff4cbb3c6" lucid_version="Gen10P_Gen11_MR_Controller.win2022@7.736.3.0__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="7.736.3.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 PA3)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 PA3)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="7.732.3.0 (B)" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix windows tool cert expire issue.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d9d151c798d94a31a9d263cef309ab70" version="a7e83a973d674a43902b49a6eef62041" lucid_version="ubuntu2404amsd@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Instead of using sed command, using awk command to fetch the right column name</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Instead of using sed command, using awk command to fetch the right column name</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.6.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Instead of using sed command, using awk command to fetch the right column name</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Instead of using sed command, using awk command to fetch the right column name</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f4715848575b4c2a8afe1c481f6415ae" version="d256859bf1274ee0b892731c2a98d9f9" lucid_version="emulex_storport_x64.w2k25_rt_gen12@14.4.624.1(b)__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.624.1" revision="b" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.624.1</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>

<p>&nbsp;</p>

<p>Added following Enhancement:</p>

<p>Reverted IRQ count to 128 from 240 in inf file to avoid resource constraints on low end server configurations</p>

<p>Added support for Azure local 24H2</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.624.1</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>

<p>&nbsp;</p>

<p>Added following Enhancement:</p>

<p>Reverted IRQ count to 128 from 240 in inf file to avoid resource constraints on low end server configurations</p>

<p>Added support for Azure local 24H2</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.624.1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.624.1</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>

<p>&nbsp;</p>

<p>Added following Enhancement:</p>

<p>Reverted IRQ count to 128 from 240 in inf file to avoid resource constraints on low end server configurations</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to driver version&nbsp;14.4.624.1</p>

<p>The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.&nbsp; Use this command:</p>

<p>&nbsp;&nbsp;&nbsp; elxdrvr-fc-version.exe /q2 extract=2</p>

<p>The extracted files are located:</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version</p>

<p>Each kit folder has subsequent architecture folders with subsequent OS folders.&nbsp; For example,</p>

<p>&nbsp;&nbsp;&nbsp; C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022</p>

<p>&nbsp;</p>

<p>Added following Enhancement:</p>

<p>Reverted IRQ count to 128 from 240 in inf file to avoid resource constraints on low end server configurations</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ffe236b3c9414886ad6bebd19a87b8d3" version="e04c7094cab24fe2852e7a023aa61fde" lucid_version="nicfwpkg_bcme_57608_2p100@235.1.164.14-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="13f7ba6cc0a0488cb274ce960d482e1c" version="058416468302498dbb85bd9fa6c9c6bf" lucid_version="FWPKG_VO001920KYDMT_VO003840KYDMV_MO001600KYDMU@HPK6__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>FW HPK5 may cause Uncorrectable Machine Check Exception (UMCE) to occur. It is recommended to update FW to HPK6.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>FW HPK5 may cause Uncorrectable Machine Check Exception (UMCE) to occur. It is recommended to update FW to HPK6.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK5" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Prioritize disabling Non-Fatal Error reporting at the beginning of FLR processing</li>
	<li>Fix known FW bug PI/CI indexing issue</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Prioritize disabling Non-Fatal Error reporting at the beginning of FLR processing</li>
	<li>Fix known FW bug PI/CI indexing issue</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2469c1c22cec4fe2bad4ee9c59e235c3" version="21fa87f35a284370a9bc675575e955c0" lucid_version="PICGen12.FWPKG@1.1.2__fwpkg-power_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.1.2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>

<p>None</p>

<p><strong>Firmware Dependencies:</strong></p>

<p>None</p>

<p><strong>Enhancements/New Features:</strong></p>

<p>Enhanced the accuracy of power value displayed in iLO Web where the average power value should be equal to or below the power cap value.</p>

<p><strong>Known Issues:</strong></p>

<p>None</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>Important Notes:</strong></p>

<p>None</p>

<p><strong>Firmware Dependencies:</strong></p>

<p>None</p>

<p><strong>Enhancements/New Features:</strong></p>

<p>Enhanced the accuracy of power value displayed in iLO Web where the average power value should be equal to or below the power cap value.</p>

<p><strong>Known Issues:</strong></p>

<p>None</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2ed4fb56e81f45b0b8ae601a61b78e6c" version="417cb571a27e44a5b9cd0ee1e069f9cc" lucid_version="bnxt.sles15@1.10.3-235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="1.10.3-235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.10.3-235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fcbfe734454648628f4d8c3848d7db3e" version="cfb3c1b576564b7fafa4c9bdcc52cffb" lucid_version="FWPKG_MO001600PXVRU_VO003840PXVRR_VO007680PXVRT@HPD3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>To fix chip kill -The host IO CMD may get timed out and shows SNS=04/40/C2.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>To fix chip kill -The host IO CMD may get timed out and shows SNS=04/40/C2.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD2" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Added fix to address a rare case where drive health queries can trigger false drive predictive failure.</li>
	<li>For more information, refer to HPE Customer Advisory at the following URL: <a href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us" id="menur2cjc" rel="noreferrer noopener" target="_blank" title="https://support.hpe.com/hpesc/public/docdisplay?docid=emr_na-a00146367en_us">https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us</a> which will be active on 20-Mar-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Added fix to address a rare case where drive health queries can trigger false drive predictive failure.</li>
	<li>For more information, refer to HPE Customer Advisory at the following URL: <a href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us" id="menur2cjc" rel="noreferrer noopener" target="_blank" title="https://support.hpe.com/hpesc/public/docdisplay?docid=emr_na-a00146367en_us">https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00146367en_us</a> which will be active on 20-Mar-2025.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6e3ebe76de054c89aca30ca4b9935195" version="2d31ba792a4e4c4da2e3da6f05f69bb2" lucid_version="nicfwpkg_intel_e830_xxv8ocp@1.22__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.22" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="01dd36b9ad8145f48edf876566d56fdb" version="66bb24ccc3574c59912c4b91169c0d8e" lucid_version="FWPKG-S2A69A@26.45.1020__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="26.45.1020" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Upgraded to version&nbsp;26.45.1020</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Upgraded to version&nbsp;26.45.1020</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6671e1ba66ed4626bc090904b85d669d" version="8983181b204c4044882308f464927ff5" lucid_version="FWPKG_MB010000JWZHA_MB012000JWZHB_MB014000JWZHC@HPD4__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="83e1148b5c0344d788a4b7811addf33e" version="721e34d82ea94443bf252a90810a7e75" lucid_version="intel_lkv_vf.w2k22@2.3.7.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="2.3.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.3.2.4 (C)" revision="C" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product added WoL support for Intel E610 OCP.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed system freeze during the E610 adapter disablement when maximum number of VFs is allocated.</li>
	<li>This product fixed driver failed after booting installation media with updated driver via UEFI &amp; Legacy.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3757faf2593745dba2aa0de24a538cf3" version="51d4119d39cb4c7e857960beb3ea63f2" lucid_version="FWPKG-P79115-H21@40.48.1000-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="40.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="40.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following changes and new features have been inlcuded in version 40.48.1000:</strong></p>

<ul>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>Introduces a DOCA PCC device API that enables retrieval of the DSCP value associated with a PCC flow when PCC operates in QP mode (for example, when&nbsp;ROCE_CC_SHAPER_COALESCE_P1=2&nbsp;and&nbsp;ROCE_CC_SHAPER_COALESCE_P2=2&nbsp;are configured via mlxconfig).</li>
	<li>The system-wide limit for DPA processes has been reduced to&nbsp;30. This total includes both user processes across all GVMIs and internal ProgCC processes. The&nbsp;max_dpa_processes&nbsp;value reported to the user is calculated as:&nbsp;max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events. Refer to DSP0248 for details.</li>
	<li>Added a validation step during firmware updates to detect whether the BMC is asserting write protection, helping diagnose and prevent update failures.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support&nbsp;set&nbsp;and&nbsp;copy&nbsp;actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field,&nbsp;TUNNEL_HDR_DW_2&nbsp;(0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>mlxlink&nbsp;show_links&nbsp;now reports the full PCIe identifier (domain/segment + BDF), improving device-to-link mapping and avoiding ambiguous/duplicate BDF entries on multi-domain systems.</li>
	<li>Implemented IB extended port telemetry counters via the NSM Type 1 Get Port Telemetry Counters command, adding counters 19 and 20: NSM_LINK_ERROR_RECOVERY_COUNTER_CNTR_ID and NSM_LINK_DOWNED_COUNTER_CNTR_ID.</li>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues&nbsp;have been fixed in version 40.48.1000:</strong></p>

<ul>
	<li>In certain configurations with the ConnectX-8 PCIe switch enabled, downstream devices (including GPUs) might not be detected and could drop from the PCI bus, with GPU sensors/properties reporting NA. This was caused by the device not receiving the required PERST# assertion during initialization, and was seen only when PCIe settings were manually modified via mlxconfig (e.g., restricting link speed/width or ASPM on specific PCI buses).</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which could cause the DPA kernel to hang during FLR.</li>
	<li>Link failures were occasionally observed at PAM4 speeds over optical interfaces in rare cases.</li>
	<li>An issue in the User Debugger &ldquo;query caps&rdquo; where it returned only the number of capabilities, not the capability bitmap.</li>
	<li>CR dumps could time out when accessing xpl_top addresses across all three pcores.</li>
	<li>The Virtio and NVMe EMU_MNG settings were exposed incorrectly, which could cause confusion when using mlxconfig.</li>
	<li>The PHY LED could show green during the initializing state when active speed was set to full speed. In IB mode, the initializing-state LED should be amber only.</li>
	<li>On multi-PF-per-port systems, a PF FLR could impact the traffic bandwidth of other PFs on the same port.</li>
	<li>PTP could converge to an incorrect time/offset and report an inaccurate path delay.</li>
	<li>In Flit Mode, the device could become unresponsive when receiving malformed or invalid traffic from a link partner.</li>
	<li>&quot;mlxlink&quot; reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Parallel accesses to the MCIA register could return incorrect data. In some hosts running ethtool -m &lt;interface&gt; repeatedly (e.g., once per second), this could intermittently report Identifier: 0x00 (unknown/no module), causing health checks to fail.</li>
	<li>A rare attestation certificate signature formatting issue leading to an unnecessary zero byte in the &ldquo;r&rdquo; or &ldquo;s&rdquo; value.</li>
	<li>In certain Gen6 setups, RDMA READ bidirectional traffic required at least 5 QPs to reach full wire speed.</li>
	<li>An issue affecting single-process, unidirectional RDMA READ to GPU memory (4 QPs, 128KB messages) by enabling ZERO_TOUCH_TUNING_ENABLE via MLXCONFIG.</li>
	<li>An issue where probe packets might not be sent under heavy traffic.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>An intX message was sent with a Requester ID of 0, causing an ACS violation at the root port. The fix uses the correct BDF as the Requester ID instead of 0.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3435b64680a240ef985cff616421b9f8" version="58a18665274f432bb68d513de4753200" lucid_version="nicfwpkg_bcm_bcm5719@20.35.41-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="20.35.41" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="20.35.41" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where unique serial number in VPD (Vital Product Data) will be altered to a dummy serial number</li>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where unique serial number in VPD (Vital Product Data) will be altered to a dummy serial number</li>
	<li>This product fixes the issue where Failing to Obtain iLO shared NIC DHCP IP and MCTP EID Missing during Reboot.</li>
	<li>This product fixes the issue where PCI Temperature sensor might be missing intermittently causing Increase in Fan Speed<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="92ea33d10ac8425e8a37a09b1f14f44a" version="2ef3ce7b50404c2dbfc7838c07bc8a24" lucid_version="qla2xxx.rhel9.x86_64_legacy_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="10.02.14.00-k1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added Support For:</p>

<p>Red Hat Enterprise Linux 10</p>

<p>Updated Driver version&nbsp;10.02.14.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="58e30c6460374d34ab64c2a8547dafe2" version="526837a94da34ff39f8183978e99b2a5" lucid_version="nicfwpkg_intel_e810_2cq2sec@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="72b6bd7095ec40a7947f8f947956c698" version="8f615e32ccf54da4a7ac306326bb396f" lucid_version="Gen10P_Gen11_Storcli-sut.esxi91@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="242891bb48e3412db468da595765efc8" version="5240ae77df9a4bb7980865cd9ddbc87b" lucid_version="sanjac.asr.win2025.x64@4.8.0.0(F)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="4.8.0.0" revision="F" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.8.0.0 (E)" revision="E" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;supported environments</li>
	<li>Updated supported products</li>
	<li>Updated setup utility dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="dc41774861a945f28d388059e656b2ca" version="3dac84cbe13f448aa40cc30f6843f523" lucid_version="nicfwpkg_intel_e810_cq2ocp@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</li>
	<li>This product enhanced media type detection function on PHY on 100G adapter.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</li>
	<li>This product enhanced media type detection function on PHY on 100G adapter.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="a529a1b0d8b0405f80457239f0d32b29" version="8e35585af64849d9a9b92d4cb546c7b9" lucid_version="bnxt.rhel10@1.10.3-235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="1.10.3-235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.10.3-235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3c3b18c087cf4abfa2c47b59042d0c23" version="7acf4ed3c2c34b6ca53e4278f6da5fd6" lucid_version="icen.vmware91@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8fe4fa268c8c441bbc19bdade735a0d6" version="edb54981bd324f16bfd8b1962401c8a5" lucid_version="FWPKG_MB016000JXLBA_MB018000JXLAU@HPD3__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2079058db213445cb2b49d341b2df92d" version="b11e8e7c1bdc476e8fdc7209faa5cfd0" lucid_version="iavf.rhel10@4.13.20-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.13.20-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.13.16-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c013d920d5db4350b0283f4634a4df97" version="570b95e792e14a2d994ae68b730ee8fa" lucid_version="nicfwpkg_bcme_57608_2p100ocp@235.1.164.14-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.&nbsp;</li>
	<li>This product fixes the issue where OS installation failed with shared nic BCM 957508-N2 100Gb/s OCP.</li>
	<li>&nbsp;This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.&nbsp;</li>
	<li>This product fixes the issue where OS installation failed with shared nic BCM 957508-N2 100Gb/s OCP.</li>
	<li>&nbsp;This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>&nbsp;This product fixes the issue where OS installation failed with shared nic BCM 957508-N2 100Gb/s OCP.</li>
	<li>&nbsp;This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>&nbsp;This product fixes the issue where OS installation failed with shared nic BCM 957508-N2 100Gb/s OCP.</li>
	<li>&nbsp;This product fixes the issue where RDE &quot;Location&quot; property is missing under &quot;NetworkAdapter&quot; schema.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="953566d3c1ab4efe9b762b361100a259" version="4412e3e7c98649b3bd32cc53ac661f12" lucid_version="FWPKG_MO001600KZYWU_MO003200KZYXB_MO006400KZYXC@HPK5__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK5" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware provides bug fixes for the P5620/P5520.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This firmware provides bug fixes for the P5620/P5520.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="46fddc1064aa49689f5fc2bc4ced3518" version="e152fcfaa2b74c0289a535cdc073814b" lucid_version="FWPKG_MV003200LXUJK_MV006400LXUJL_VV003840LXUJE@HPK7__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK7" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance for fixing MCU,sanitize, DRAM and log page..etc.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance for fixing MCU,sanitize, DRAM and log page..etc.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK6" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes PCIe link drop, Drive detection after hot re-insert on Windows and includes other regular FW patch releases.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixes PCIe link drop, Drive detection after hot re-insert on Windows and includes other regular FW patch releases.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="7e0050d7cc724a879a45bb605213e3c8" version="4924d8e0104a4e96a2206473e4ce8b62" lucid_version="FWPKG_VR000960YYXPR@HPK2__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>RSOD issue fixed. RSOD was occurred during server power-on if enable the VROC.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>RSOD issue fixed. RSOD was occurred during server power-on if enable the VROC.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="dcff0c4699e341cf85f18eb94d85147c" version="5c2ad4196c7e42169f6d89cfef5629c4" lucid_version="tg3.rhel9@3.139w-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="3.139w-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="3.139t-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes issue where link disconnected with the latest Out-of-Box (OOB) Driver.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes issue where link disconnected with the latest Out-of-Box (OOB) Driver.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2e4ac8b988164dc087668639a95037d3" version="946679b18e0a483397d4dc7e3773f91e" lucid_version="tg3.rhel10@3.139w-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="3.139w-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="68526791858d42b69b174ffed2a35fa0" version="290bf32b748e4b8f9c4cbe3f9cfe6e6d" lucid_version="amsd_sles16@4.7.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.7.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.6.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5d636f95f482471a9bd020c928d3b4af" version="f807c9c2ce5c459197e66ec2d1b36e36" lucid_version="HPE_NS204i_Gen10P_Gen11_Gen12@1.2.14.1029(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.2.14.1029" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product resolves the issue that&nbsp;NS204i-r and NS204i-t target guid missing in secret header and xml.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product resolves the issue that&nbsp;NS204i-r and NS204i-t target guid missing in secret header and xml.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.2.14.1029" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix invalid VolumeOK event while system boot-up.</li>
	<li>Fix irrelevant Status and Conditions in rebuilding process.</li>
	<li>Fix irrelevant volume events appearing after removing the drives.</li>
	<li>Fix irrelevant drive events appearing after removing the drives.</li>
	<li>Fix irrelevant volume events appearing after replacing the drives.</li>
	<li>Fix irrelevant drive events appearing after replacing the drives.</li>
	<li>Fix irrelevant controller status after controller firmware update.</li>
	<li>Fix irrelevant controller and drive status after reset-to-default with preserving volume required.</li>
	<li>Fix corrupted storage page in iLO with some NS204i Gen10+ cards.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix invalid VolumeOK event while system boot-up.</li>
	<li>Fix irrelevant Status and Conditions in rebuilding process.</li>
	<li>Fix irrelevant volume events appearing after removing the drives.</li>
	<li>Fix irrelevant drive events appearing after removing the drives.</li>
	<li>Fix irrelevant volume events appearing after replacing the drives.</li>
	<li>Fix irrelevant drive events appearing after replacing the drives.</li>
	<li>Fix irrelevant controller status after controller firmware update.</li>
	<li>Fix irrelevant controller and drive status after reset-to-default with preserving volume required.</li>
	<li>Fix corrupted storage page in iLO with some NS204i Gen10+ cards.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="ada99fb833d94a8ba8e825827baed488" version="0c199dea1c8d415faceafdc7df41cbf7" lucid_version="ams.gen11.gen12.win.x64@4.80.0.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="4.80.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.70.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the enhancements in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the <a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1174220fe8354722a040071980d1eb37" version="42c425060451475ab163d4176929f4fe" lucid_version="mellanox_winof2.w2k25@26.1.27016.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="26.1.27016.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>TBD</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.7.26882.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an issue where the Relaxed Ordering feature was incorrectly disabled when using firmware versions newer than XX.36.2024.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an issue where the Relaxed Ordering feature was incorrectly disabled when using firmware versions newer than XX.36.2024.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="17ddd4982753427c9eac8be3bb37e260" version="3d0531102ecb4982b8848d2e844ed84a" lucid_version="trinity.asr.win2022.x64@4.7.1.0(I)__sc-windows_en"/>
      <revision_history>
        <revision>
          <version value="4.7.1.0" revision="I" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility&nbsp;dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated setup utility&nbsp;dependencies</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.7.1.0 (H)" revision="H" type_of_change="0"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Updated&nbsp;Supported Environments</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="231e2fa57546404f9e7b4f9edbb7f3b9" version="2c7a808c0ad74908928b0bee15996417" lucid_version="lpfc.rhel10.x86_64_legacy_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="2e783bb79a1d489d9f42398711c931ef" version="9e388a85f8d24360bc70316faedd83d7" lucid_version="ixgbevf.rhel10@5.2.2-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="5.2.2-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="5.1.6-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an intermittent traffic failure issue from a virtual function.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixed an intermittent traffic failure issue from a virtual function.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="000bfbde35e84381b78976b2c1748662" version="2782e9828ea24cbfb4448825ce1a9cba" lucid_version="intel_vf.w2k22@1.18.161.0__sc-windows_en,ja"/>
      <revision_history>
        <revision>
          <version value="1.18.161.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.17.63.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes an issue where the VM traffic may not working when VF driver disabled or not installed.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>This product fixes an issue where the VM traffic may not working when VF driver disabled or not installed.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="994a0b6ce04a44b9b4daabf9aed11e4c" version="74f767c43f7945eeb251b5b71675b1d5" lucid_version="iLO6.fwpkg@1.76__fwpkg-ilo_en"/>
      <revision_history>
        <revision>
          <version value="1.76" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial Build</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial Build</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Initial Build</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Initial Build</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.75" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Please&nbsp;refer to the&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007714en_us" rel="noopener noreferrer" target="_blank">iLO 6&nbsp;v1.75&nbsp;Release Notes</a>&nbsp;for the Enhancements&nbsp;included in this Release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Please&nbsp;refer to the&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007714en_us" rel="noopener noreferrer" target="_blank">iLO 6&nbsp;v1.75&nbsp;Release Notes</a>&nbsp;for the Enhancements&nbsp;included in this Release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Please&nbsp;refer to the&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007714en_us" rel="noopener noreferrer" target="_blank">iLO 6&nbsp;v1.75&nbsp;Release Notes</a>&nbsp;for the Fixes included in this Release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Please&nbsp;refer to the&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007714en_us" rel="noopener noreferrer" target="_blank">iLO 6&nbsp;v1.75&nbsp;Release Notes</a>&nbsp;for the Fixes included in this Release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b94d0b4280eb4ea0ae41d5fd3c38b589" version="a51312f359a14beca16a92b19179cb0c" lucid_version="ixgben.vmware91@2026.03.00__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9eeb0ff245dd43c78ad42320aad05c3a" version="72de1746861741ab8b5062cc500c3079" lucid_version="ixgbe.sles16@6.3.4-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.3.4-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0055efda426a4eb0935cd8a229108a26" version="9fdd802c5d11404faf456743fa8a450f" lucid_version="FWPKG_MB004000JWWQB_MB002000JWWQA@HPD8__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD8" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c73603f447664d53b84b56e38b35a86b" version="4dd9819d2a844736b3709222a082209e" lucid_version="bnxt_roce.rhel9u6@235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9b11c8b2e5814a11b64b738755f0d8ce" version="3d2e90b3dab24c458b2fd74f4d437b70" lucid_version="FWPKG_MO001600KYLEC_MO003200KYLHL_MO006400KYLHN@HPK1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="51c52bf006bd4c60b09797563ff886bf" version="5ee7637cddbb4b778e4943aa0b18c662" lucid_version="ssacli.linux.x64@6.60.8.0__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="6.60.8.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>RC drop 6.60.8.0.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>RC drop 6.60.8.0.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.50.11.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
	<li>Fixed an issue where the last failure reason was not listing on physical drives.&nbsp;</li>
	<li>Fixed an issue where SSAScripting failed to create an encrypted volume while in express local mode.&nbsp;</li>
	<li>Fixed an issue where an error/warning message was not being generated correctly while expanding a RAID 1+0 volume.&nbsp;</li>
	<li>Fixed an issue where a duplicate entry for the physical drive was displayed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed the &ldquo;Parity Initialization Method&rdquo; information displayed for non-parity RAID levels.&nbsp;</li>
	<li>Fixed an issue where users were unable to clear the controller&rsquo;s configuration when a foreign volume was present.&nbsp;</li>
	<li>Fixed an issue where a foreign-owned SED drive was being listed for array creation.&nbsp;</li>
	<li>Fixed an issue where the last failure reason was not listing on physical drives.&nbsp;</li>
	<li>Fixed an issue where SSAScripting failed to create an encrypted volume while in express local mode.&nbsp;</li>
	<li>Fixed an issue where an error/warning message was not being generated correctly while expanding a RAID 1+0 volume.&nbsp;</li>
	<li>Fixed an issue where a duplicate entry for the physical drive was displayed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="fefae5f129c9429dbe5f506829e99ac7" version="4428eb713ea64a80b9e7f49c0e6713a2" lucid_version="ixgbevf.sles16@5.2.2-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="5.2.2-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1e88e3b27b814bcdbc8dcf6390d324d1" version="4e14138c4c714237bcc8bfb333533ccd" lucid_version="UBM4_FWPKG@1.24(G)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.24" revision="G" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Support Gen12 servers.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Support Gen12 servers.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.24 (F)" revision="F" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>For Gen11 PR3 &amp; 2023 March MSB</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>For Gen11 PR3 &amp; 2023 March MSB</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="710acbec2a70445381651a2e1f3c55ab" version="1e8d6ce0a2844f278f512b54bb9813d3" lucid_version="mlnx_en_roce_mlx5.sles15sp7.x86_64.rpm@26.01__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="26.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01</strong><strong>:</strong></p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 26.01</strong><strong>:</strong></p>

<ul>
	<li>
	<p>Adds support for reporting RS-FEC histogram statistics via ethtool. These IEEE 802.3&ndash;defined histograms reveal the distribution of corrected codewords by number of symbol errors corrected per block, improving link quality diagnostics and enabling earlier detection of signal degradation.</p>
	</li>
	<li>
	<p>PTP Raw Cycle Counter Exposure&nbsp;&ndash; Extends the PTP subsystem and driver to expose the raw free-running cycle counter of PTP hardware clocks, enabling user space to obtain (cycle, system-time) pairs via new ioctls and correlate hardware cycle timestamps with host time without requiring PHC synchronization.</p>
	</li>
	<li>
	<p>TCP Header-Data Split Zero-Copy&nbsp;&ndash; Exposes header&ndash;data split to the TCP layer to enable TCP zero-copy. This allows all headers up to and including TCP to be processed in software, while payload data is DMA-transferred directly from the NIC to the GPU without CPU involvement, achieving true zero-copy.</p>
	</li>
	<li>
	<p>PCIe Congestion Event Counters&nbsp;&ndash; PCIe congestion events are events generated by the firmware when the device side has sustained PCIe inbound or outbound traffic above certain thresholds. This feature adds support for receiving and exposing such events as ethtool counters.</p>
	</li>
	<li>
	<p>PH and Steering Tags Support&nbsp;&ndash; Enables the device to provide &quot;hints&quot; indicating where MR TLPs should be processed in system memory.</p>
	</li>
	<li>
	<p>InfiniBand Service Record Resolution&nbsp;&ndash; Introduces APIs that translate an InfiniBand service name or ID into destination address details and allow querying that resolved IB addressing information.</p>
	</li>
	<li>
	<p>IPsec Offload for Active-Passive Bonding&nbsp;&ndash; Active-passive bonding aggregates multiple network devices into a single logical interface for higher redundancy. While bonding already supported IPsec offload, this completes full support by adding correct IPsec GSO offload and fixing several race conditions around failover.</p>
	</li>
	<li>
	<p>PSP Security Protocol&nbsp;&ndash; PSP Security Protocol support is now integrated into the core subsystem, with corresponding support implemented in the mlx5 driver. This enables mlx5 devices to recognize and handle PSP-secured traffic using the common core infrastructure.</p>
	</li>
	<li>
	<p>DOCA-Host Universal doca-sosreport Enablement&nbsp;&ndash; Adds doca-sosreport to all DOCA-Host profile packages (RoCE, OFED, Networking, and All) so the same support data collection tool is always available, regardless of which DOCA flavor is installed. It standardizes how system and DOCA-related diagnostics are gathered (e.g., host OS details, driver/module status, configuration, and relevant logs), making it faster and more consistent to capture troubleshooting bundles for analysis and support.</p>
	</li>
	<li>
	<p>Transition to Upstream DPDK Sourcing and Dependencies (DPDK 25.11+)&nbsp;&ndash; As DOCA transitions from MLNX_DPDK to upstream DPDK, all package dependencies switch to the upstream versions, and DPDK sources should be pulled from the official upstream repository, starting with DPDK 25.11 and tracking the latest releases from there.</p>
	</li>
	<li>
	<p>Querying Effective VF Bandwidth when in LAG Mode&nbsp;&ndash; Currently, the mlx5 driver reports only the parent function&#39;s link speed to VFs, with no way to retrieve the VF&#39;s effective bandwidth in LAG and MPESW setups. As a result, user space and upper-layer software cannot obtain accurate bandwidth information, which can lead to suboptimal traffic decisions. This new capability allows user space applications to query the effective port speed and receive real-time notifications when it changes. In LAG configurations, each mlx5 port reports the aggregated transmit bandwidth available to it.</p>
	</li>
	<li>
	<p>Extended DCB Traffic Class (TC) Rate Limiting&nbsp;-&nbsp;Extended DCB Traffic Class (TC) Rate Limiting, significantly increases the maximum configurable TC bandwidth on high-speed NICs. Previously, the TC max-rate field was limited to 8 bits, capping the value at 255 Gbps. With compatible firmware, the mlx5 driver now supports TC rate limits up to 65,535 Gbps (&asymp; 6.5 Tbps) through capability detection, while maintaining backward compatibility on legacy hardware.</p>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 26.01:</strong></p>

<ul>
	<li>An issue on RHEL systems where installing chkconfig after mlnx-ofa_kernel (pulled in by packages such as doca-ofed and doca-host) could fail during installation. In this sequence, chkconfig could be installed indirectly as a dependency of a package that places init scripts under /etc/init.d, but the install would error out because /etc/init.d already existed as a directory (whereas chkconfig expects to manage it as a symlink). This fix prevents the /etc/init.d directory/symlink conflict that caused the RPM unpacking failure.</li>
	<li>In LAG mode, a firmware reset race could cause the driver to hang during unload while waiting for UMR completion. The fix ensures sys_error notifications are registered early and kept through device unregister so error events reach the bond device during teardown.</li>
	<li>Soft lockup warnings that could occur while releasing large UMEMs by periodically yielding the CPU during the release flow.</li>
	<li>A kernel crash that could occur if the devlink userspace process was terminated while switching the device to switchdev mode.</li>
	<li>Devlink operations were not synchronized with fw_reset, which could lead to various failures. Added a mechanism to coordinate fw_reset with devlink operations.</li>
	<li>The driver could incorrectly initialize polling-only CQs (e.g., ASO CQs), allowing them to receive EQ interrupts in rare cases. The CQ initialization flow was updated to prevent interrupts for polling-only CQs.</li>
	<li>An overflow issue where the max-rate value was stored in a unsigned 8-bit integer type , causing values above 255 to wrap (e.g., 257 became 1).</li>
	<li>An issue that prevented using more than 8 cores to set SF CPU affinity. This restriction has now been removed.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="25.07-0.9.7.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>The following new features and changes have been included in version 25.07-0.9.7.1:</strong><br />
&nbsp;</p>

<ul>
	<li>Hardware Steering (HWS): Enabled HWS as a secondary option for the device steering mode. If Software Steering (SWS) is not supported, HWS will be used by default, assuming it is available. Firmware Steering (FW) will now serve as the default only when both SWS and HWS are unsupported.</li>
	<li>
	<p>Hardware-Managed Flow Steering (HMFS): HMFS is a new approach to managing steering rules, where STEs are written to the ICM by hardware instead of software (as in software-managed steering). This enables a higher rate of rule insertion.</p>
	</li>
	<li>
	<p>Queue Affinity Bonding: Added support for 4-port bonding to allow users to add both p0 and p1 to a bond without requiring SSH access to the host or bringing down the driver beforehand.</p>
	</li>
	<li>
	<p>Multiple Doorbells per PF: Increased the number of doorbells from 1 to 8, distributing them in a round-robin manner across channel send and receive queues. This enhancement improves scalability on multi-core systems with high packet rates by reducing MMIO contention on doorbell addresses. In high packet-rate scenarios, Sub-NUMA Clustering is also required to maintain consistent channel packet rates.</p>
	</li>
	<li>
	<p>HQoS for Virtualization Solution: Added support for hierarchical group structures to enable multi-tier resource control, where parent groups enforce overall limits and child groups dynamically share available bandwidth. This design is essential for effective QoS enforcement, burst handling, and fair bandwidth allocation, ensuring workloads receive appropriate resources.</p>
	</li>
	<li>
	<p>Number of lanes Configuration when Auto-Negotiation is Disabled: Added support for specifying the number of lanes (protocol width) when auto-negotiation is disabled. Since each combination of speed and lane count corresponds to a unique link mode, this allows the user to select a specific link mode when auto-negotiation is off. This change aligns with a recent firmware update that requires the driver to provide a single link mode, rather than a bitmap based on the user-defined speed.</p>
	</li>
	<li>Extend ODP Statistics with Operation Count: Added the following new page-granularity counters:
	<ul>
		<li>num_page_faults: counts the number of page fault events handled</li>
		<li>num_invalidations: counts the number of page invalidation events handled</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version &nbsp;25.07-0.9.7.1:</strong></p>

<ul>
	<li>OFED installation caused CIFS to break in RHEL 8.4 and above. A dummy module was added so that CIFS will be disabled after OFED installation in RHEL 8.4 and above.</li>
	<li>Performance degradation on older kernel versions using RX cache, particularly on slower ARM CPUs with larger RX buffers. The issue was caused by the driver attempting to allocate new RX pages too quickly, leading to head-of-line blocking in the RX cache. The fix improves RX cache usage by triggering page allocation for a bulk of at least 2 WQEs, allowing the application more time to process packets and return buffers to the RX cache, thereby reducing blocking and enhancing performance.</li>
	<li>VF behavior was not aligned with /sys/class/net/&lt;interface-name&gt;/device/sriov_numvfs (silently ignore attempts to set the same number of VFs, and prevent changing the number of VFs until existing VFs are removed).</li>
	<li>On BlueField-3 devices running linux-bluefield kernel versions 5.15.0-1050 or 5.15.0-1060, a kernel crash occurred due to a NULL pointer dereference in the cls_api network scheduler.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4b7bb75be74941e8987c342978cb18f9" version="38f66438673e4c28a2393b82f5a51be5" lucid_version="nicfwpkg_bcme_57416_2p10@235.1.164.14-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixes the issue where the Firmeare update failed on 4 MB flash cards.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the transceiver temperature read from EEPROM is good but the is_temp_valid flag says it is not valid and sometimes returns 0xff through MCTP over PCIeVDM.</li>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixes the issue where the Firmeare update failed on 4 MB flash cards.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.14" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhancement enables a self-shutdown feature to prevent overheating when certain monitoring features are disabled.&nbsp;<br />
It applies only to newer hardware that originally shipped with firmware version 223.1.135.7 or higher and is not enabled on earlier revisions.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixes the issue where the Firmeare update failed on 4 MB flash cards.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where the firmware version details failed to update and the card showed as not operational after upgrading BCM5741x adapters&nbsp;</li>
	<li>This product fixes the issue where failed to detect a 10GBASE-LR SFP+ causing incorrect defaults and a link failure.</li>
	<li>This product fixes the issue where the adapter is unable to establish link after rebooting when using the &ldquo;HPE 10GBASE-T SFP+ 30m RJ45 Transceiver&rdquo; HPE PN 813874-B21 with vendor PN SP7053-HPE.</li>
	<li>This product fixes the issue where the Firmeare update failed on 4 MB flash cards.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8f24173ef2e740d2b110bb710e861366" version="c34ffdfde0b2461ea76af03f721fd3e2" lucid_version="Gen10P_Gen11_Gen12_hpemrsa.rhel9.sles15.sles16@8.16.13.0-rev1__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="8.16.13.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Support MR200, MR400 and MR900 controllers</li>
	<li>Enhance the MRSA Bypass Authentication mechanism so that the configuration is<br />
	allowed only when logged in as an administrator or root</li>
	<li>Removed the Sanitize Secure Erase option from MRSA for SED drives, as SEDs<br />
	support only Cryptographic Erase&nbsp;</li>
	<li>Return error when enabling encryption with 256 characters for Security Key Identifier in<br />
	Drive Security setting</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Support MR200, MR400 and MR900 controllers</li>
	<li>Enhance the MRSA Bypass Authentication mechanism so that the configuration is<br />
	allowed only when logged in as an administrator or root</li>
	<li>Removed the Sanitize Secure Erase option from MRSA for SED drives, as SEDs<br />
	support only Cryptographic Erase&nbsp;</li>
	<li>Return error when enabling encryption with 256 characters for Security Key Identifier in<br />
	Drive Security setting</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00155532en_us Advisory: HPE MR Storage Administrator (MRSA) - The MRSA&nbsp; Application Fails To Launch In SUSE Linux Enterprise Server (SLES) 16 After A Server&nbsp;Reboot</li>
	<li>Fix an issue that MRSA return &quot; Error Code 5002 Invalid URI Parameter&quot; when selecting&nbsp;Continuously in Schedule Consistency Check setting</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00155532en_us Advisory: HPE MR Storage Administrator (MRSA) - The MRSA&nbsp; Application Fails To Launch In SUSE Linux Enterprise Server (SLES) 16 After A Server&nbsp;Reboot</li>
	<li>Fix an issue that MRSA return &quot; Error Code 5002 Invalid URI Parameter&quot; when selecting&nbsp;Continuously in Schedule Consistency Check setting</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="8.16.13.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Support MR200, MR400 and MR900 controllers</li>
	<li>Enhance the MRSA Bypass Authentication mechanism so that the configuration is<br />
	allowed only when logged in as an administrator or root</li>
	<li>Removed the Sanitize Secure Erase option from MRSA for SED drives, as SEDs<br />
	support only Cryptographic Erase&nbsp;</li>
	<li>Return error when enabling encryption with 256 characters for Security Key Identifier in<br />
	Drive Security setting</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Support MR200, MR400 and MR900 controllers</li>
	<li>Enhance the MRSA Bypass Authentication mechanism so that the configuration is<br />
	allowed only when logged in as an administrator or root</li>
	<li>Removed the Sanitize Secure Erase option from MRSA for SED drives, as SEDs<br />
	support only Cryptographic Erase&nbsp;</li>
	<li>Return error when enabling encryption with 256 characters for Security Key Identifier in<br />
	Drive Security setting</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00155532en_us Advisory: HPE MR Storage Administrator (MRSA) - The MRSA&nbsp; Application Fails To Launch In SUSE Linux Enterprise Server (SLES) 16 After A Server&nbsp;Reboot</li>
	<li>Fix an issue that MRSA return &quot; Error Code 5002 Invalid URI Parameter&quot; when selecting&nbsp;Continuously in Schedule Consistency Check setting</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00155532en_us Advisory: HPE MR Storage Administrator (MRSA) - The MRSA&nbsp; Application Fails To Launch In SUSE Linux Enterprise Server (SLES) 16 After A Server&nbsp;Reboot</li>
	<li>Fix an issue that MRSA return &quot; Error Code 5002 Invalid URI Parameter&quot; when selecting&nbsp;Continuously in Schedule Consistency Check setting</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6ae43265b51b435494ee88fb571a2899" version="66843d04b7dd4718885f3a4ea87ab2d6" lucid_version="qla2xxx.sles16.x86_64_gen12@10.02.15.00-k1__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="10.02.15.00-k1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Updated Driver version&nbsp;10.02.15.00-k1</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b04dfd2901b740109ffc56eef8ba366b" version="c8ad3937cc594d4a86fa403f67b9d4b8" lucid_version="Gen12_MR_Controller_AV2.esxi9.1_bundle@2026.04.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.04.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="c549eb5726da4e0ab54cbcdd6abecebd" version="66e0ee09018e463c9b0da88f6f3702f5" lucid_version="bnxt.rhel9@1.10.3-235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="1.10.3-235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="1.10.3-235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="29b23e8f7b0d4dbf97ddc41ea0425103" version="12e10145ad2c40a5aeb104112fcffe11" lucid_version="FWPKG_MB020000JXMVU@HPD1(B)__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD1" revision="B" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPD1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>An error was found in the queue fullhandling process that results in the FUA bit not getting properly set, which could lead to the drive self-initiated reset</li>
	<li>The FW fix is to resolve the handling of FUA bit during the queue full handling process has been implemented</li>
	<li>The FW was confirmed to resolve the issue of drives resetting under queue full handling situations.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>An error was found in the queue fullhandling process that results in the FUA bit not getting properly set, which could lead to the drive self-initiated reset</li>
	<li>The FW fix is to resolve the handling of FUA bit during the queue full handling process has been implemented</li>
	<li>The FW was confirmed to resolve the issue of drives resetting under queue full handling situations.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8adb0ce7a5bc4820ace9651b574ccdf3" version="1c191606f72f49d7b71717492a0d489f" lucid_version="Gen12_StorCLI_AV2.ubuntu@008.0016.0000.0011__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="008.0016.0000.0011" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 PR2 RC1 drop</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>8.16 PR2 RC1 drop</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="008.0015.0000.0011" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="0736c8a5b1e44034a251e0cf10f7d121" version="f988993a31af4c38a6a1530152a2f451" lucid_version="FWPKG_EG001800JWJNR_EG002400JWJNT_EG002400MXJQT@HPDB__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPDB" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This Firmware version adds compatibility with the latest NAND generation for continuity of supply.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This Firmware version adds compatibility with the latest NAND generation for continuity of supply.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPDA" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="332a1cff050e45b999d3c0f17ade482b" version="f1eb364b44104b1681f2888a5aa237ce" lucid_version="bnxt_roce.sles15sp7@235.1.164.14__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="235.1.164.14" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="235.1.164.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:disc">
	<li>This product fixes the issue where 10Gb SFP (SP7053-HPE) adapters are unable to establish a link after rebooting with BCM 57504 and 5741x adapters</li>
	<li>This product fixes the issue where BCM5741x NICs no longer connect after firmware 228.x FW with 10Gb-RJ45 Transceivers</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6d646143d845471b959d65babb13943e" version="5a3243ff398440baa049cf99470fb928" lucid_version="emulex_32G_64GFC_FW_Gen12@14.4.731.12-rev1__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="14.4.731.12" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellpadding="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Universal Boot Image</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Boot Bios</strong></p>
			</td>
		</tr>
		<tr>
			<td>
			<p dir="LTR">HPE SN1620E 32Gb Dual Port Fibre Channel Host Bus Adapter</p>
			</td>
			<td>
			<p dir="LTR">32Gb</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.716.0</p>
			</td>
			<td>
			<p dir="LTR">14.4.718.0</p>
			</td>
		</tr>
		<tr>
			<td>HPE&nbsp;SN1720E 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>14.4.731.12</td>
			<td>14.4.731.12</td>
			<td>14.4.716.0</td>
			<td>14.4.718.0</td>
		</tr>
	</tbody>
</table>

<p>Added Following&nbsp;Enhancements:</p>

<p>[RedFish]:HPE specific SFP Data - Predicted days for non working stage</p>

<p>[Redfish]:&nbsp;API to read SFP Data</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellpadding="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Universal Boot Image</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Boot Bios</strong></p>
			</td>
		</tr>
		<tr>
			<td>
			<p dir="LTR">HPE SN1620E 32Gb Dual Port Fibre Channel Host Bus Adapter</p>
			</td>
			<td>
			<p dir="LTR">32Gb</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.716.0</p>
			</td>
			<td>
			<p dir="LTR">14.4.718.0</p>
			</td>
		</tr>
		<tr>
			<td>HPE&nbsp;SN1720E 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>14.4.731.12</td>
			<td>14.4.731.12</td>
			<td>14.4.716.0</td>
			<td>14.4.718.0</td>
		</tr>
	</tbody>
</table>

<p>Added Following&nbsp;Enhancements:</p>

<p>[RedFish]:HPE specific SFP Data - Predicted days for non working stage</p>

<p>[Redfish]:&nbsp;API to read SFP Data</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Fixed the following:</p>

<p>SPDM - Get Certificate response returns out of bound values</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Fixed the following:</p>

<p>SPDM - Get Certificate response returns out of bound values</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.731.12" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellpadding="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Universal Boot Image</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Boot Bios</strong></p>
			</td>
		</tr>
		<tr>
			<td>
			<p dir="LTR">HPE SN1620E 32Gb Dual Port Fibre Channel Host Bus Adapter</p>
			</td>
			<td>
			<p dir="LTR">32Gb</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.716.0</p>
			</td>
			<td>
			<p dir="LTR">14.4.718.0</p>
			</td>
		</tr>
		<tr>
			<td>HPE&nbsp;SN1720E 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>14.4.731.12</td>
			<td>14.4.731.12</td>
			<td>14.4.716.0</td>
			<td>14.4.718.0</td>
		</tr>
	</tbody>
</table>

<p>Added Following&nbsp;Enhancements:</p>

<p>[RedFish]:HPE specific SFP Data - Predicted days for non working stage</p>

<p>[Redfish]:&nbsp;API to read SFP Data</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellpadding="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Universal Boot Image</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Boot Bios</strong></p>
			</td>
		</tr>
		<tr>
			<td>
			<p dir="LTR">HPE SN1620E 32Gb Dual Port Fibre Channel Host Bus Adapter</p>
			</td>
			<td>
			<p dir="LTR">32Gb</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.731.12</p>
			</td>
			<td>
			<p dir="LTR">14.4.716.0</p>
			</td>
			<td>
			<p dir="LTR">14.4.718.0</p>
			</td>
		</tr>
		<tr>
			<td>HPE&nbsp;SN1720E 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>14.4.731.12</td>
			<td>14.4.731.12</td>
			<td>14.4.716.0</td>
			<td>14.4.718.0</td>
		</tr>
	</tbody>
</table>

<p>Added Following&nbsp;Enhancements:</p>

<p>[RedFish]:HPE specific SFP Data - Predicted days for non working stage</p>

<p>[Redfish]:&nbsp;API to read SFP Data</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Fixed the following:</p>

<p>SPDM - Get Certificate response returns out of bound values</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Fixed the following:</p>

<p>SPDM - Get Certificate response returns out of bound values</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f3f8a4081d78499e9a2dd9c8d9fb4059" version="7ba069824fd74ad0839f78daf18a16bb" lucid_version="nicfwpkg_intel_e810_cq2@4.91__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="4.91" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.90" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</li>
	<li>This product enhanced media type detection function on PHY on 100G adapter.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>This product adds Automatic Link on Startup option under the NIC Configuration in HPE RBSU menu.</li>
	<li>This product enhanced media type detection function on PHY on 100G adapter.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This product fixed PXE Boot does not work when MS secured-core enabled with HPE ProLiant Gen11 AMD platform server.</li>
	<li>This product fixed Link Speed selection under NIC Configuration in HPE RBSU menu.<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="94c09025ee214a6993489ac1827b2aac" version="eb345686a3294f2c9da85a025bc73c14" lucid_version="qlogic_32G_64G_FC_FW_Gen12@02.11.13__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="02.11.13" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>MBI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
	</tbody>
</table>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>MBI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.13</td>
			<td>09.15.19</td>
			<td>7.39</td>
		</tr>
	</tbody>
</table>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="02.11.11" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>MBI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
	</tbody>
</table>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p dir="LTR">This Firmware package contains following firmware versions:</p>

<table border="1" cellspacing="1">
	<tbody>
		<tr>
			<td>
			<p dir="LTR"><strong>Adapter</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Speed</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>MBI</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>Firmware</strong></p>
			</td>
			<td>
			<p dir="LTR"><strong>UEFI</strong></p>
			</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1610Q 32Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>32Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Dual Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
		<tr>
			<td>HPE SN1700Q 64Gb Single Port Fibre Channel Host Bus Adapter</td>
			<td>64Gb</td>
			<td>02.11.11</td>
			<td>09.15.15</td>
			<td>7.39</td>
		</tr>
	</tbody>
</table>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>Fixed the following :</p>

<p>SFP Parameters value decimal part is truncated</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>Fixed the following :</p>

<p>SFP Parameters value decimal part is truncated</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="1ba6abb4e9ff40ab8c8d2a6c0f1a1860" version="51e4703baf5541a39b8cedc42cbdbead" lucid_version="Gen10P_Gen11_StorCLI.ubuntu@007.3604.0000.0000__pubsw-linux_de,en,es,fr,it,ja"/>
      <revision_history>
        <revision>
          <version value="007.3604.0000.0000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 Alpha).</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="007.3212.0000.0000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation
	<ul>
		<li>Command: storcli /cx set factory repurpose</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Add support for users to clear NVRAM using Factory Repurpose operation
	<ul>
		<li>Command: storcli /cx set factory repurpose</li>
	</ul>
	</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="d32e3e2cf68a47998f06cb81ab591bd1" version="6b130a31fe0d448fb1f50b6eaee27c6a" lucid_version="isut.deb_x64@6.7.0.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.7.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>To Do</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>To Do</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.6.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>To Do</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>To Do</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6b091dcf4ee1419ba5b96976da014a69" version="ffa72cc6dc6f4096b3f3a27e068bf1d4" lucid_version="iavf.sles16@4.13.20-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.13.20-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="95cd675c9c4947eda03bc921bfff84c3" version="22b25cb7056247fca6f226ad387ab8a6" lucid_version="FWPKG_MB006000GWZVL_MB008000GWZVN@HPG3__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPG3" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity. &nbsp;The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity. &nbsp;The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG1" type_of_change="2"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
	<li>For more information, refer to HPE Customer Advisory at the following URL:&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00138902en_us" style="color:#0563c1; text-decoration:underline">https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00138902en_us</a>&nbsp;which will be active on&nbsp;24-April-2024.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity.&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
	<li>For more information, refer to HPE Customer Advisory at the following URL:&nbsp;<a href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00138902en_us" style="color:#0563c1; text-decoration:underline">https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00138902en_us</a>&nbsp;which will be active on&nbsp;24-April-2024.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="8796bf21e8204a0da4179cfbcd105e85" version="35defd3e087b41669dcdb71f86fc971a" lucid_version="Gen10P_Gen11_MR_Controller.rhel9.x86_64.rpm@07.736.04.00__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="07.736.04.00" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="07.732.03.00" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Verified the UNMAP command and confirmed that the Block Limits VPD page data is correct with the latest firmware.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Verified the UNMAP command and confirmed that the Block Limits VPD page data is correct with the latest firmware.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a potential mutex deadlock between reset and event handling thread. The issue may&nbsp;happen when there is heavy IO, device add/delete and SCSI rescan running in the same&nbsp;time.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a potential mutex deadlock between reset and event handling thread. The issue may&nbsp;happen when there is heavy IO, device add/delete and SCSI rescan running in the same&nbsp;time.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3d8cb748df644cf3a26ed91efafffb67" version="3ba8955d2eee4602a11446ec07e9a45c" lucid_version="smartpqi.rhel9_x86_64.rpm@2.1.38-022__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="2.1.38-022" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC drop.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>SR 2.10.2/SR 3.5.2 RC drop.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2.1.36-026" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added a timeout value to RAID path requests to physical devices.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>Added a timeout value to RAID path requests to physical devices.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where the kernel call trace when calling smp_processor_id() in real-time kernel.&nbsp;</li>
	<li>Fixed an issue of accessing NULL SCSI device pointer caused by a rare race condition.&nbsp;</li>
	<li>Fixed a system crash issue caused by a divide-by-zero condition.&nbsp;</li>
	<li>Fixed an issue where after a device has been removed, it&#39;s possible for a previously scheduled work item for a LUN reset to be executed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fixed an issue where the kernel call trace when calling smp_processor_id() in real-time kernel.&nbsp;</li>
	<li>Fixed an issue of accessing NULL SCSI device pointer caused by a rare race condition.&nbsp;</li>
	<li>Fixed a system crash issue caused by a divide-by-zero condition.&nbsp;</li>
	<li>Fixed an issue where after a device has been removed, it&#39;s possible for a previously scheduled work item for a LUN reset to be executed.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="4abcb10dd89d42588ceeee38917ac493" version="bdaa845e5c264096ad59f0f767ecc753" lucid_version="FWPKG_MB014000JXUCC@HPD4__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPD4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Remove ROM flash way from this FWPKG.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="143d62f0b8284920a58c4a72da25be26" version="7fbd8fd855be43b28e1fa6ab506cb769" lucid_version="FWPKG_MV001600KYNVA_MV003200KYNVC_MV006400KYNVD@HPK2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements, which required one time power cycle.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This is a maintenance release that contains code fix improvements and drive function enhancements, which required one time power cycle.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="5156ee2ce74d4685bd9c2931c6170220" version="4822206d12a6446a94667a7ef05ef52e" lucid_version="iavf.sles15@4.13.20-1__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="4.13.20-1" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>MarSPP2026</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="4.13.16-1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>This product enhanced the compatibility with firmware.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="90a21d24fe854b07a035a8e7bf0e3602" version="fc0c2a18b79a47bdbb56ae585710f8f3" lucid_version="FWPKG_MO000800KYDZK_MO001600KYDZR@HPK6__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:square">
	<li>Disabled Latency Tolerance Reporting Feature&nbsp;</li>
	<li>Drop MCTP command when interrupted by a Function Level Reset (FLR)&nbsp;</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul style="list-style-type:square">
	<li>Disabled Latency Tolerance Reporting Feature&nbsp;</li>
	<li>Drop MCTP command when interrupted by a Function Level Reset (FLR)&nbsp;</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:square">
	<li>Changes have been made in the 7500 firmware HPK6 over the previous firmware release to address Uncorrectable PCIe errors that are reported as ACS violations when Function Level Resets (FLR) are issued to the drive.<br />
	If this firmware is not updated, errors will be reported in HPE&rsquo;s iLO logging but there is no risk to user data or drive reliability.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul style="list-style-type:square">
	<li>Changes have been made in the 7500 firmware HPK6 over the previous firmware release to address Uncorrectable PCIe errors that are reported as ACS violations when Function Level Resets (FLR) are issued to the drive.<br />
	If this firmware is not updated, errors will be reported in HPE&rsquo;s iLO logging but there is no risk to user data or drive reliability.&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK1" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Changes and improvements made in HPK1&nbsp;are to enhance receiver signals by changing the drive&rsquo;s internal PHY register values on Gen11 x2 direct attached system.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Changes and improvements made in HPK1&nbsp;are to enhance receiver signals by changing the drive&rsquo;s internal PHY register values on Gen11 x2 direct attached system.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3ddaaa3582974e20842a8f677722b37a" version="2c6ddb95a2444b0db75ec74b02dff987" lucid_version="lpfc.rhel9.x86_64_gen12@14.4.731.6__pubsw-linux_en,ja"/>
      <revision_history>
        <revision>
          <version value="14.4.731.6" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 9.7</p>

<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 9.7</p>

<p>Updated to&nbsp;version&nbsp;14.4.731.6</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="14.4.473.24" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Added support for:</p>

<p>Red Hat Enterprise Linux 10.0</p>

<p>Updated to&nbsp;version 14.4.473.24</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="f56420e1793d48958fc061b802e973db" version="b86554bf52994fa69e0aa1a946645fcf" lucid_version="FWPKG-P45642-B22@28.48.1000-rev2__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="28.48.1000" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
	<li>To align with updated Microsoft UEFI Secure Boot requirements and the upcoming end-of-life of the 2011 Certificate Authority (CA), a transition to the 2023 CA has been done.&nbsp;To ensure successful loading of the Expansion ROM (ExpROM) during the UEFI Secure Boot process, system BIOS and operating system trust stores must be updated to include the 2023 CA.<br />
	<strong>Note:</strong>&nbsp;When performing a firmware update of ConnectX and BlueField devices the new certificate is required for Secure Boot. To continue supporting Secure Boot, systems must be updated to recognize the &quot;Microsoft Option ROM UEFI CA 2023&quot;.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="28.48.1000" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p><strong>New features and changes included in version 28.48.1000:</strong></p>

<ul>
	<li>Improved the ADP-RETX algorithm to avoid re-arming without performing a retransmission.</li>
	<li>The DOCA PCC NP application now enables the NIC to insert the RTT response transmit timestamp in hardware, reducing software-induced jitter and improving the accuracy and consistency of RTT measurements.</li>
	<li>The system-wide limit for DPA processes has been reduced to 30. This total includes both user processes across all GVMIs and internal ProgCC processes. The max_dpa_processes value reported to the user is calculated as: max_dpa_processes=30&minus;number_of_progcc_processes</li>
	<li>Added &nbsp;MAD (Management Datagram) access to the new &nbsp;Adaptive Retransmission Histogram &nbsp;registers. Users can configure the &nbsp;histogram &nbsp;by issuing &nbsp;VSP MAD GET/SET operations to ADP_RETX_HISTOGRAM_CONFIG (0xC01D), and retrieve histogram data via VSP MAD GET to ADP_RETX_HISTOGRAM_READ (0xC01E) (using the required VSP MAD header values and TLV format). This enables configuring and collecting adaptive retransmission timeout statistics through the MAD interface.</li>
	<li>Host rate limiting has been extended to support bandwidth values above 255 Gbps. To remove the previous cap, a new max_bw_value_msb field was added to est_global, providing additional MSB bits to represent higher bandwidth values. With this enhancement, firmware and host tooling can correctly configure and report rate limits beyond 255 Gbps on high-speed links.</li>
	<li>PLDM now supports the PDR Repository Change event type, enabling notification to the BMC when PDRs change. With this flow, the BMC can detect cable insertion/removal events.</li>
	<li>Added support for running save and load operations in parallel, enabling multiple contexts (e.g., multiple VFs) to be checkpointed and restored concurrently instead of serially. This reduces overall migration time and improves scalability in environments that need to migrate or recover many VFs at once.</li>
	<li>Extended packet modify-header operations to support set and copy actions on the NVGRE VSID (Virtual Subnet Identifier) . A new field, TUNNEL_HDR_DW_2 (0x84), enables dynamic VSID modification, adding header rewrite support for NVGRE tunnel traffic in addition to existing filtering capabilities.</li>
	<li>Added a new output field, migration_state, to QUERY_VHCA_MIGRATION_STATE. Software uses this field to make live-migration flow decisions, specifically to signal when it is not a good time to transition into the stop-copy stage.</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p><strong>The following issues have been fixed in version 28.48.1000:</strong></p>

<p>&nbsp;</p>

<ul>
	<li>An interoperability issue where, when ConnectX-7 communicates with ConnectX-8 using the probe-based algorithm, bandwidth could become extremely low due to probe packets being dropped.</li>
	<li>The DPA kernel used unsafe ICM access during process creation/modification, which would cause the DPA kernel to hang during FLR.</li>
	<li>User Debugger &ldquo;query caps&rdquo; returned only the number of capabilities, not the capability bitmap.</li>
	<li>Race condition in standby/boot power sequencing. In certain timing windows, port power-down would be delayed such that the power-up flow detected the port still transitioning to power-down, causing the sequence to fail and leaving the port stuck in a powered-down state.</li>
	<li>mlxlink reported 0 values for SNR (media and host) due to incorrect local port mapping in firmware and an incorrect page number used by MFT.</li>
	<li>Due to an SMBus release race condition, the I2C bus would become stuck.</li>
	<li>Fuse values were not aligned with the updated values burned across different ConnectX-7 setups.</li>
	<li>Issue in the steering definers used for LAG with IPv6 traffic.</li>
	<li>A spurious CNP was sent in response to an out-of-sequence packet.</li>
	<li>The root complex sent MCTP-over-PCI messages before a BDF was assigned, causing responses to be sent with BDF 0. The fix ensures that MCTP messages routed by ID are ignored until a valid BDF is assigned.</li>
	<li>The steering tables were not updated after enabling partial Spectrum-X capabilities (BTH.AR) via LLPD.</li>
	<li>When decapsulation on a packet occurred, the FCS indication was not calculated correctly.</li>
	<li>In IB system, RTT_response_sl feature did not work with Sniffer tools (e.g., Wireshark/Tcpdump/).<br />
	&nbsp;</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="25fca856f4a94804be9c77e4d53842cc" version="185cc9226be1448cb70dcb0e46ae7af1" lucid_version="Gen12_MR_Controller_AV2.esxi9.0_bundle@2026.04.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.04.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>8.16 AV2 PR2 GCA</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="513474ad42a4495f8786b7e4966794d7" version="0cddd2fd5f2e43a58aab7c9111cdd9dd" lucid_version="FWPKG_MB016000GWXKK@HPG5__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPG5" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity. The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This maintenance revision improves data integrity. The risk of not upgrading to this firmware is the increased possibility of data corruption in certain error and timing conditions.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPG4" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>&nbsp;</p>

<ul>
	<li>&nbsp;&nbsp;&nbsp; This firmware revision improves data integrity and reliability by optimizing adjacent track refresh parameters and management of emergency power loss table structure</li>
	<li>&nbsp;&nbsp;&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in emergency power loss events</li>
	<li>&nbsp;&nbsp;&nbsp; Several maintenance items are included in this firmware revision that reduce the probability of hangs and provide some minor performance improvements</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>&nbsp;</p>

<ul>
	<li>&nbsp;&nbsp;&nbsp; This firmware revision improves data integrity and reliability by optimizing adjacent track refresh parameters and management of emergency power loss table structure</li>
	<li>&nbsp;&nbsp;&nbsp; The risk of not upgrading to this firmware is the increased possibility of data corruption in emergency power loss events</li>
	<li>&nbsp;&nbsp;&nbsp; Several maintenance items are included in this firmware revision that reduce the probability of hangs and provide some minor performance improvements</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="3e44af8bcf3140b3bef280f7e913e5b4" version="38bbc6322f054a4b9d684698cc19c086" lucid_version="FWPKG_MO000800KXUJT_MO001600KXUJU_MO003200KXUJV@HPK2__fwpkg-drive_en"/>
      <revision_history>
        <revision>
          <version value="HPK2" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This version of FW now supports the 15.36TB model and FW fixes of drive time-out/failures.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>This version of FW now supports the 15.36TB model and FW fixes of drive time-out/failures.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="21705c05438d4e42ab093aa8ea61bd57" version="6b8cf057a9034aebbdad3c52be87a701" lucid_version="esxi80-amsdv-sw-bundle-sc@2026.05.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.05.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2026.03.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="http://www.hpe.com/support/AMS-en">AMS Release Notes&nbsp;</a>for information about the issues resolved in this release.</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="9f1ff08535434ba0ad3d9924079f9908" version="518ac76b543d46469d9245292ee12137" lucid_version="FWPKG_MO001600YXUJB_MO003200YXUJC_MO006400YXUJD@HPK4__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="HPK4" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release for sanitize, DRAM and log page fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Regular FW maintenance release for sanitize, DRAM and log page fix.</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="HPK3" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix for PCIe link length drop in AMD x2 system configuration</li>
	<li>Fix for drive detection after hot re-insert on Windows</li>
	<li>Fix for other regular FW patch release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix for PCIe link length drop in AMD x2 system configuration</li>
	<li>Fix for drive detection after hot re-insert on Windows</li>
	<li>Fix for other regular FW patch release</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="6b0653271f3e4e3a8e730542d61ffed8" version="4d76931c26af4d43986103fc1ca896c6" lucid_version="Gen10P_Gen11_MR_Controller.esxi8.0_bundle@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.09.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00145710en_us: HPE MR Gen11 and Gen10 Plus Storage Controllers - Purple&nbsp;Screen of Death (PSOD) May Be Observed When Updating Controller Firmware Via&nbsp;Service Pack for ProLiant (SPP) in Remote Deployment Mode With a VMware ESXi OS</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00145710en_us: HPE MR Gen11 and Gen10 Plus Storage Controllers - Purple&nbsp;Screen of Death (PSOD) May Be Observed When Updating Controller Firmware Via&nbsp;Service Pack for ProLiant (SPP) in Remote Deployment Mode With a VMware ESXi OS</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="eb043ee46d3343e7a128d08c1b9be087" version="c88089ebd42f43858969b27b98ab21a4" lucid_version="nicfwpkg_intel_e830_xxv4@1.22__fwpkg-generic_en"/>
      <revision_history>
        <revision>
          <version value="1.22" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>Initial version</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="b3a8e7e2c4ea466a9b404955f474449e" version="8328fb5e06d04fdaba15b5a0918ea252" lucid_version="isut.linux_x64@6.7.0.0__pubsw-linux_en"/>
      <revision_history>
        <revision>
          <version value="6.7.0.0" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="6.6.0.0" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<p>See the&nbsp;<a href="https://support.hpe.com/connect/s/search?language=en_US#q=integrated%20smart%20update%20tools&amp;t=All&amp;sort=relevancy&amp;numberOfResults=25">iSUT Release Notes&nbsp;</a>for information about the issues resolved in this release</p>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
    <product_version>
      <id product="39040fa72ee34e15b8d90d8ca174f1ed" version="7eaf15c47df143f49aab9806e11c534d" lucid_version="Gen10P_Gen11_MR_Controller.esxi9.0_bundle@2026.03.01__component-vmware_en"/>
      <revision_history>
        <revision>
          <version value="2026.03.01" revision="" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part><![CDATA[<ul>
	<li>7.36 (Aero PR11 GCA)</li>
</ul>
]]></revision_enhancements_xlate_part>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part/>
          </revision_fixes_xlate>
        </revision>
        <revision>
          <version value="2025.09.01" type_of_change="1"/>
          <revision_enhancements_xlate lang="cn">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_enhancements_xlate lang="en">
            <revision_enhancements_xlate_part/>
          </revision_enhancements_xlate>
          <revision_fixes_xlate lang="cn">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00145710en_us: HPE MR Gen11 and Gen10 Plus Storage Controllers - Purple&nbsp;Screen of Death (PSOD) May Be Observed When Updating Controller Firmware Via&nbsp;Service Pack for ProLiant (SPP) in Remote Deployment Mode With a VMware ESXi OS</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
          <revision_fixes_xlate lang="en">
            <revision_fixes_xlate_part><![CDATA[<ul>
	<li>Fix a00145710en_us: HPE MR Gen11 and Gen10 Plus Storage Controllers - Purple&nbsp;Screen of Death (PSOD) May Be Observed When Updating Controller Firmware Via&nbsp;Service Pack for ProLiant (SPP) in Remote Deployment Mode With a VMware ESXi OS</li>
</ul>
]]></revision_fixes_xlate_part>
          </revision_fixes_xlate>
        </revision>
      </revision_history>
    </product_version>
  </revision_history>
</manifest>
