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