Lines Matching refs:the

6 		SMBIOS tables to the operating system.  Getting at this
10 		The kernel itself does not rely on the majority of the
12 		cannot ensure that the data as exported to userland is
16 		each entry has a common header indicating the type and
17 		length of the entry, as well as a firmware-provided
21 		Some entries are required by the specification, but many
27 		Multiple entries of the same type are allowed.  In order
29 		assigned by the operating system an 'instance', which is
31 		to say, if there are 'N' multiple entries with the same type
32 		'T' in the DMI tables (adjacent or spread apart, it
44 		Instance numbers are used in lieu of the firmware
45 		assigned entry handles as the kernel itself makes no
48 		the wild.
50 		Each DMI entry in sysfs has the common header values
54 			  entry by the firmware.  This handle may be
56 		length	: The length of the entry, as presented in the
57 			  entry itself.  Note that this is _not the
58 			  total count of bytes associated with the
59 			  entry_.  This value represents the length of
60 			  the "formatted" portion of the entry.  This
62 			  the "unformatted" region composed of nul
65 		raw	: The raw bytes of the entry. This includes the
66 			  "formatted" portion of the entry, the
67 			  "unformatted" strings portion of the entry,
68 			  and the two terminating nul characters.
69 		type	: The type of the entry.  This value is the same
70 			  as found in the directory name.  It indicates
71 			  how the rest of the entry should be interpreted.
72 		instance: The instance ordinal of the entry for the
73 			  given type.  This value is the same as found
74 			  in the parent directory name.
75 		position: The ordinal position (zero-based) of the entry
76 			  within the entirety of the DMI entry table.
85 		This entry allows the firmware to export a log of
86 		events the system has taken.  This information is
87 		typically backed by nvram, but the implementation
89 		is exported in the directory:
93 		and has the following attributes (documented in the
107 		As well, the kernel exports the binary attribute:
109 		raw_event_log	: The raw binary bits of the event log
110 				  as described by the DMI entry.