Kconfig 5.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169
  1. #
  2. # For a description of the syntax of this configuration file,
  3. # see Documentation/kbuild/kconfig-language.txt.
  4. #
  5. menu "Firmware Drivers"
  6. config EDD
  7. tristate "BIOS Enhanced Disk Drive calls determine boot disk"
  8. depends on X86
  9. help
  10. Say Y or M here if you want to enable BIOS Enhanced Disk Drive
  11. Services real mode BIOS calls to determine which disk
  12. BIOS tries boot from. This information is then exported via sysfs.
  13. This option is experimental and is known to fail to boot on some
  14. obscure configurations. Most disk controller BIOS vendors do
  15. not yet implement this feature.
  16. config EDD_OFF
  17. bool "Sets default behavior for EDD detection to off"
  18. depends on EDD
  19. default n
  20. help
  21. Say Y if you want EDD disabled by default, even though it is compiled into the
  22. kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
  23. using the kernel parameter 'edd={on|skipmbr|off}'.
  24. config FIRMWARE_MEMMAP
  25. bool "Add firmware-provided memory map to sysfs" if EXPERT
  26. default X86
  27. help
  28. Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
  29. That memory map is used for example by kexec to set up parameter area
  30. for the next kernel, but can also be used for debugging purposes.
  31. See also Documentation/ABI/testing/sysfs-firmware-memmap.
  32. config EFI_VARS
  33. tristate "EFI Variable Support via sysfs"
  34. depends on EFI
  35. default n
  36. help
  37. If you say Y here, you are able to get EFI (Extensible Firmware
  38. Interface) variable information via sysfs. You may read,
  39. write, create, and destroy EFI variables through this interface.
  40. Note that using this driver in concert with efibootmgr requires
  41. at least test release version 0.5.0-test3 or later, which is
  42. available from Matt Domsch's website located at:
  43. <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
  44. Subsequent efibootmgr releases may be found at:
  45. <http://linux.dell.com/efibootmgr>
  46. config EFI_VARS_PSTORE
  47. bool "Register efivars backend for pstore"
  48. depends on EFI_VARS && PSTORE
  49. default y
  50. help
  51. Say Y here to enable use efivars as a backend to pstore. This
  52. will allow writing console messages, crash dumps, or anything
  53. else supported by pstore to EFI variables.
  54. config EFI_VARS_PSTORE_DEFAULT_DISABLE
  55. bool "Disable using efivars as a pstore backend by default"
  56. depends on EFI_VARS_PSTORE
  57. default n
  58. help
  59. Saying Y here will disable the use of efivars as a storage
  60. backend for pstore by default. This setting can be overridden
  61. using the efivars module's pstore_disable parameter.
  62. config EFI_PCDP
  63. bool "Console device selection via EFI PCDP or HCDP table"
  64. depends on ACPI && EFI && IA64
  65. default y if IA64
  66. help
  67. If your firmware supplies the PCDP table, and you want to
  68. automatically use the primary console device it describes
  69. as the Linux console, say Y here.
  70. If your firmware supplies the HCDP table, and you want to
  71. use the first serial port it describes as the Linux console,
  72. say Y here. If your EFI ConOut path contains only a UART
  73. device, it will become the console automatically. Otherwise,
  74. you must specify the "console=hcdp" kernel boot argument.
  75. Neither the PCDP nor the HCDP affects naming of serial devices,
  76. so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  77. on how the driver discovers devices.
  78. You must also enable the appropriate drivers (serial, VGA, etc.)
  79. See DIG64_HCDPv20_042804.pdf available from
  80. <http://www.dig64.org/specifications/>
  81. config DELL_RBU
  82. tristate "BIOS update support for DELL systems via sysfs"
  83. depends on X86
  84. select FW_LOADER
  85. help
  86. Say m if you want to have the option of updating the BIOS for your
  87. DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
  88. supporting application to communicate with the BIOS regarding the new
  89. image for the image update to take effect.
  90. See <file:Documentation/dell_rbu.txt> for more details on the driver.
  91. config DCDBAS
  92. tristate "Dell Systems Management Base Driver"
  93. depends on X86
  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. See <file:Documentation/dcdbas.txt> for more details on the driver
  100. and the Dell systems on which Dell systems management software makes
  101. use of this driver.
  102. Say Y or M here to enable the driver for use by Dell systems
  103. management software such as Dell OpenManage.
  104. config DMIID
  105. bool "Export DMI identification via sysfs to userspace"
  106. depends on DMI
  107. default y
  108. help
  109. Say Y here if you want to query SMBIOS/DMI system identification
  110. information from userspace through /sys/class/dmi/id/ or if you want
  111. DMI-based module auto-loading.
  112. config DMI_SYSFS
  113. tristate "DMI table support in sysfs"
  114. depends on SYSFS && DMI
  115. default n
  116. help
  117. Say Y or M here to enable the exporting of the raw DMI table
  118. data via sysfs. This is useful for consuming the data without
  119. requiring any access to /dev/mem at all. Tables are found
  120. under /sys/firmware/dmi when this option is enabled and
  121. loaded.
  122. config ISCSI_IBFT_FIND
  123. bool "iSCSI Boot Firmware Table Attributes"
  124. depends on X86
  125. default n
  126. help
  127. This option enables the kernel to find the region of memory
  128. in which the ISCSI Boot Firmware Table (iBFT) resides. This
  129. is necessary for iSCSI Boot Firmware Table Attributes module to work
  130. properly.
  131. config ISCSI_IBFT
  132. tristate "iSCSI Boot Firmware Table Attributes module"
  133. select ISCSI_BOOT_SYSFS
  134. depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
  135. default n
  136. help
  137. This option enables support for detection and exposing of iSCSI
  138. Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
  139. detect iSCSI boot parameters dynamically during system boot, say Y.
  140. Otherwise, say N.
  141. source "drivers/firmware/google/Kconfig"
  142. endmenu