summaryrefslogtreecommitdiffstats
path: root/documentation/UEFI_from_spec/Access SMBIOS
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/UEFI_from_spec/Access SMBIOS')
-rw-r--r--documentation/UEFI_from_spec/Access SMBIOS26
1 files changed, 26 insertions, 0 deletions
diff --git a/documentation/UEFI_from_spec/Access SMBIOS b/documentation/UEFI_from_spec/Access SMBIOS
new file mode 100644
index 0000000..cd20f5f
--- /dev/null
+++ b/documentation/UEFI_from_spec/Access SMBIOS
@@ -0,0 +1,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