Storage Virtualization Changes

Device Node

Target Changes	Backward Compatible	Platform	OS
Post 6.5: Device node for performing the firmware update is /dev/vblkdevX.ctl for Linux and /dev/vblk_ufsX.ctl or /dev/vblk_mnandX.ctl for QNX. From 7.0: Device node for performing the firmware update changed. A separate device node - /dev/vblkdevX.ffu for Linux and /dev/vblk_ufsX.ffu or /dev/vblk_mnandX.ffu for QNX now performs storage device firmware update-related operations.	No	NSR, SR	Linux and QNX

Migration Path

• Orin to Thor

Migration Rationale

To provide separate access control for device management and firmware update features, a separate device node is enumerated for each feature.

Steps to Migrate

For the steps to migrate, refer to the next section.

Steps to Migrate Example Per the Previous Table

Storage device firmware update operation users have to change the device node from the .ctl device node to the .ffu device node.

For example, following is the mnand_hs command to perform a firmware update in the 6.X release.

• Linux:

  mnand_hs -d /dev/vblkdevX.ctl -ffu <Firmware Image>

• QNX:

  mnand_hs -d /dev/vblk_mnandX.ctl -ffu <Firmware Image> or mnand_ufs_hs -d /dev/vblk_ufsX.ctl -ffu <Firmware Image>

Following is the mnand_hs command to perform a firmware update in the 7.X release.

• Linux:

  mnand_hs -d /dev/vblkdevX.ffu -ffu <Firmware Image> or

• QNX:

  mnand_hs -d /dev/vblk_mnandX.ffu -ffu <Firmware Image> or mnand_ufs_hs -d /dev/vblk_ufsX.ffu -ffu <Firmware Image>