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 tristate "EFI Variable Support via sysfs"
25 If you say Y here, you are able to get EFI (Extensible Firmware
26 Interface) variable information via sysfs. You may read,
27 write, create, and destroy EFI variables through this interface.
29 Note that using this driver in concert with efibootmgr requires
30 at least test release version 0.5.0-test3 or later, which is
31 available from Matt Domsch's website located at:
32 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
34 Subsequent efibootmgr releases may be found at:
35 <http://linux.dell.com/efibootmgr>
38 bool "Console device selection via EFI PCDP or HCDP table"
39 depends on ACPI && EFI && IA64
42 If your firmware supplies the PCDP table, and you want to
43 automatically use the primary console device it describes
44 as the Linux console, say Y here.
46 If your firmware supplies the HCDP table, and you want to
47 use the first serial port it describes as the Linux console,
48 say Y here. If your EFI ConOut path contains only a UART
49 device, it will become the console automatically. Otherwise,
50 you must specify the "console=hcdp" kernel boot argument.
52 Neither the PCDP nor the HCDP affects naming of serial devices,
53 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
54 on how the driver discovers devices.
56 You must also enable the appropriate drivers (serial, VGA, etc.)
58 See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
61 tristate "BIOS update support for DELL systems via sysfs"
65 Say m if you want to have the option of updating the BIOS for your
66 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
67 supporting application to communicate with the BIOS regarding the new
68 image for the image update to take effect.
69 See <file:Documentation/dell_rbu.txt> for more details on the driver.
72 tristate "Dell Systems Management Base Driver"
75 The Dell Systems Management Base Driver provides a sysfs interface
76 for systems management software to perform System Management
77 Interrupts (SMIs) and Host Control Actions (system power cycle or
78 power off after OS shutdown) on certain Dell systems.
80 See <file:Documentation/dcdbas.txt> for more details on the driver
81 and the Dell systems on which Dell systems management software makes
84 Say Y or M here to enable the driver for use by Dell systems
85 management software such as Dell OpenManage.
88 bool "Export DMI identification via sysfs to userspace"
92 Say Y here if you want to query SMBIOS/DMI system identification
93 information from userspace through /sys/class/dmi/id/ or if you want
94 DMI-based module auto-loading.
96 config ISCSI_IBFT_FIND
97 bool "iSCSI Boot Firmware Table Attributes"
101 This option enables the kernel to find the region of memory
102 in which the ISCSI Boot Firmware Table (iBFT) resides. This
103 is necessary for iSCSI Boot Firmware Table Attributes module to work
107 tristate "iSCSI Boot Firmware Table Attributes module"
108 depends on ISCSI_IBFT_FIND
111 This option enables support for detection and exposing of iSCSI
112 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
113 detect iSCSI boot parameters dynamically during system boot, say Y.