2013-02-08 23:48:51 +08:00
|
|
|
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
|
2014-12-10 05:14:11 +08:00
|
|
|
available from:
|
2013-02-08 23:48:51 +08:00
|
|
|
<http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
|
|
|
|
|
|
|
|
|
|
Subsequent efibootmgr releases may be found at:
|
2014-12-10 05:14:11 +08:00
|
|
|
<http://github.com/vathpela/efibootmgr>
|
2013-02-08 23:48:51 +08:00
|
|
|
|
efi: Work around ia64 build problem with ESRT driver
So, I'm told this problem exists in the world:
> Subject: Build error in -next due to 'efi: Add esrt support'
>
> Building ia64:defconfig ... failed
> --------------
> Error log:
>
> drivers/firmware/efi/esrt.c:28:31: fatal error: asm/early_ioremap.h: No such file or directory
>
I'm not really sure how it's okay that we have things in asm-generic on
some platforms but not others - is having it the same everywhere not the
whole point of asm-generic?
That said, ia64 doesn't have early_ioremap.h . So instead, since it's
difficult to imagine new IA64 machines with UEFI 2.5, just don't build
this code there.
To me this looks like a workaround - doing something like:
generic-y += early_ioremap.h
in arch/ia64/include/asm/Kbuild would appear to be more correct, but
ia64 has its own early_memremap() decl in arch/ia64/include/asm/io.h ,
and it's a macro. So adding the above /and/ requiring that asm/io.h be
included /after/ asm/early_ioremap.h in all cases would fix it, but
that's pretty ugly as well. Since I'm not going to spend the rest of my
life rectifying ia64 headers vs "generic" headers that aren't generic,
it's much simpler to just not build there.
Note that I've only actually tried to build this patch on x86_64, but
esrt.o still gets built there, and that would seem to demonstrate that
the conditional building is working correctly at all the places the code
built before. I no longer have any ia64 machines handy to test that the
exclusion actually works there.
Signed-off-by: Peter Jones <pjones@redhat.com>
Acked-by: Tony Luck <tony.luck@intel.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
(Compile-)Tested-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Matt Fleming <matt.fleming@intel.com>
2015-06-06 03:14:54 +08:00
|
|
|
config EFI_ESRT
|
|
|
|
|
bool
|
|
|
|
|
depends on EFI && !IA64
|
|
|
|
|
default y
|
|
|
|
|
|
2013-02-08 23:48:51 +08:00
|
|
|
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.
|
|
|
|
|
|
2013-12-20 18:02:18 +08:00
|
|
|
config EFI_RUNTIME_MAP
|
|
|
|
|
bool "Export efi runtime maps to sysfs"
|
2015-09-10 06:38:55 +08:00
|
|
|
depends on X86 && EFI && KEXEC_CORE
|
2013-12-20 18:02:18 +08:00
|
|
|
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.
|
|
|
|
|
|
2015-09-30 22:01:56 +08:00
|
|
|
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.
|
|
|
|
|
|
2013-12-31 01:12:12 +08:00
|
|
|
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.
|
|
|
|
|
|
2014-06-26 18:09:05 +08:00
|
|
|
config EFI_RUNTIME_WRAPPERS
|
|
|
|
|
bool
|
|
|
|
|
|
2014-07-02 20:54:43 +08:00
|
|
|
config EFI_ARMSTUB
|
|
|
|
|
bool
|
|
|
|
|
|
2013-02-08 23:48:51 +08:00
|
|
|
endmenu
|
2013-12-16 22:39:40 +08:00
|
|
|
|
|
|
|
|
config UEFI_CPER
|
|
|
|
|
bool
|
