Kconfig 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144
  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_PCDP
  33. bool "Console device selection via EFI PCDP or HCDP table"
  34. depends on ACPI && EFI && IA64
  35. default y if IA64
  36. help
  37. If your firmware supplies the PCDP table, and you want to
  38. automatically use the primary console device it describes
  39. as the Linux console, say Y here.
  40. If your firmware supplies the HCDP table, and you want to
  41. use the first serial port it describes as the Linux console,
  42. say Y here. If your EFI ConOut path contains only a UART
  43. device, it will become the console automatically. Otherwise,
  44. you must specify the "console=hcdp" kernel boot argument.
  45. Neither the PCDP nor the HCDP affects naming of serial devices,
  46. so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  47. on how the driver discovers devices.
  48. You must also enable the appropriate drivers (serial, VGA, etc.)
  49. See DIG64_HCDPv20_042804.pdf available from
  50. <http://www.dig64.org/specifications/>
  51. config DELL_RBU
  52. tristate "BIOS update support for DELL systems via sysfs"
  53. depends on X86
  54. select FW_LOADER
  55. select FW_LOADER_USER_HELPER
  56. help
  57. Say m if you want to have the option of updating the BIOS for your
  58. DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
  59. supporting application to communicate with the BIOS regarding the new
  60. image for the image update to take effect.
  61. See <file:Documentation/dell_rbu.txt> for more details on the driver.
  62. config DCDBAS
  63. tristate "Dell Systems Management Base Driver"
  64. depends on X86
  65. help
  66. The Dell Systems Management Base Driver provides a sysfs interface
  67. for systems management software to perform System Management
  68. Interrupts (SMIs) and Host Control Actions (system power cycle or
  69. power off after OS shutdown) on certain Dell systems.
  70. See <file:Documentation/dcdbas.txt> for more details on the driver
  71. and the Dell systems on which Dell systems management software makes
  72. use of this driver.
  73. Say Y or M here to enable the driver for use by Dell systems
  74. management software such as Dell OpenManage.
  75. config DMIID
  76. bool "Export DMI identification via sysfs to userspace"
  77. depends on DMI
  78. default y
  79. help
  80. Say Y here if you want to query SMBIOS/DMI system identification
  81. information from userspace through /sys/class/dmi/id/ or if you want
  82. DMI-based module auto-loading.
  83. config DMI_SYSFS
  84. tristate "DMI table support in sysfs"
  85. depends on SYSFS && DMI
  86. default n
  87. help
  88. Say Y or M here to enable the exporting of the raw DMI table
  89. data via sysfs. This is useful for consuming the data without
  90. requiring any access to /dev/mem at all. Tables are found
  91. under /sys/firmware/dmi when this option is enabled and
  92. loaded.
  93. config DMI_SCAN_MACHINE_NON_EFI_FALLBACK
  94. bool
  95. config ISCSI_IBFT_FIND
  96. bool "iSCSI Boot Firmware Table Attributes"
  97. depends on X86 && ACPI
  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. select ISCSI_BOOT_SYSFS
  107. depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
  108. default n
  109. help
  110. This option enables support for detection and exposing of iSCSI
  111. Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
  112. detect iSCSI boot parameters dynamically during system boot, say Y.
  113. Otherwise, say N.
  114. config QCOM_SCM
  115. bool
  116. depends on ARM || ARM64
  117. source "drivers/firmware/broadcom/Kconfig"
  118. source "drivers/firmware/google/Kconfig"
  119. source "drivers/firmware/efi/Kconfig"
  120. endmenu