Commit | Line | Data |
---|---|---|
04851772 MF |
1 | menu "EFI (Extensible Firmware Interface) Support" |
2 | depends on EFI | |
3 | ||
4 | config EFI_VARS | |
5 | tristate "EFI Variable Support via sysfs" | |
6 | depends on EFI | |
7 | default n | |
8 | help | |
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. | |
12 | ||
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 | |
0e4ca02b | 15 | available from: |
04851772 MF |
16 | <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz> |
17 | ||
18 | Subsequent efibootmgr releases may be found at: | |
0e4ca02b | 19 | <http://github.com/vathpela/efibootmgr> |
04851772 | 20 | |
3846c158 PJ |
21 | config EFI_ESRT |
22 | bool | |
23 | depends on EFI && !IA64 | |
24 | default y | |
25 | ||
04851772 MF |
26 | config EFI_VARS_PSTORE |
27 | tristate "Register efivars backend for pstore" | |
28 | depends on EFI_VARS && PSTORE | |
29 | default y | |
30 | help | |
31 | Say Y here to enable use efivars as a backend to pstore. This | |
32 | will allow writing console messages, crash dumps, or anything | |
33 | else supported by pstore to EFI variables. | |
34 | ||
35 | config EFI_VARS_PSTORE_DEFAULT_DISABLE | |
36 | bool "Disable using efivars as a pstore backend by default" | |
37 | depends on EFI_VARS_PSTORE | |
38 | default n | |
39 | help | |
40 | Saying Y here will disable the use of efivars as a storage | |
41 | backend for pstore by default. This setting can be overridden | |
42 | using the efivars module's pstore_disable parameter. | |
43 | ||
926172d4 DY |
44 | config EFI_RUNTIME_MAP |
45 | bool "Export efi runtime maps to sysfs" | |
46 | depends on X86 && EFI && KEXEC | |
47 | default y | |
48 | help | |
49 | Export efi runtime memory maps to /sys/firmware/efi/runtime-map. | |
50 | That memory map is used for example by kexec to set up efi virtual | |
51 | mapping the 2nd kernel, but can also be used for debugging purposes. | |
52 | ||
53 | See also Documentation/ABI/testing/sysfs-firmware-efi-runtime-map. | |
54 | ||
0f96a99d TI |
55 | config EFI_FAKE_MEMMAP |
56 | bool "Enable EFI fake memory map" | |
57 | depends on EFI && X86 | |
58 | default n | |
59 | help | |
60 | Saying Y here will enable "efi_fake_mem" boot option. | |
61 | By specifying this parameter, you can add arbitrary attribute | |
62 | to specific memory range by updating original (firmware provided) | |
63 | EFI memmap. | |
64 | This is useful for debugging of EFI memmap related feature. | |
65 | e.g. Address Range Mirroring feature. | |
66 | ||
67 | config EFI_MAX_FAKE_MEM | |
68 | int "maximum allowable number of ranges in efi_fake_mem boot option" | |
69 | depends on EFI_FAKE_MEMMAP | |
70 | range 1 128 | |
71 | default 8 | |
72 | help | |
73 | Maximum allowable number of ranges in efi_fake_mem boot option. | |
74 | Ranges can be set up to this value using comma-separated list. | |
75 | The default value is 8. | |
76 | ||
0302f71c MS |
77 | config EFI_PARAMS_FROM_FDT |
78 | bool | |
79 | help | |
80 | Select this config option from the architecture Kconfig if | |
81 | the EFI runtime support gets system table address, memory | |
82 | map address, and other parameters from the device tree. | |
83 | ||
022ee6c5 AB |
84 | config EFI_RUNTIME_WRAPPERS |
85 | bool | |
86 | ||
f4f75ad5 AB |
87 | config EFI_ARMSTUB |
88 | bool | |
89 | ||
04851772 | 90 | endmenu |
fce7d3bf JB |
91 | |
92 | config UEFI_CPER | |
93 | bool |