| .. | .. |
|---|
| 33 | 33 | doesn't matter), they will be represented in sysfs as |
|---|
| 34 | 34 | entries "T-0" through "T-(N-1)": |
|---|
| 35 | 35 | |
|---|
| 36 | | - Example entry directories: |
|---|
| 36 | + Example entry directories:: |
|---|
| 37 | 37 | |
|---|
| 38 | 38 | /sys/firmware/dmi/entries/17-0 |
|---|
| 39 | 39 | /sys/firmware/dmi/entries/17-1 |
|---|
| .. | .. |
|---|
| 50 | 50 | Each DMI entry in sysfs has the common header values |
|---|
| 51 | 51 | exported as attributes: |
|---|
| 52 | 52 | |
|---|
| 53 | | - handle : The 16bit 'handle' that is assigned to this |
|---|
| 53 | + ======== ================================================= |
|---|
| 54 | + handle The 16bit 'handle' that is assigned to this |
|---|
| 54 | 55 | entry by the firmware. This handle may be |
|---|
| 55 | 56 | referred to by other entries. |
|---|
| 56 | | - length : The length of the entry, as presented in the |
|---|
| 57 | + length The length of the entry, as presented in the |
|---|
| 57 | 58 | entry itself. Note that this is _not the |
|---|
| 58 | 59 | total count of bytes associated with the |
|---|
| 59 | | - entry_. This value represents the length of |
|---|
| 60 | + entry. This value represents the length of |
|---|
| 60 | 61 | the "formatted" portion of the entry. This |
|---|
| 61 | 62 | "formatted" region is sometimes followed by |
|---|
| 62 | 63 | the "unformatted" region composed of nul |
|---|
| 63 | 64 | terminated strings, with termination signalled |
|---|
| 64 | 65 | by a two nul characters in series. |
|---|
| 65 | | - raw : The raw bytes of the entry. This includes the |
|---|
| 66 | + raw The raw bytes of the entry. This includes the |
|---|
| 66 | 67 | "formatted" portion of the entry, the |
|---|
| 67 | 68 | "unformatted" strings portion of the entry, |
|---|
| 68 | 69 | and the two terminating nul characters. |
|---|
| 69 | | - type : The type of the entry. This value is the same |
|---|
| 70 | + type The type of the entry. This value is the same |
|---|
| 70 | 71 | as found in the directory name. It indicates |
|---|
| 71 | 72 | how the rest of the entry should be interpreted. |
|---|
| 72 | | - instance: The instance ordinal of the entry for the |
|---|
| 73 | + instance The instance ordinal of the entry for the |
|---|
| 73 | 74 | given type. This value is the same as found |
|---|
| 74 | 75 | in the parent directory name. |
|---|
| 75 | | - position: The ordinal position (zero-based) of the entry |
|---|
| 76 | + position The ordinal position (zero-based) of the entry |
|---|
| 76 | 77 | within the entirety of the DMI entry table. |
|---|
| 78 | + ======== ================================================= |
|---|
| 77 | 79 | |
|---|
| 78 | | - === Entry Specialization === |
|---|
| 80 | + **Entry Specialization** |
|---|
| 79 | 81 | |
|---|
| 80 | 82 | Some entry types may have other information available in |
|---|
| 81 | 83 | sysfs. Not all types are specialized. |
|---|
| 82 | 84 | |
|---|
| 83 | | - --- Type 15 - System Event Log --- |
|---|
| 85 | + **Type 15 - System Event Log** |
|---|
| 84 | 86 | |
|---|
| 85 | 87 | This entry allows the firmware to export a log of |
|---|
| 86 | 88 | events the system has taken. This information is |
|---|
| 87 | 89 | typically backed by nvram, but the implementation |
|---|
| 88 | 90 | details are abstracted by this table. This entry's data |
|---|
| 89 | | - is exported in the directory: |
|---|
| 91 | + is exported in the directory:: |
|---|
| 90 | 92 | |
|---|
| 91 | | - /sys/firmware/dmi/entries/15-0/system_event_log |
|---|
| 93 | + /sys/firmware/dmi/entries/15-0/system_event_log |
|---|
| 92 | 94 | |
|---|
| 93 | 95 | and has the following attributes (documented in the |
|---|
| 94 | 96 | SMBIOS / DMI specification under "System Event Log (Type 15)": |
|---|
| 95 | 97 | |
|---|
| 96 | | - area_length |
|---|
| 97 | | - header_start_offset |
|---|
| 98 | | - data_start_offset |
|---|
| 99 | | - access_method |
|---|
| 100 | | - status |
|---|
| 101 | | - change_token |
|---|
| 102 | | - access_method_address |
|---|
| 103 | | - header_format |
|---|
| 104 | | - per_log_type_descriptor_length |
|---|
| 105 | | - type_descriptors_supported_count |
|---|
| 98 | + - area_length |
|---|
| 99 | + - header_start_offset |
|---|
| 100 | + - data_start_offset |
|---|
| 101 | + - access_method |
|---|
| 102 | + - status |
|---|
| 103 | + - change_token |
|---|
| 104 | + - access_method_address |
|---|
| 105 | + - header_format |
|---|
| 106 | + - per_log_type_descriptor_length |
|---|
| 107 | + - type_descriptors_supported_count |
|---|
| 106 | 108 | |
|---|
| 107 | 109 | As well, the kernel exports the binary attribute: |
|---|
| 108 | 110 | |
|---|
| 109 | | - raw_event_log : The raw binary bits of the event log |
|---|
| 111 | + ============= ==================================== |
|---|
| 112 | + raw_event_log The raw binary bits of the event log |
|---|
| 110 | 113 | as described by the DMI entry. |
|---|
| 114 | + ============= ==================================== |
|---|