threeeye
bc1d038eac
Squashed backup commit (no shallow-clone history issues) of xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2 branch, upstream commit 9eece662e) plus all fixes applied to get everpal_defconfig building clean against a modern (GCC 15.2.0) toolchain -- see the previous commit message on the lineage-23.2 branch (also in this repo history is not available here since this is a squashed snapshot; full incremental history lives in the local DL380 checkout and the upstream GitHub remote). Upstream: https://github.com/xiaomi-mt6833-dev/kernel_xiaomi_mt6833 (lineage-23.2)
34 lines
1.5 KiB
Plaintext
34 lines
1.5 KiB
Plaintext
What: /sys/firmware/ibft/initiator
|
|
Date: November 2007
|
|
Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
|
|
Description: The /sys/firmware/ibft/initiator directory will contain
|
|
files that expose the iSCSI Boot Firmware Table initiator data.
|
|
Usually this contains the Initiator name.
|
|
|
|
What: /sys/firmware/ibft/targetX
|
|
Date: November 2007
|
|
Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
|
|
Description: The /sys/firmware/ibft/targetX directory will contain
|
|
files that expose the iSCSI Boot Firmware Table target data.
|
|
Usually this contains the target's IP address, boot LUN,
|
|
target name, and what NIC it is associated with. It can also
|
|
contain the CHAP name (and password), the reverse CHAP
|
|
name (and password)
|
|
|
|
What: /sys/firmware/ibft/ethernetX
|
|
Date: November 2007
|
|
Contact: Konrad Rzeszutek <ketuzsezr@darnok.org>
|
|
Description: The /sys/firmware/ibft/ethernetX directory will contain
|
|
files that expose the iSCSI Boot Firmware Table NIC data.
|
|
Usually this contains the IP address, MAC, and gateway of the NIC.
|
|
|
|
What: /sys/firmware/ibft/acpi_header
|
|
Date: March 2016
|
|
Contact: David Bond <dbond@suse.com>
|
|
Description: The /sys/firmware/ibft/acpi_header directory will contain files
|
|
that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the
|
|
acpi table header of the iBFT structure. This will allow for
|
|
identification of the creator of the table which is useful in
|
|
determining quirks associated with some adapters when used in
|
|
hardware vs software iscsi initiator mode.
|