Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # For a description of the syntax of this configuration file, |
| 3 | # see Documentation/kbuild/kconfig-language.txt. |
| 4 | # |
| 5 | |
| 6 | menu "Firmware Drivers" |
| 7 | |
| 8 | config EDD |
Chris Wedgwood | 5d18639 | 2006-06-25 05:47:46 -0700 | [diff] [blame] | 9 | tristate "BIOS Enhanced Disk Drive calls determine boot disk" |
Mike Frysinger | 9b6e3e4 | 2009-12-14 18:01:16 -0800 | [diff] [blame] | 10 | depends on X86 |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 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 | |
Tim Gardner | 8c4dd60 | 2008-04-29 01:02:45 -0700 | [diff] [blame] | 20 | config 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 Walle | 69ac9cd | 2008-06-27 13:12:54 +0200 | [diff] [blame] | 29 | config FIRMWARE_MEMMAP |
| 30 | bool "Add firmware-provided memory map to sysfs" if EMBEDDED |
Mike Frysinger | 9b6e3e4 | 2009-12-14 18:01:16 -0800 | [diff] [blame] | 31 | default X86 |
Bernhard Walle | 69ac9cd | 2008-06-27 13:12:54 +0200 | [diff] [blame] | 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 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 39 | config EFI_VARS |
| 40 | tristate "EFI Variable Support via sysfs" |
| 41 | depends on EFI |
| 42 | default n |
| 43 | help |
| 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. |
| 47 | |
| 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> |
| 52 | |
| 53 | Subsequent efibootmgr releases may be found at: |
| 54 | <http://linux.dell.com/efibootmgr> |
| 55 | |
| 56 | config EFI_PCDP |
| 57 | bool "Console device selection via EFI PCDP or HCDP table" |
| 58 | depends on ACPI && EFI && IA64 |
| 59 | default y if IA64 |
| 60 | help |
| 61 | If your firmware supplies the PCDP table, and you want to |
| 62 | automatically use the primary console device it describes |
| 63 | as the Linux console, say Y here. |
| 64 | |
| 65 | If your firmware supplies the HCDP table, and you want to |
| 66 | use the first serial port it describes as the Linux console, |
| 67 | say Y here. If your EFI ConOut path contains only a UART |
| 68 | device, it will become the console automatically. Otherwise, |
| 69 | you must specify the "console=hcdp" kernel boot argument. |
| 70 | |
| 71 | Neither the PCDP nor the HCDP affects naming of serial devices, |
| 72 | so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending |
| 73 | on how the driver discovers devices. |
| 74 | |
| 75 | You must also enable the appropriate drivers (serial, VGA, etc.) |
| 76 | |
Justin P. Mattock | 631dd1a | 2010-10-18 11:03:14 +0200 | [diff] [blame] | 77 | See DIG64_HCDPv20_042804.pdf available from |
| 78 | <http://www.dig64.org/specifications/> |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 79 | |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 80 | config DELL_RBU |
| 81 | tristate "BIOS update support for DELL systems via sysfs" |
Dave Jones | 6c52f13 | 2005-11-21 21:32:30 -0800 | [diff] [blame] | 82 | depends on X86 |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 83 | select FW_LOADER |
| 84 | help |
| 85 | Say m if you want to have the option of updating the BIOS for your |
| 86 | DELL system. Note you need a Dell OpenManage or Dell Update package (DUP) |
Matt LaPlante | 0950960 | 2006-10-03 22:31:37 +0200 | [diff] [blame] | 87 | supporting application to communicate with the BIOS regarding the new |
Abhay Salunke | 6c54c28 | 2005-09-06 15:17:14 -0700 | [diff] [blame] | 88 | image for the image update to take effect. |
| 89 | See <file:Documentation/dell_rbu.txt> for more details on the driver. |
Doug Warzecha | 90563ec | 2005-09-06 15:17:15 -0700 | [diff] [blame] | 90 | |
| 91 | config DCDBAS |
| 92 | tristate "Dell Systems Management Base Driver" |
Brian Gerst | 0d078f6 | 2005-10-30 14:59:20 -0800 | [diff] [blame] | 93 | depends on X86 |
Doug Warzecha | 90563ec | 2005-09-06 15:17:15 -0700 | [diff] [blame] | 94 | help |
| 95 | The Dell Systems Management Base Driver provides a sysfs interface |
| 96 | for systems management software to perform System Management |
| 97 | Interrupts (SMIs) and Host Control Actions (system power cycle or |
| 98 | power off after OS shutdown) on certain Dell systems. |
| 99 | |
| 100 | See <file:Documentation/dcdbas.txt> for more details on the driver |
| 101 | and the Dell systems on which Dell systems management software makes |
| 102 | use of this driver. |
| 103 | |
| 104 | Say Y or M here to enable the driver for use by Dell systems |
| 105 | management software such as Dell OpenManage. |
| 106 | |
Lennart Poettering | 4f5c791 | 2007-05-08 22:07:02 +0200 | [diff] [blame] | 107 | config DMIID |
| 108 | bool "Export DMI identification via sysfs to userspace" |
| 109 | depends on DMI |
| 110 | default y |
| 111 | help |
| 112 | Say Y here if you want to query SMBIOS/DMI system identification |
| 113 | information from userspace through /sys/class/dmi/id/ or if you want |
| 114 | DMI-based module auto-loading. |
| 115 | |
Konrad Rzeszutek | 138fe4e | 2008-04-09 19:50:41 -0700 | [diff] [blame] | 116 | config ISCSI_IBFT_FIND |
| 117 | bool "iSCSI Boot Firmware Table Attributes" |
| 118 | depends on X86 |
| 119 | default n |
| 120 | help |
| 121 | This option enables the kernel to find the region of memory |
| 122 | in which the ISCSI Boot Firmware Table (iBFT) resides. This |
| 123 | is necessary for iSCSI Boot Firmware Table Attributes module to work |
| 124 | properly. |
| 125 | |
| 126 | config ISCSI_IBFT |
| 127 | tristate "iSCSI Boot Firmware Table Attributes module" |
Mike Christie | b33a84a | 2010-04-12 18:06:18 +0000 | [diff] [blame] | 128 | select ISCSI_BOOT_SYSFS |
Randy Dunlap | 3e0f686 | 2010-10-13 18:07:16 -0700 | [diff] [blame] | 129 | depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL |
Konrad Rzeszutek | 138fe4e | 2008-04-09 19:50:41 -0700 | [diff] [blame] | 130 | default n |
| 131 | help |
| 132 | This option enables support for detection and exposing of iSCSI |
| 133 | Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to |
| 134 | detect iSCSI boot parameters dynamically during system boot, say Y. |
| 135 | Otherwise, say N. |
| 136 | |
Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 137 | endmenu |