summaryrefslogtreecommitdiffstats
path: root/documentation/UEFI/Access SMBIOS
blob: cd20f5f88d08a1a20bfd6feedc86b4cc8d6adcdc (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
(several forums)

INSIDE UEFI:
	EFI_CONFIGURATION_TABLE contains entries pointing to the SMBIOS2 and/or SMBIOS3 tables

FROM UEFI Shell:
	SmbiosView command

FROM LINUX:
	SMBIOS decoder: dmidecode(8)

WINDOWS:
	WMI

Generating SMBIOS data:
Table&structure creation is normally up to the system firmware/BIOS.
UEFI Platform Initialization (PI) spec includes SMBIOS protocol (EFI_SMBIOS_PROTOCOL) that allows components
to submit SMBIOS structures for incluseion, enables producer to create SMBIOS table for a platform.

Some hardware information is available through ACPI and DMI. The ACPI tables are technically provided through UEFI,
by virtue of passing one pointer (and supposed by leaving the relevant memory reserved, in the memory map
which the IS is passed by UEFI.

Platform virtualization software can also generate SMBIOS tables for use inside VMs, for instance qemu.

--> Desktop Management BIOS Specification 2/3