Kconfig 3.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788
  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 (EXPERIMENTAL)"
  8. depends on EXPERIMENTAL
  9. depends on !IA64
  10. help
  11. Say Y or M here if you want to enable BIOS Enhanced Disk Drive
  12. Services real mode BIOS calls to determine which disk
  13. BIOS tries boot from. This information is then exported via sysfs.
  14. This option is experimental and is known to fail to boot on some
  15. obscure configurations. Most disk controller BIOS vendors do
  16. not yet implement this feature.
  17. config EFI_VARS
  18. tristate "EFI Variable Support via sysfs"
  19. depends on EFI
  20. default n
  21. help
  22. If you say Y here, you are able to get EFI (Extensible Firmware
  23. Interface) variable information via sysfs. You may read,
  24. write, create, and destroy EFI variables through this interface.
  25. Note that using this driver in concert with efibootmgr requires
  26. at least test release version 0.5.0-test3 or later, which is
  27. available from Matt Domsch's website located at:
  28. <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
  29. Subsequent efibootmgr releases may be found at:
  30. <http://linux.dell.com/efibootmgr>
  31. config EFI_PCDP
  32. bool "Console device selection via EFI PCDP or HCDP table"
  33. depends on ACPI && EFI && IA64
  34. default y if IA64
  35. help
  36. If your firmware supplies the PCDP table, and you want to
  37. automatically use the primary console device it describes
  38. as the Linux console, say Y here.
  39. If your firmware supplies the HCDP table, and you want to
  40. use the first serial port it describes as the Linux console,
  41. say Y here. If your EFI ConOut path contains only a UART
  42. device, it will become the console automatically. Otherwise,
  43. you must specify the "console=hcdp" kernel boot argument.
  44. Neither the PCDP nor the HCDP affects naming of serial devices,
  45. so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  46. on how the driver discovers devices.
  47. You must also enable the appropriate drivers (serial, VGA, etc.)
  48. See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
  49. config DELL_RBU
  50. tristate "BIOS update support for DELL systems via sysfs"
  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 comunicate 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 || X86_64
  61. default m
  62. help
  63. The Dell Systems Management Base Driver provides a sysfs interface
  64. for systems management software to perform System Management
  65. Interrupts (SMIs) and Host Control Actions (system power cycle or
  66. power off after OS shutdown) on certain Dell systems.
  67. See <file:Documentation/dcdbas.txt> for more details on the driver
  68. and the Dell systems on which Dell systems management software makes
  69. use of this driver.
  70. Say Y or M here to enable the driver for use by Dell systems
  71. management software such as Dell OpenManage.
  72. endmenu