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 select FW_LOADER_USER_HELPER 68 help 69 Say m if you want to have the option of updating the BIOS for your 70 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP) 71 supporting application to communicate with the BIOS regarding the new 72 image for the image update to take effect. 73 See <file:Documentation/dell_rbu.txt> for more details on the driver. 74 75config DCDBAS 76 tristate "Dell Systems Management Base Driver" 77 depends on X86 78 help 79 The Dell Systems Management Base Driver provides a sysfs interface 80 for systems management software to perform System Management 81 Interrupts (SMIs) and Host Control Actions (system power cycle or 82 power off after OS shutdown) on certain Dell systems. 83 84 See <file:Documentation/dcdbas.txt> for more details on the driver 85 and the Dell systems on which Dell systems management software makes 86 use of this driver. 87 88 Say Y or M here to enable the driver for use by Dell systems 89 management software such as Dell OpenManage. 90 91config DMIID 92 bool "Export DMI identification via sysfs to userspace" 93 depends on DMI 94 default y 95 help 96 Say Y here if you want to query SMBIOS/DMI system identification 97 information from userspace through /sys/class/dmi/id/ or if you want 98 DMI-based module auto-loading. 99 100config DMI_SYSFS 101 tristate "DMI table support in sysfs" 102 depends on SYSFS && DMI 103 default n 104 help 105 Say Y or M here to enable the exporting of the raw DMI table 106 data via sysfs. This is useful for consuming the data without 107 requiring any access to /dev/mem at all. Tables are found 108 under /sys/firmware/dmi when this option is enabled and 109 loaded. 110 111config DMI_SCAN_MACHINE_NON_EFI_FALLBACK 112 bool 113 114config ISCSI_IBFT_FIND 115 bool "iSCSI Boot Firmware Table Attributes" 116 depends on X86 && ACPI 117 default n 118 help 119 This option enables the kernel to find the region of memory 120 in which the ISCSI Boot Firmware Table (iBFT) resides. This 121 is necessary for iSCSI Boot Firmware Table Attributes module to work 122 properly. 123 124config ISCSI_IBFT 125 tristate "iSCSI Boot Firmware Table Attributes module" 126 select ISCSI_BOOT_SYSFS 127 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL 128 default n 129 help 130 This option enables support for detection and exposing of iSCSI 131 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 132 detect iSCSI boot parameters dynamically during system boot, say Y. 133 Otherwise, say N. 134 135config QCOM_SCM 136 bool 137 depends on ARM || ARM64 138 139source "drivers/firmware/broadcom/Kconfig" 140source "drivers/firmware/google/Kconfig" 141source "drivers/firmware/efi/Kconfig" 142 143endmenu 144