Lines Matching +full:entry +full:- +full:name
16 each entry has a common header indicating the type and
17 length of the entry, as well as a firmware-provided
23 never expect to find a specific entry type on their
28 to handle these duplicate entry types, each entry is
30 derived from an entry type's ordinal position. That is
34 entries "T-0" through "T-(N-1)":
36 Example entry directories::
38 /sys/firmware/dmi/entries/17-0
39 /sys/firmware/dmi/entries/17-1
40 /sys/firmware/dmi/entries/17-2
41 /sys/firmware/dmi/entries/17-3
45 assigned entry handles as the kernel itself makes no
50 Each DMI entry in sysfs has the common header values
55 entry by the firmware. This handle may be
57 length The length of the entry, as presented in the
58 entry itself. Note that this is _not the
60 entry. This value represents the length of
61 the "formatted" portion of the entry. This
66 raw The raw bytes of the entry. This includes the
67 "formatted" portion of the entry, the
68 "unformatted" strings portion of the entry,
70 type The type of the entry. This value is the same
71 as found in the directory name. It indicates
72 how the rest of the entry should be interpreted.
73 instance The instance ordinal of the entry for the
75 in the parent directory name.
76 position The ordinal position (zero-based) of the entry
77 within the entirety of the DMI entry table.
80 **Entry Specialization**
82 Some entry types may have other information available in
85 **Type 15 - System Event Log**
87 This entry allows the firmware to export a log of
90 details are abstracted by this table. This entry's data
93 /sys/firmware/dmi/entries/15-0/system_event_log
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
113 as described by the DMI entry.