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