1# 2# For a description of the syntax of this configuration file, 3# see Documentation/kbuild/kconfig-language.txt. 4# 5 6menu "Firmware Drivers" 7 8config EDD 9 tristate "BIOS Enhanced Disk Drive calls determine boot disk" 10 depends on X86 11 help 12 Say Y or M here if you want to enable BIOS Enhanced Disk Drive 13 Services real mode BIOS calls to determine which disk 14 BIOS tries boot from. This information is then exported via sysfs. 15 16 This option is experimental and is known to fail to boot on some 17 obscure configurations. Most disk controller BIOS vendors do 18 not yet implement this feature. 19 20config EDD_OFF 21 bool "Sets default behavior for EDD detection to off" 22 depends on EDD 23 default n 24 help 25 Say Y if you want EDD disabled by default, even though it is compiled into the 26 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set 27 using the kernel parameter 'edd={on|skipmbr|off}'. 28 29config FIRMWARE_MEMMAP 30 bool "Add firmware-provided memory map to sysfs" if EXPERT 31 default X86 32 help 33 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap. 34 That memory map is used for example by kexec to set up parameter area 35 for the next kernel, but can also be used for debugging purposes. 36 37 See also Documentation/ABI/testing/sysfs-firmware-memmap. 38 39config EFI_VARS 40 tristate "EFI Variable Support via sysfs" 41 depends on EFI 42 default n 43 help 44 If you say Y here, you are able to get EFI (Extensible Firmware 45 Interface) variable information via sysfs. You may read, 46 write, create, and destroy EFI variables through this interface. 47 48 Note that using this driver in concert with efibootmgr requires 49 at least test release version 0.5.0-test3 or later, which is 50 available from Matt Domsch's website located at: 51 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz> 52 53 Subsequent efibootmgr releases may be found at: 54 <http://linux.dell.com/efibootmgr> 55 56config EFI_VARS_PSTORE 57 bool "Register efivars backend for pstore" 58 depends on EFI_VARS && PSTORE 59 default y 60 help 61 Say Y here to enable use efivars as a backend to pstore. This 62 will allow writing console messages, crash dumps, or anything 63 else supported by pstore to EFI variables. 64 65config EFI_VARS_PSTORE_DEFAULT_DISABLE 66 bool "Disable using efivars as a pstore backend by default" 67 depends on EFI_VARS_PSTORE 68 default n 69 help 70 Saying Y here will disable the use of efivars as a storage 71 backend for pstore by default. This setting can be overridden 72 using the efivars module's pstore_disable parameter. 73 74config EFI_PCDP 75 bool "Console device selection via EFI PCDP or HCDP table" 76 depends on ACPI && EFI && IA64 77 default y if IA64 78 help 79 If your firmware supplies the PCDP table, and you want to 80 automatically use the primary console device it describes 81 as the Linux console, say Y here. 82 83 If your firmware supplies the HCDP table, and you want to 84 use the first serial port it describes as the Linux console, 85 say Y here. If your EFI ConOut path contains only a UART 86 device, it will become the console automatically. Otherwise, 87 you must specify the "console=hcdp" kernel boot argument. 88 89 Neither the PCDP nor the HCDP affects naming of serial devices, 90 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending 91 on how the driver discovers devices. 92 93 You must also enable the appropriate drivers (serial, VGA, etc.) 94 95 See DIG64_HCDPv20_042804.pdf available from 96 <http://www.dig64.org/specifications/> 97 98config DELL_RBU 99 tristate "BIOS update support for DELL systems via sysfs" 100 depends on X86 101 select FW_LOADER 102 help 103 Say m if you want to have the option of updating the BIOS for your 104 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP) 105 supporting application to communicate with the BIOS regarding the new 106 image for the image update to take effect. 107 See <file:Documentation/dell_rbu.txt> for more details on the driver. 108 109config DCDBAS 110 tristate "Dell Systems Management Base Driver" 111 depends on X86 112 help 113 The Dell Systems Management Base Driver provides a sysfs interface 114 for systems management software to perform System Management 115 Interrupts (SMIs) and Host Control Actions (system power cycle or 116 power off after OS shutdown) on certain Dell systems. 117 118 See <file:Documentation/dcdbas.txt> for more details on the driver 119 and the Dell systems on which Dell systems management software makes 120 use of this driver. 121 122 Say Y or M here to enable the driver for use by Dell systems 123 management software such as Dell OpenManage. 124 125config DMIID 126 bool "Export DMI identification via sysfs to userspace" 127 depends on DMI 128 default y 129 help 130 Say Y here if you want to query SMBIOS/DMI system identification 131 information from userspace through /sys/class/dmi/id/ or if you want 132 DMI-based module auto-loading. 133 134config DMI_SYSFS 135 tristate "DMI table support in sysfs" 136 depends on SYSFS && DMI 137 default n 138 help 139 Say Y or M here to enable the exporting of the raw DMI table 140 data via sysfs. This is useful for consuming the data without 141 requiring any access to /dev/mem at all. Tables are found 142 under /sys/firmware/dmi when this option is enabled and 143 loaded. 144 145config ISCSI_IBFT_FIND 146 bool "iSCSI Boot Firmware Table Attributes" 147 depends on X86 148 default n 149 help 150 This option enables the kernel to find the region of memory 151 in which the ISCSI Boot Firmware Table (iBFT) resides. This 152 is necessary for iSCSI Boot Firmware Table Attributes module to work 153 properly. 154 155config ISCSI_IBFT 156 tristate "iSCSI Boot Firmware Table Attributes module" 157 select ISCSI_BOOT_SYSFS 158 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL 159 default n 160 help 161 This option enables support for detection and exposing of iSCSI 162 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 163 detect iSCSI boot parameters dynamically during system boot, say Y. 164 Otherwise, say N. 165 166source "drivers/firmware/google/Kconfig" 167 168endmenu 169