SRP boot firmware table

The SRP Boot Firmware Table (sBFT) is a block of information containing various parameters useful to the SRP boot process. It is the mechanism whereby the boot firmware conveys information about the boot device to the loaded operating system.

The sBFT can be located by scanning through base memory (address 0x00000 to address 0x09FFFF) for the table header signature. The table must be aligned on a 16-byte boundary, and the checksum must be correct.

The sBFT follows the structure of an ACPI table.

All scalar quantities are little-endian.

All fields marked as reserved must be filled with zeroes.

The sBFT consists of an ACPI Subtable, a SCSI Subtable, an SRP Subtable, and one or more transport-specific subtables such as the IB Subtable.

This is the offset (in bytes from the start of the sBFT) to the SCSI Subtable.

This is the offset (in bytes from the start of the sBFT) to the SRP Subtable.

This is the offset (in bytes from the start of the sBFT) to the IB Subtable. A zero value indicates that no IB Subtable is present.

The ACPI Subtable contains the generic header fields to allow for identification of the sBFT.

'sBFT' signature for the SRP Boot Firmware Table.

Length in bytes of the entire sBFT, including the signature.

Must be set to 1.

Entire table must sum to zero.

ACPI OEM ID. All unused trailing bytes must be zero.

For the sBFT the Table ID is the Manufacturer's Model ID. All unused trailing bytes must be zero.

The SCSI Subtable contains values that are required for all SRP sessions, independent of transport type.

This is the SCSI LUN, as defined by the SCSI Architecture Model-2 standard.

The SRP Subtable contains values that are required for all SRP sessions, independent of transport type.

This is the initiator port identifier as defined in the SRP specification and used in the SRP_LOGIN_REQ request.

This is the target port identifier as defined in the SRP specification and used in the SRP_LOGIN_REQ request.

The IB Subtable, if present, contains values that are required for all SRP sessions running over Infiniband transport.

Note that the SRP specification imposes an Infiniband-specific interpretation on the initiator and target port identifiers as found in the SRP Subtable (above); some values with Infiniband-specific meanings (e.g. the I/O Controller GUID) can therefore be derived from the values in the SRP Subtable and are not duplicated here in the IB Subtable.

This is a GID belonging to the HCA port used to initiate the SRP connection.

This is the GID of the SRP target.

This is the service identifier of the SRP target.

This is the partition key of the SRP target.