| menu "EFI (Extensible Firmware Interface) Support" | |
| depends on EFI | |
| config EFI_VARS | |
| tristate "EFI Variable Support via sysfs" | |
| depends on EFI | |
| default n | |
| help | |
| If you say Y here, you are able to get EFI (Extensible Firmware | |
| Interface) variable information via sysfs. You may read, | |
| write, create, and destroy EFI variables through this interface. | |
| Note that using this driver in concert with efibootmgr requires | |
| at least test release version 0.5.0-test3 or later, which is | |
| available from: | |
| <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz> | |
| Subsequent efibootmgr releases may be found at: | |
| <http://github.com/vathpela/efibootmgr> | |
| config EFI_ESRT | |
| bool | |
| depends on EFI && !IA64 | |
| default y | |
| config EFI_VARS_PSTORE | |
| tristate "Register efivars backend for pstore" | |
| depends on EFI_VARS && PSTORE | |
| default y | |
| help | |
| Say Y here to enable use efivars as a backend to pstore. This | |
| will allow writing console messages, crash dumps, or anything | |
| else supported by pstore to EFI variables. | |
| config EFI_VARS_PSTORE_DEFAULT_DISABLE | |
| bool "Disable using efivars as a pstore backend by default" | |
| depends on EFI_VARS_PSTORE | |
| default n | |
| help | |
| Saying Y here will disable the use of efivars as a storage | |
| backend for pstore by default. This setting can be overridden | |
| using the efivars module's pstore_disable parameter. | |
| config EFI_RUNTIME_MAP | |
| bool "Export efi runtime maps to sysfs" | |
| depends on X86 && EFI && KEXEC_CORE | |
| default y | |
| help | |
| Export efi runtime memory maps to /sys/firmware/efi/runtime-map. | |
| That memory map is used for example by kexec to set up efi virtual | |
| mapping the 2nd kernel, but can also be used for debugging purposes. | |
| See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map. | |
| config EFI_FAKE_MEMMAP | |
| bool "Enable EFI fake memory map" | |
| depends on EFI && X86 | |
| default n | |
| help | |
| Saying Y here will enable "efi_fake_mem" boot option. | |
| By specifying this parameter, you can add arbitrary attribute | |
| to specific memory range by updating original (firmware provided) | |
| EFI memmap. | |
| This is useful for debugging of EFI memmap related feature. | |
| e.g. Address Range Mirroring feature. | |
| config EFI_MAX_FAKE_MEM | |
| int "maximum allowable number of ranges in efi_fake_mem boot option" | |
| depends on EFI_FAKE_MEMMAP | |
| range 1 128 | |
| default 8 | |
| help | |
| Maximum allowable number of ranges in efi_fake_mem boot option. | |
| Ranges can be set up to this value using comma-separated list. | |
| The default value is 8. | |
| config EFI_PARAMS_FROM_FDT | |
| bool | |
| help | |
| Select this config option from the architecture Kconfig if | |
| the EFI runtime support gets system table address, memory | |
| map address, and other parameters from the device tree. | |
| config EFI_RUNTIME_WRAPPERS | |
| bool | |
| config EFI_ARMSTUB | |
| bool | |
| endmenu | |
| config UEFI_CPER | |
| bool |