Version:  2.0.40 2.2.26 2.4.37 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15 3.16 3.17 3.18 3.19 4.0 4.1 4.2 4.3 4.4

Linux/drivers/firmware/efi/Kconfig

  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
 15           available from:
 16           <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
 17 
 18           Subsequent efibootmgr releases may be found at:
 19           <http://github.com/vathpela/efibootmgr>
 20 
 21 config EFI_ESRT
 22         bool
 23         depends on EFI && !IA64
 24         default y
 25 
 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 
 44 config EFI_RUNTIME_MAP
 45         bool "Export efi runtime maps to sysfs"
 46         depends on X86 && EFI && KEXEC_CORE
 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 
 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 
 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 
 84 config EFI_RUNTIME_WRAPPERS
 85         bool
 86 
 87 config EFI_ARMSTUB
 88         bool
 89 
 90 endmenu
 91 
 92 config UEFI_CPER
 93         bool

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us