drivers/firmware/Kconfig

   1 #
   2 # For a description of the syntax of this configuration file,
   3 # see Documentation/kbuild/kconfig-language.txt.
   4 #
   5
   6 menu "Firmware Drivers"
   7
   8 config EDD
   9         tristate "BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL)"
  10         depends on EXPERIMENTAL
  11         depends on !IA64
  12         help
  13           Say Y or M here if you want to enable BIOS Enhanced Disk Drive
  14           Services real mode BIOS calls to determine which disk
  15           BIOS tries boot from.  This information is then exported via sysfs.
  16
  17           This option is experimental and is known to fail to boot on some
  18           obscure configurations. Most disk controller BIOS vendors do
  19           not yet implement this feature.
  20
  21 config EFI_VARS
  22         tristate "EFI Variable Support via sysfs"
  23         depends on EFI
  24         default n
  25         help
  26           If you say Y here, you are able to get EFI (Extensible Firmware
  27           Interface) variable information via sysfs.  You may read,
  28           write, create, and destroy EFI variables through this interface.
  29
  30           Note that using this driver in concert with efibootmgr requires
  31           at least test release version 0.5.0-test3 or later, which is
  32           available from Matt Domsch's website located at:
  33           <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
  34
  35           Subsequent efibootmgr releases may be found at:
  36           <http://linux.dell.com/efibootmgr>
  37
  38 config EFI_PCDP
  39         bool "Console device selection via EFI PCDP or HCDP table"
  40         depends on ACPI && EFI && IA64
  41         default y if IA64
  42         help
  43           If your firmware supplies the PCDP table, and you want to
  44           automatically use the primary console device it describes
  45           as the Linux console, say Y here.
  46
  47           If your firmware supplies the HCDP table, and you want to
  48           use the first serial port it describes as the Linux console,
  49           say Y here.  If your EFI ConOut path contains only a UART
  50           device, it will become the console automatically.  Otherwise,
  51           you must specify the "console=hcdp" kernel boot argument.
  52
  53           Neither the PCDP nor the HCDP affects naming of serial devices,
  54           so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  55           on how the driver discovers devices.
  56
  57           You must also enable the appropriate drivers (serial, VGA, etc.)
  58
  59           See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
  60
  61 endmenu