2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 menu "Firmware Drivers"
9 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
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.
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.
21 bool "Sets default behavior for EDD detection to off"
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}'.
29 config FIRMWARE_MEMMAP
30 bool "Add firmware-provided memory map to sysfs" if EXPERT
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.
37 See also Documentation/ABI/testing/sysfs-firmware-memmap.
40 tristate "EFI Variable Support via sysfs"
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.
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>
53 Subsequent efibootmgr releases may be found at:
54 <http://linux.dell.com/efibootmgr>
56 config EFI_VARS_PSTORE
57 bool "Register efivars backend for pstore"
58 depends on EFI_VARS && PSTORE
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.
66 bool "Console device selection via EFI PCDP or HCDP table"
67 depends on ACPI && EFI && IA64
70 If your firmware supplies the PCDP table, and you want to
71 automatically use the primary console device it describes
72 as the Linux console, say Y here.
74 If your firmware supplies the HCDP table, and you want to
75 use the first serial port it describes as the Linux console,
76 say Y here. If your EFI ConOut path contains only a UART
77 device, it will become the console automatically. Otherwise,
78 you must specify the "console=hcdp" kernel boot argument.
80 Neither the PCDP nor the HCDP affects naming of serial devices,
81 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
82 on how the driver discovers devices.
84 You must also enable the appropriate drivers (serial, VGA, etc.)
86 See DIG64_HCDPv20_042804.pdf available from
87 <http://www.dig64.org/specifications/>
90 tristate "BIOS update support for DELL systems via sysfs"
94 Say m if you want to have the option of updating the BIOS for your
95 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
96 supporting application to communicate with the BIOS regarding the new
97 image for the image update to take effect.
98 See <file:Documentation/dell_rbu.txt> for more details on the driver.
101 tristate "Dell Systems Management Base Driver"
104 The Dell Systems Management Base Driver provides a sysfs interface
105 for systems management software to perform System Management
106 Interrupts (SMIs) and Host Control Actions (system power cycle or
107 power off after OS shutdown) on certain Dell systems.
109 See <file:Documentation/dcdbas.txt> for more details on the driver
110 and the Dell systems on which Dell systems management software makes
113 Say Y or M here to enable the driver for use by Dell systems
114 management software such as Dell OpenManage.
117 bool "Export DMI identification via sysfs to userspace"
121 Say Y here if you want to query SMBIOS/DMI system identification
122 information from userspace through /sys/class/dmi/id/ or if you want
123 DMI-based module auto-loading.
126 tristate "DMI table support in sysfs"
127 depends on SYSFS && DMI
130 Say Y or M here to enable the exporting of the raw DMI table
131 data via sysfs. This is useful for consuming the data without
132 requiring any access to /dev/mem at all. Tables are found
133 under /sys/firmware/dmi when this option is enabled and
136 config ISCSI_IBFT_FIND
137 bool "iSCSI Boot Firmware Table Attributes"
141 This option enables the kernel to find the region of memory
142 in which the ISCSI Boot Firmware Table (iBFT) resides. This
143 is necessary for iSCSI Boot Firmware Table Attributes module to work
147 tristate "iSCSI Boot Firmware Table Attributes module"
148 select ISCSI_BOOT_SYSFS
149 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
152 This option enables support for detection and exposing of iSCSI
153 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
154 detect iSCSI boot parameters dynamically during system boot, say Y.
158 tristate "SigmaStudio firmware loader"
163 Enable helper functions for working with Analog Devices SigmaDSP
164 parts and binary firmwares produced by Analog Devices SigmaStudio.
166 If unsure, say N here. Drivers that need these helpers will select
167 this option automatically.
169 source "drivers/firmware/google/Kconfig"