blob: 3e532002e4d1c01a3d21cd84c3a4a5e22e5e2440 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
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
Chris Wedgwood5d186392006-06-25 05:47:46 -07009 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080010 depends on X86
Linus Torvalds1da177e2005-04-16 15:20:36 -070011 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
Tim Gardner8c4dd602008-04-29 01:02:45 -070020config 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
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020029config FIRMWARE_MEMMAP
David Rientjes6a108a12011-01-20 14:44:16 -080030 bool "Add firmware-provided memory map to sysfs" if EXPERT
Mike Frysinger9b6e3e42009-12-14 18:01:16 -080031 default X86
Bernhard Walle69ac9cd2008-06-27 13:12:54 +020032 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070039config EFI_VARS
40 tristate "EFI Variable Support via sysfs"
41 depends on EFI
Matthew Garrett0635eb82013-04-15 13:09:45 -070042 select UCS2_STRING
Linus Torvalds1da177e2005-04-16 15:20:36 -070043 default n
44 help
45 If you say Y here, you are able to get EFI (Extensible Firmware
46 Interface) variable information via sysfs. You may read,
47 write, create, and destroy EFI variables through this interface.
48
49 Note that using this driver in concert with efibootmgr requires
50 at least test release version 0.5.0-test3 or later, which is
51 available from Matt Domsch's website located at:
52 <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
53
54 Subsequent efibootmgr releases may be found at:
55 <http://linux.dell.com/efibootmgr>
56
Seth Forsheeed9dc8c2013-03-07 11:40:17 -060057config EFI_VARS_PSTORE
58 bool "Register efivars backend for pstore"
59 depends on EFI_VARS && PSTORE
60 default y
61 help
62 Say Y here to enable use efivars as a backend to pstore. This
63 will allow writing console messages, crash dumps, or anything
64 else supported by pstore to EFI variables.
65
Seth Forsheeec0971b2013-03-11 16:17:50 -050066config EFI_VARS_PSTORE_DEFAULT_DISABLE
67 bool "Disable using efivars as a pstore backend by default"
68 depends on EFI_VARS_PSTORE
69 default n
70 help
71 Saying Y here will disable the use of efivars as a storage
72 backend for pstore by default. This setting can be overridden
73 using the efivars module's pstore_disable parameter.
74
Linus Torvalds1da177e2005-04-16 15:20:36 -070075config EFI_PCDP
76 bool "Console device selection via EFI PCDP or HCDP table"
77 depends on ACPI && EFI && IA64
78 default y if IA64
79 help
80 If your firmware supplies the PCDP table, and you want to
81 automatically use the primary console device it describes
82 as the Linux console, say Y here.
83
84 If your firmware supplies the HCDP table, and you want to
85 use the first serial port it describes as the Linux console,
86 say Y here. If your EFI ConOut path contains only a UART
87 device, it will become the console automatically. Otherwise,
88 you must specify the "console=hcdp" kernel boot argument.
89
90 Neither the PCDP nor the HCDP affects naming of serial devices,
91 so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
92 on how the driver discovers devices.
93
94 You must also enable the appropriate drivers (serial, VGA, etc.)
95
Justin P. Mattock631dd1a2010-10-18 11:03:14 +020096 See DIG64_HCDPv20_042804.pdf available from
97 <http://www.dig64.org/specifications/>
Linus Torvalds1da177e2005-04-16 15:20:36 -070098
Abhay Salunke6c54c282005-09-06 15:17:14 -070099config DELL_RBU
100 tristate "BIOS update support for DELL systems via sysfs"
Dave Jones6c52f132005-11-21 21:32:30 -0800101 depends on X86
Abhay Salunke6c54c282005-09-06 15:17:14 -0700102 select FW_LOADER
103 help
104 Say m if you want to have the option of updating the BIOS for your
105 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
Matt LaPlante09509602006-10-03 22:31:37 +0200106 supporting application to communicate with the BIOS regarding the new
Abhay Salunke6c54c282005-09-06 15:17:14 -0700107 image for the image update to take effect.
108 See <file:Documentation/dell_rbu.txt> for more details on the driver.
Doug Warzecha90563ec2005-09-06 15:17:15 -0700109
110config DCDBAS
111 tristate "Dell Systems Management Base Driver"
Brian Gerst0d078f62005-10-30 14:59:20 -0800112 depends on X86
Doug Warzecha90563ec2005-09-06 15:17:15 -0700113 help
114 The Dell Systems Management Base Driver provides a sysfs interface
115 for systems management software to perform System Management
116 Interrupts (SMIs) and Host Control Actions (system power cycle or
117 power off after OS shutdown) on certain Dell systems.
118
119 See <file:Documentation/dcdbas.txt> for more details on the driver
120 and the Dell systems on which Dell systems management software makes
121 use of this driver.
122
123 Say Y or M here to enable the driver for use by Dell systems
124 management software such as Dell OpenManage.
125
Lennart Poettering4f5c7912007-05-08 22:07:02 +0200126config DMIID
127 bool "Export DMI identification via sysfs to userspace"
128 depends on DMI
129 default y
130 help
131 Say Y here if you want to query SMBIOS/DMI system identification
132 information from userspace through /sys/class/dmi/id/ or if you want
133 DMI-based module auto-loading.
134
Mike Waychison948af1f2011-02-22 17:53:21 -0800135config DMI_SYSFS
136 tristate "DMI table support in sysfs"
137 depends on SYSFS && DMI
138 default n
139 help
140 Say Y or M here to enable the exporting of the raw DMI table
141 data via sysfs. This is useful for consuming the data without
142 requiring any access to /dev/mem at all. Tables are found
143 under /sys/firmware/dmi when this option is enabled and
144 loaded.
145
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700146config ISCSI_IBFT_FIND
147 bool "iSCSI Boot Firmware Table Attributes"
148 depends on X86
149 default n
150 help
151 This option enables the kernel to find the region of memory
152 in which the ISCSI Boot Firmware Table (iBFT) resides. This
153 is necessary for iSCSI Boot Firmware Table Attributes module to work
154 properly.
155
156config ISCSI_IBFT
157 tristate "iSCSI Boot Firmware Table Attributes module"
Mike Christieb33a84a2010-04-12 18:06:18 +0000158 select ISCSI_BOOT_SYSFS
Randy Dunlap3e0f6862010-10-13 18:07:16 -0700159 depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
Konrad Rzeszutek138fe4e2008-04-09 19:50:41 -0700160 default n
161 help
162 This option enables support for detection and exposing of iSCSI
163 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
164 detect iSCSI boot parameters dynamically during system boot, say Y.
165 Otherwise, say N.
166
Mike Waychison74c5b312011-04-29 17:39:19 -0700167source "drivers/firmware/google/Kconfig"
168
Linus Torvalds1da177e2005-04-16 15:20:36 -0700169endmenu