Commit | Line | Data |
---|---|---|
138fe4e0 KR |
1 | What: /sys/firmware/ibft/initiator |
2 | Date: November 2007 | |
3 | Contact: Konrad Rzeszutek <ketuzsezr@darnok.org> | |
4 | Description: The /sys/firmware/ibft/initiator directory will contain | |
5 | files that expose the iSCSI Boot Firmware Table initiator data. | |
6 | Usually this contains the Initiator name. | |
7 | ||
8 | What: /sys/firmware/ibft/targetX | |
9 | Date: November 2007 | |
10 | Contact: Konrad Rzeszutek <ketuzsezr@darnok.org> | |
11 | Description: The /sys/firmware/ibft/targetX directory will contain | |
12 | files that expose the iSCSI Boot Firmware Table target data. | |
13 | Usually this contains the target's IP address, boot LUN, | |
14 | target name, and what NIC it is associated with. It can also | |
15 | contain the CHAP name (and password), the reverse CHAP | |
16 | name (and password) | |
17 | ||
18 | What: /sys/firmware/ibft/ethernetX | |
19 | Date: November 2007 | |
20 | Contact: Konrad Rzeszutek <ketuzsezr@darnok.org> | |
21 | Description: The /sys/firmware/ibft/ethernetX directory will contain | |
22 | files that expose the iSCSI Boot Firmware Table NIC data. | |
dce9b2c9 | 23 | Usually this contains the IP address, MAC, and gateway of the NIC. |
b3c8eb50 DB |
24 | |
25 | What: /sys/firmware/ibft/acpi_header | |
26 | Date: March 2016 | |
27 | Contact: David Bond <dbond@suse.com> | |
28 | Description: The /sys/firmware/ibft/acpi_header directory will contain files | |
29 | that expose the SIGNATURE, OEM_ID, and OEM_TABLE_ID fields of the | |
30 | acpi table header of the iBFT structure. This will allow for | |
31 | identification of the creator of the table which is useful in | |
32 | determining quirks associated with some adapters when used in | |
33 | hardware vs software iscsi initiator mode. |