menu "EFI (Extensible Firmware Interface) Support"
depends on [31mCONFIG_EFI[0m
config [31mCONFIG_EFI_VARS[0m
tristate "EFI Variable Support via sysfs"
depends on [31mCONFIG_EFI[0m
default n
help
If you say Y here, you are able to get [31mCONFIG_EFI[0m (Extensible Firmware
Interface) variable information via sysfs. You may read,
write, create, and destroy [31mCONFIG_EFI[0m 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 [31mCONFIG_EFI_ESRT[0m
bool
depends on [31mCONFIG_EFI[0m && ![31mCONFIG_IA64[0m
default y
config [31mCONFIG_EFI_VARS_PSTORE[0m
tristate "Register efivars backend for pstore"
depends on [31mCONFIG_EFI_VARS[0m && [31mCONFIG_PSTORE[0m
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 [31mCONFIG_EFI[0m variables.
config [31mCONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE[0m
bool "Disable using efivars as a pstore backend by default"
depends on [31mCONFIG_EFI_VARS_PSTORE[0m
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 [31mCONFIG_EFI_RUNTIME_MAP[0m
bool "Export efi runtime maps to sysfs"
depends on [31mCONFIG_X86[0m && [31mCONFIG_EFI[0m && [31mCONFIG_KEXEC_CORE[0m
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 [31mCONFIG_EFI_FAKE_MEMMAP[0m
bool "Enable EFI fake memory map"
depends on [31mCONFIG_EFI[0m && [31mCONFIG_X86[0m
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)
[31mCONFIG_EFI[0m memmap.
This is useful for debugging of [31mCONFIG_EFI[0m memmap related feature.
e.g. Address Range Mirroring feature.
config [31mCONFIG_EFI_MAX_FAKE_MEM[0m
int "maximum allowable number of ranges in efi_fake_mem boot option"
depends on [31mCONFIG_EFI_FAKE_MEMMAP[0m
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 [31mCONFIG_EFI_PARAMS_FROM_FDT[0m
bool
help
Select this config option from the architecture Kconfig if
the [31mCONFIG_EFI[0m runtime support gets system table address, memory
map address, and other parameters from the device tree.
config [31mCONFIG_EFI_RUNTIME_WRAPPERS[0m
bool
config [31mCONFIG_EFI_ARMSTUB[0m
bool
config [31mCONFIG_EFI_BOOTLOADER_CONTROL[0m
tristate "EFI Bootloader Control"
depends on [31mCONFIG_EFI_VARS[0m
default n
---help---
This module installs a reboot hook, such that if reboot() is
invoked with a string argument NNN, "NNN" is copied to the
"LoaderEntryOneShot" [31mCONFIG_EFI[0m variable, to be read by the
bootloader. If the string matches one of the boot labels
defined in its configuration, the bootloader will boot once
to that label. The "LoaderEntryRebootReason" [31mCONFIG_EFI[0m variable is
set with the reboot reason: "reboot" or "shutdown". The
bootloader reads this reboot reason and takes particular
action according to its policy.
config [31mCONFIG_EFI_CAPSULE_LOADER[0m
tristate "EFI capsule loader"
depends on [31mCONFIG_EFI[0m
help
This option exposes a loader interface "/dev/efi_capsule_loader" for
users to load [31mCONFIG_EFI[0m capsules. This driver requires working runtime
capsule support in the firmware, which many OEMs do not provide.
Most users should say N.
config [31mCONFIG_EFI_TEST[0m
tristate "EFI Runtime Service Tests Support"
depends on [31mCONFIG_EFI[0m
default n
help
This driver uses the efi.<service> function pointers directly instead
of going through the efivar API, because it is not trying to test the
kernel subsystem, just for testing the UEFI runtime service
interfaces which are provided by the firmware. This driver is used
by the Firmware Test Suite (FWTS) for testing the UEFI runtime
interfaces readiness of the firmware.
Details for FWTS are available from:
<https://wiki.ubuntu.com/FirmwareTestSuite>
Say Y here to enable the runtime services support via /dev/efi_test.
If unsure, say N.
config [31mCONFIG_APPLE_PROPERTIES[0m
bool "Apple Device Properties"
depends on [31mCONFIG_EFI_STUB[0m && [31mCONFIG_X86[0m
select [31mCONFIG_EFI_DEV_PATH_PARSER[0m
select [31mCONFIG_UCS2_STRING[0m
help
Retrieve properties from [31mCONFIG_EFI[0m on Apple Macs and assign them to
devices, allowing for improved support of Apple hardware.
Properties that would otherwise be missing include the
Thunderbolt Device [31mCONFIG_ROM[0m and GPU configuration data.
If unsure, say Y if you have a Mac. Otherwise N.
endmenu
config [31mCONFIG_UEFI_CPER[0m
bool
config [31mCONFIG_EFI_DEV_PATH_PARSER[0m
bool
depends on [31mCONFIG_ACPI[0m
default n