linux/drivers/firmware/Kconfig
<<
>>
Prefs
   1#
   2# For a description of the syntax of this configuration file,
   3# see Documentation/kbuild/kconfig-language.txt.
   4#
   5
   6menu "Firmware Drivers"
   7
   8config EDD
   9        tristate "BIOS Enhanced Disk Drive calls determine boot disk"
  10        depends on X86
  11        help
  12          Say Y or M here if you want to enable BIOS Enhanced Disk Drive
  13          Services real mode BIOS calls to determine which disk
  14          BIOS tries boot from.  This information is then exported via sysfs.
  15
  16          This option is experimental and is known to fail to boot on some
  17          obscure configurations. Most disk controller BIOS vendors do
  18          not yet implement this feature.
  19
  20config EDD_OFF
  21        bool "Sets default behavior for EDD detection to off"
  22        depends on EDD
  23        default n
  24        help
  25          Say Y if you want EDD disabled by default, even though it is compiled into the
  26          kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
  27          using the kernel parameter 'edd={on|skipmbr|off}'.
  28
  29config FIRMWARE_MEMMAP
  30    bool "Add firmware-provided memory map to sysfs" if EXPERT
  31    default X86
  32    help
  33      Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
  34      That memory map is used for example by kexec to set up parameter area
  35      for the next kernel, but can also be used for debugging purposes.
  36
  37      See also Documentation/ABI/testing/sysfs-firmware-memmap.
  38
  39config EFI_VARS
  40        tristate "EFI Variable Support via sysfs"
  41        depends on EFI
  42        select UCS2_STRING
  43        default n
  44        help
  45          If you say Y here, you are able to get EFI (Extensible Firmware
  46          Interface) variable information via sysfs.  You may read,
  47          write, create, and destroy EFI variables through this interface.
  48
  49          Note that using this driver in concert with efibootmgr requires
  50          at least test release version 0.5.0-test3 or later, which is
  51          available from Matt Domsch's website located at:
  52          <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz>
  53
  54          Subsequent efibootmgr releases may be found at:
  55          <http://linux.dell.com/efibootmgr>
  56
  57config EFI_VARS_PSTORE
  58        bool "Register efivars backend for pstore"
  59        depends on EFI_VARS && PSTORE
  60        default y
  61        help
  62          Say Y here to enable use efivars as a backend to pstore. This
  63          will allow writing console messages, crash dumps, or anything
  64          else supported by pstore to EFI variables.
  65
  66config EFI_VARS_PSTORE_DEFAULT_DISABLE
  67        bool "Disable using efivars as a pstore backend by default"
  68        depends on EFI_VARS_PSTORE
  69        default n
  70        help
  71          Saying Y here will disable the use of efivars as a storage
  72          backend for pstore by default. This setting can be overridden
  73          using the efivars module's pstore_disable parameter.
  74
  75config EFI_PCDP
  76        bool "Console device selection via EFI PCDP or HCDP table"
  77        depends on ACPI && EFI && IA64
  78        default y if IA64
  79        help
  80          If your firmware supplies the PCDP table, and you want to
  81          automatically use the primary console device it describes
  82          as the Linux console, say Y here.
  83
  84          If your firmware supplies the HCDP table, and you want to
  85          use the first serial port it describes as the Linux console,
  86          say Y here.  If your EFI ConOut path contains only a UART
  87          device, it will become the console automatically.  Otherwise,
  88          you must specify the "console=hcdp" kernel boot argument.
  89
  90          Neither the PCDP nor the HCDP affects naming of serial devices,
  91          so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending
  92          on how the driver discovers devices.
  93
  94          You must also enable the appropriate drivers (serial, VGA, etc.)
  95
  96          See DIG64_HCDPv20_042804.pdf available from
  97          <http://www.dig64.org/specifications/> 
  98
  99config DELL_RBU
 100        tristate "BIOS update support for DELL systems via sysfs"
 101        depends on X86
 102        select FW_LOADER
 103        help
 104         Say m if you want to have the option of updating the BIOS for your
 105         DELL system. Note you need a Dell OpenManage or Dell Update package (DUP)
 106         supporting application to communicate with the BIOS regarding the new
 107         image for the image update to take effect.
 108         See <file:Documentation/dell_rbu.txt> for more details on the driver.
 109
 110config DCDBAS
 111        tristate "Dell Systems Management Base Driver"
 112        depends on X86
 113        help
 114          The Dell Systems Management Base Driver provides a sysfs interface
 115          for systems management software to perform System Management
 116          Interrupts (SMIs) and Host Control Actions (system power cycle or
 117          power off after OS shutdown) on certain Dell systems.
 118
 119          See <file:Documentation/dcdbas.txt> for more details on the driver
 120          and the Dell systems on which Dell systems management software makes
 121          use of this driver.
 122
 123          Say Y or M here to enable the driver for use by Dell systems
 124          management software such as Dell OpenManage.
 125
 126config DMIID
 127    bool "Export DMI identification via sysfs to userspace"
 128    depends on DMI
 129    default y
 130        help
 131          Say Y here if you want to query SMBIOS/DMI system identification
 132          information from userspace through /sys/class/dmi/id/ or if you want
 133          DMI-based module auto-loading.
 134
 135config DMI_SYSFS
 136        tristate "DMI table support in sysfs"
 137        depends on SYSFS && DMI
 138        default n
 139        help
 140          Say Y or M here to enable the exporting of the raw DMI table
 141          data via sysfs.  This is useful for consuming the data without
 142          requiring any access to /dev/mem at all.  Tables are found
 143          under /sys/firmware/dmi when this option is enabled and
 144          loaded.
 145
 146config ISCSI_IBFT_FIND
 147        bool "iSCSI Boot Firmware Table Attributes"
 148        depends on X86
 149        default n
 150        help
 151          This option enables the kernel to find the region of memory
 152          in which the ISCSI Boot Firmware Table (iBFT) resides. This
 153          is necessary for iSCSI Boot Firmware Table Attributes module to work
 154          properly.
 155
 156config ISCSI_IBFT
 157        tristate "iSCSI Boot Firmware Table Attributes module"
 158        select ISCSI_BOOT_SYSFS
 159        depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL
 160        default n
 161        help
 162          This option enables support for detection and exposing of iSCSI
 163          Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
 164          detect iSCSI boot parameters dynamically during system boot, say Y.
 165          Otherwise, say N.
 166
 167source "drivers/firmware/google/Kconfig"
 168
 169endmenu
 170
lxr.linux.no kindly hosted by Redpill Linpro AS, provider of Linux consulting and operations services since 1995.