Kconfig 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135
  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 !IA64
  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 EMBEDDED
  26. default (X86_64 || X86_32)
  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_PCDP
  47. bool "Console device selection via EFI PCDP or HCDP table"
  48. depends on ACPI && EFI && IA64
  49. default y if IA64
  50. help
  51. If your firmware supplies the PCDP table, and you want to
  52. automatically use the primary console device it describes
  53. as the Linux console, say Y here.
  54. If your firmware supplies the HCDP table, and you want to
  55. use the first serial port it describes as the Linux console,
  56. say Y here. If your EFI ConOut path contains only a UART
  57. device, it will become the console automatically. Otherwise,
  58. you must specify the "console=hcdp" kernel boot argument.
  59. Neither the PCDP nor the HCDP affects naming of serial devices,
  60. so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  61. on how the driver discovers devices.
  62. You must also enable the appropriate drivers (serial, VGA, etc.)
  63. See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
  64. config DELL_RBU
  65. tristate "BIOS update support for DELL systems via sysfs"
  66. depends on X86
  67. select FW_LOADER
  68. help
  69. Say m if you want to have the option of updating the BIOS for your
  70. DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
  71. supporting application to communicate with the BIOS regarding the new
  72. image for the image update to take effect.
  73. See <file:Documentation/dell_rbu.txt> for more details on the driver.
  74. config DCDBAS
  75. tristate "Dell Systems Management Base Driver"
  76. depends on X86
  77. help
  78. The Dell Systems Management Base Driver provides a sysfs interface
  79. for systems management software to perform System Management
  80. Interrupts (SMIs) and Host Control Actions (system power cycle or
  81. power off after OS shutdown) on certain Dell systems.
  82. See <file:Documentation/dcdbas.txt> for more details on the driver
  83. and the Dell systems on which Dell systems management software makes
  84. use of this driver.
  85. Say Y or M here to enable the driver for use by Dell systems
  86. management software such as Dell OpenManage.
  87. config DMIID
  88. bool "Export DMI identification via sysfs to userspace"
  89. depends on DMI
  90. default y
  91. help
  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.
  95. config ISCSI_IBFT_FIND
  96. bool "iSCSI Boot Firmware Table Attributes"
  97. depends on X86
  98. default n
  99. help
  100. This option enables the kernel to find the region of memory
  101. in which the ISCSI Boot Firmware Table (iBFT) resides. This
  102. is necessary for iSCSI Boot Firmware Table Attributes module to work
  103. properly.
  104. config ISCSI_IBFT
  105. tristate "iSCSI Boot Firmware Table Attributes module"
  106. depends on ISCSI_IBFT_FIND
  107. default n
  108. help
  109. This option enables support for detection and exposing of iSCSI
  110. Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
  111. detect iSCSI boot parameters dynamically during system boot, say Y.
  112. Otherwise, say N.
  113. endmenu