Kconfig 3.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687
  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 EFI_VARS
  17. tristate "EFI Variable Support via sysfs"
  18. depends on EFI
  19. default n
  20. help
  21. If you say Y here, you are able to get EFI (Extensible Firmware
  22. Interface) variable information via sysfs. You may read,
  23. write, create, and destroy EFI variables through this interface.
  24. Note that using this driver in concert with efibootmgr requires
  25. at least test release version 0.5.0-test3 or later, which is
  26. available from Matt Domsch's website located at:
  27. <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
  28. Subsequent efibootmgr releases may be found at:
  29. <http://linux.dell.com/efibootmgr>
  30. config EFI_PCDP
  31. bool "Console device selection via EFI PCDP or HCDP table"
  32. depends on ACPI && EFI && IA64
  33. default y if IA64
  34. help
  35. If your firmware supplies the PCDP table, and you want to
  36. automatically use the primary console device it describes
  37. as the Linux console, say Y here.
  38. If your firmware supplies the HCDP table, and you want to
  39. use the first serial port it describes as the Linux console,
  40. say Y here. If your EFI ConOut path contains only a UART
  41. device, it will become the console automatically. Otherwise,
  42. you must specify the "console=hcdp" kernel boot argument.
  43. Neither the PCDP nor the HCDP affects naming of serial devices,
  44. so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  45. on how the driver discovers devices.
  46. You must also enable the appropriate drivers (serial, VGA, etc.)
  47. See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
  48. config DELL_RBU
  49. tristate "BIOS update support for DELL systems via sysfs"
  50. depends on X86
  51. select FW_LOADER
  52. help
  53. Say m if you want to have the option of updating the BIOS for your
  54. DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
  55. supporting application to communicate with the BIOS regarding the new
  56. image for the image update to take effect.
  57. See <file:Documentation/dell_rbu.txt> for more details on the driver.
  58. config DCDBAS
  59. tristate "Dell Systems Management Base Driver"
  60. depends on X86
  61. help
  62. The Dell Systems Management Base Driver provides a sysfs interface
  63. for systems management software to perform System Management
  64. Interrupts (SMIs) and Host Control Actions (system power cycle or
  65. power off after OS shutdown) on certain Dell systems.
  66. See <file:Documentation/dcdbas.txt> for more details on the driver
  67. and the Dell systems on which Dell systems management software makes
  68. use of this driver.
  69. Say Y or M here to enable the driver for use by Dell systems
  70. management software such as Dell OpenManage.
  71. endmenu