xref: /openbmc/linux/drivers/firmware/Kconfig (revision 0d078f6f)
11da177e4SLinus Torvalds#
21da177e4SLinus Torvalds# For a description of the syntax of this configuration file,
31da177e4SLinus Torvalds# see Documentation/kbuild/kconfig-language.txt.
41da177e4SLinus Torvalds#
51da177e4SLinus Torvalds
61da177e4SLinus Torvaldsmenu "Firmware Drivers"
71da177e4SLinus Torvalds
81da177e4SLinus Torvaldsconfig EDD
91da177e4SLinus Torvalds	tristate "BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL)"
101da177e4SLinus Torvalds	depends on EXPERIMENTAL
111da177e4SLinus Torvalds	depends on !IA64
121da177e4SLinus Torvalds	help
131da177e4SLinus Torvalds	  Say Y or M here if you want to enable BIOS Enhanced Disk Drive
141da177e4SLinus Torvalds	  Services real mode BIOS calls to determine which disk
151da177e4SLinus Torvalds	  BIOS tries boot from.  This information is then exported via sysfs.
161da177e4SLinus Torvalds
171da177e4SLinus Torvalds	  This option is experimental and is known to fail to boot on some
181da177e4SLinus Torvalds          obscure configurations. Most disk controller BIOS vendors do
191da177e4SLinus Torvalds          not yet implement this feature.
201da177e4SLinus Torvalds
211da177e4SLinus Torvaldsconfig EFI_VARS
221da177e4SLinus Torvalds	tristate "EFI Variable Support via sysfs"
231da177e4SLinus Torvalds	depends on EFI
241da177e4SLinus Torvalds	default n
251da177e4SLinus Torvalds	help
261da177e4SLinus Torvalds	  If you say Y here, you are able to get EFI (Extensible Firmware
271da177e4SLinus Torvalds	  Interface) variable information via sysfs.  You may read,
281da177e4SLinus Torvalds	  write, create, and destroy EFI variables through this interface.
291da177e4SLinus Torvalds
301da177e4SLinus Torvalds	  Note that using this driver in concert with efibootmgr requires
311da177e4SLinus Torvalds	  at least test release version 0.5.0-test3 or later, which is
321da177e4SLinus Torvalds	  available from Matt Domsch's website located at:
331da177e4SLinus Torvalds	  <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
341da177e4SLinus Torvalds
351da177e4SLinus Torvalds	  Subsequent efibootmgr releases may be found at:
361da177e4SLinus Torvalds	  <http://linux.dell.com/efibootmgr>
371da177e4SLinus Torvalds
381da177e4SLinus Torvaldsconfig EFI_PCDP
391da177e4SLinus Torvalds	bool "Console device selection via EFI PCDP or HCDP table"
401da177e4SLinus Torvalds	depends on ACPI && EFI && IA64
411da177e4SLinus Torvalds	default y if IA64
421da177e4SLinus Torvalds	help
431da177e4SLinus Torvalds	  If your firmware supplies the PCDP table, and you want to
441da177e4SLinus Torvalds	  automatically use the primary console device it describes
451da177e4SLinus Torvalds	  as the Linux console, say Y here.
461da177e4SLinus Torvalds
471da177e4SLinus Torvalds	  If your firmware supplies the HCDP table, and you want to
481da177e4SLinus Torvalds	  use the first serial port it describes as the Linux console,
491da177e4SLinus Torvalds	  say Y here.  If your EFI ConOut path contains only a UART
501da177e4SLinus Torvalds	  device, it will become the console automatically.  Otherwise,
511da177e4SLinus Torvalds	  you must specify the "console=hcdp" kernel boot argument.
521da177e4SLinus Torvalds
531da177e4SLinus Torvalds	  Neither the PCDP nor the HCDP affects naming of serial devices,
541da177e4SLinus Torvalds	  so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
551da177e4SLinus Torvalds	  on how the driver discovers devices.
561da177e4SLinus Torvalds
571da177e4SLinus Torvalds	  You must also enable the appropriate drivers (serial, VGA, etc.)
581da177e4SLinus Torvalds
591da177e4SLinus Torvalds	  See <http://www.dig64.org/specifications/DIG64_HCDPv20_042804.pdf>
601da177e4SLinus Torvalds
616c54c28eSAbhay Salunkeconfig DELL_RBU
626c54c28eSAbhay Salunke	tristate "BIOS update support for DELL systems via sysfs"
636c54c28eSAbhay Salunke	select FW_LOADER
646c54c28eSAbhay Salunke	help
656c54c28eSAbhay Salunke	 Say m if you want to have the option of updating the BIOS for your
666c54c28eSAbhay Salunke	 DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
676c54c28eSAbhay Salunke	 supporting application to comunicate with the BIOS regarding the new
686c54c28eSAbhay Salunke	 image for the image update to take effect.
696c54c28eSAbhay Salunke	 See <file:Documentation/dell_rbu.txt> for more details on the driver.
7090563ec4SDoug Warzecha
7190563ec4SDoug Warzechaconfig DCDBAS
7290563ec4SDoug Warzecha	tristate "Dell Systems Management Base Driver"
73*0d078f6fSBrian Gerst	depends on X86
7490563ec4SDoug Warzecha	default m
7590563ec4SDoug Warzecha	help
7690563ec4SDoug Warzecha	  The Dell Systems Management Base Driver provides a sysfs interface
7790563ec4SDoug Warzecha	  for systems management software to perform System Management
7890563ec4SDoug Warzecha	  Interrupts (SMIs) and Host Control Actions (system power cycle or
7990563ec4SDoug Warzecha	  power off after OS shutdown) on certain Dell systems.
8090563ec4SDoug Warzecha
8190563ec4SDoug Warzecha	  See <file:Documentation/dcdbas.txt> for more details on the driver
8290563ec4SDoug Warzecha	  and the Dell systems on which Dell systems management software makes
8390563ec4SDoug Warzecha	  use of this driver.
8490563ec4SDoug Warzecha
8590563ec4SDoug Warzecha	  Say Y or M here to enable the driver for use by Dell systems
8690563ec4SDoug Warzecha	  management software such as Dell OpenManage.
8790563ec4SDoug Warzecha
881da177e4SLinus Torvaldsendmenu
89