1 menu "EFI (Extensible Firmware Interface) Support"
5 tristate "EFI Variable Support via sysfs"
9 If you say Y here, you are able to get EFI (Extensible Firmware
10 Interface) variable information via sysfs. You may read,
11 write, create, and destroy EFI variables through this interface.
13 Note that using this driver in concert with efibootmgr requires
14 at least test release version 0.5.0-test3 or later, which is
16 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
18 Subsequent efibootmgr releases may be found at:
19 <http://github.com/vathpela/efibootmgr>
21 config EFI_VARS_PSTORE
22 tristate "Register efivars backend for pstore"
23 depends on EFI_VARS && PSTORE
26 Say Y here to enable use efivars as a backend to pstore. This
27 will allow writing console messages, crash dumps, or anything
28 else supported by pstore to EFI variables.
30 config EFI_VARS_PSTORE_DEFAULT_DISABLE
31 bool "Disable using efivars as a pstore backend by default"
32 depends on EFI_VARS_PSTORE
35 Saying Y here will disable the use of efivars as a storage
36 backend for pstore by default. This setting can be overridden
37 using the efivars module's pstore_disable parameter.
39 config EFI_RUNTIME_MAP
40 bool "Export efi runtime maps to sysfs"
41 depends on X86 && EFI && KEXEC
44 Export efi runtime memory maps to /sys/firmware/efi/runtime-map.
45 That memory map is used for example by kexec to set up efi virtual
46 mapping the 2nd kernel, but can also be used for debugging purposes.
48 See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map.
50 config EFI_PARAMS_FROM_FDT
53 Select this config option from the architecture Kconfig if
54 the EFI runtime support gets system table address, memory
55 map address, and other parameters from the device tree.
57 config EFI_RUNTIME_WRAPPERS