Documentation/ABI/testing/sysfs-firmware-dmi-tables

Source file repositories/reference/linux-study-clean/Documentation/ABI/testing/sysfs-firmware-dmi-tables

File Facts

System: Linux kernel
Corpus path: Documentation/ABI/testing/sysfs-firmware-dmi-tables
Extension: [no extension]
Size: 907 bytes
Lines: 23
Domain: Support Tooling And Documentation
Bucket: Documentation
Inferred role: Support Tooling And Documentation: Documentation
Status: atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

What:		/sys/firmware/dmi/tables/
Date:		April 2015
Contact:	Ivan Khoronzhuk <ivan.khoronzhuk@globallogic.com>
Description:
		The firmware provides DMI structures as a packed list of
		data referenced by a SMBIOS table entry point. The SMBIOS
		entry point contains general information, like SMBIOS
		version, DMI table size, etc. The structure, content and
		size of SMBIOS entry point is dependent on SMBIOS version.
		The format of SMBIOS entry point and DMI structures
		can be read in SMBIOS specification.

		The dmi/tables provides raw SMBIOS entry point and DMI tables
		through sysfs as an alternative to utilities reading them
		from /dev/mem. The raw SMBIOS entry point and DMI table are
		presented as binary attributes and are accessible via:

		/sys/firmware/dmi/tables/smbios_entry_point
		/sys/firmware/dmi/tables/DMI

		The complete DMI information can be obtained using these two
		tables.

Annotation

Atlas domain: Support Tooling And Documentation / Documentation.
Implementation status: atlas-only.

Implementation Notes

This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.