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_PCDP 57 bool "Console device selection via EFI PCDP or HCDP table" 58 depends on ACPI && EFI && IA64 59 default y if IA64 60 help 61 If your firmware supplies the PCDP table, and you want to 62 automatically use the primary console device it describes 63 as the Linux console, say Y here. 64 65 If your firmware supplies the HCDP table, and you want to 66 use the first serial port it describes as the Linux console, 67 say Y here. If your EFI ConOut path contains only a UART 68 device, it will become the console automatically. Otherwise, 69 you must specify the "console=hcdp" kernel boot argument. 70 71 Neither the PCDP nor the HCDP affects naming of serial devices, 72 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending 73 on how the driver discovers devices. 74 75 You must also enable the appropriate drivers (serial, VGA, etc.) 76 77 See DIG64_HCDPv20_042804.pdf available from 78 <http://www.dig64.org/specifications/> 79 80config DELL_RBU 81 tristate "BIOS update support for DELL systems via sysfs" 82 depends on X86 83 select FW_LOADER 84 help 85 Say m if you want to have the option of updating the BIOS for your 86 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP) 87 supporting application to communicate with the BIOS regarding the new 88 image for the image update to take effect. 89 See <file:Documentation/dell_rbu.txt> for more details on the driver. 90 91config DCDBAS 92 tristate "Dell Systems Management Base Driver" 93 depends on X86 94 help 95 The Dell Systems Management Base Driver provides a sysfs interface 96 for systems management software to perform System Management 97 Interrupts (SMIs) and Host Control Actions (system power cycle or 98 power off after OS shutdown) on certain Dell systems. 99 100 See <file:Documentation/dcdbas.txt> for more details on the driver 101 and the Dell systems on which Dell systems management software makes 102 use of this driver. 103 104 Say Y or M here to enable the driver for use by Dell systems 105 management software such as Dell OpenManage. 106 107config DMIID 108 bool "Export DMI identification via sysfs to userspace" 109 depends on DMI 110 default y 111 help 112 Say Y here if you want to query SMBIOS/DMI system identification 113 information from userspace through /sys/class/dmi/id/ or if you want 114 DMI-based module auto-loading. 115 116config DMI_SYSFS 117 tristate "DMI table support in sysfs" 118 depends on SYSFS && DMI 119 default n 120 help 121 Say Y or M here to enable the exporting of the raw DMI table 122 data via sysfs. This is useful for consuming the data without 123 requiring any access to /dev/mem at all. Tables are found 124 under /sys/firmware/dmi when this option is enabled and 125 loaded. 126 127config ISCSI_IBFT_FIND 128 bool "iSCSI Boot Firmware Table Attributes" 129 depends on X86 130 default n 131 help 132 This option enables the kernel to find the region of memory 133 in which the ISCSI Boot Firmware Table (iBFT) resides. This 134 is necessary for iSCSI Boot Firmware Table Attributes module to work 135 properly. 136 137config ISCSI_IBFT 138 tristate "iSCSI Boot Firmware Table Attributes module" 139 select ISCSI_BOOT_SYSFS 140 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL 141 default n 142 help 143 This option enables support for detection and exposing of iSCSI 144 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 145 detect iSCSI boot parameters dynamically during system boot, say Y. 146 Otherwise, say N. 147 148source "drivers/firmware/google/Kconfig" 149 150endmenu 151