11da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# 21da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# For a description of the syntax of this configuration file, 31da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# see Documentation/kbuild/kconfig-language.txt. 41da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds# 51da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 61da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsmenu "Firmware Drivers" 71da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 81da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig EDD 95d18639a833e9f034b055dcbb16a980be627f475Chris Wedgwood tristate "BIOS Enhanced Disk Drive calls determine boot disk" 109b6e3e42a48ea535c0ed79df32d1353d5e547bedMike Frysinger depends on X86 111da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 121da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Say Y or M here if you want to enable BIOS Enhanced Disk Drive 131da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Services real mode BIOS calls to determine which disk 141da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds BIOS tries boot from. This information is then exported via sysfs. 151da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 161da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds This option is experimental and is known to fail to boot on some 171da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds obscure configurations. Most disk controller BIOS vendors do 181da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds not yet implement this feature. 191da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 208c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardnerconfig EDD_OFF 218c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner bool "Sets default behavior for EDD detection to off" 228c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner depends on EDD 238c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner default n 248c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner help 258c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner Say Y if you want EDD disabled by default, even though it is compiled into the 268c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner kernel. Say N if you want EDD enabled by default. EDD can be dynamically set 278c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner using the kernel parameter 'edd={on|skipmbr|off}'. 288c4dd6068221cd1d0d90490ace80eb4344914a8cTim Gardner 2969ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walleconfig FIRMWARE_MEMMAP 306a108a14fa356ef607be308b68337939e56ea94eDavid Rientjes bool "Add firmware-provided memory map to sysfs" if EXPERT 319b6e3e42a48ea535c0ed79df32d1353d5e547bedMike Frysinger default X86 3269ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle help 3369ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap. 3469ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle That memory map is used for example by kexec to set up parameter area 3569ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle for the next kernel, but can also be used for debugging purposes. 3669ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle 3769ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle See also Documentation/ABI/testing/sysfs-firmware-memmap. 3869ac9cd629ca96e59f34eb4ccd12d00b2c8276a7Bernhard Walle 391da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig EFI_VARS 401da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds tristate "EFI Variable Support via sysfs" 411da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on EFI 421da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds default n 431da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 441da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If you say Y here, you are able to get EFI (Extensible Firmware 451da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Interface) variable information via sysfs. You may read, 461da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds write, create, and destroy EFI variables through this interface. 471da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 481da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Note that using this driver in concert with efibootmgr requires 491da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds at least test release version 0.5.0-test3 or later, which is 501da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds available from Matt Domsch's website located at: 511da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds <http://linux.dell.com/efibootmgr/testing/efibootmgr-0.5.0-test3.tar.gz> 521da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 531da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Subsequent efibootmgr releases may be found at: 541da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds <http://linux.dell.com/efibootmgr> 551da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 561da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsconfig EFI_PCDP 571da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds bool "Console device selection via EFI PCDP or HCDP table" 581da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds depends on ACPI && EFI && IA64 591da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds default y if IA64 601da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds help 611da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If your firmware supplies the PCDP table, and you want to 621da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds automatically use the primary console device it describes 631da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds as the Linux console, say Y here. 641da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 651da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds If your firmware supplies the HCDP table, and you want to 661da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds use the first serial port it describes as the Linux console, 671da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds say Y here. If your EFI ConOut path contains only a UART 681da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds device, it will become the console automatically. Otherwise, 691da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds you must specify the "console=hcdp" kernel boot argument. 701da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 711da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds Neither the PCDP nor the HCDP affects naming of serial devices, 721da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds so a serial console may be /dev/ttyS0, /dev/ttyS1, etc, depending 731da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds on how the driver discovers devices. 741da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 751da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds You must also enable the appropriate drivers (serial, VGA, etc.) 761da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 77631dd1a885b6d7e9f6f51b4e5b311c2bb04c323cJustin P. Mattock See DIG64_HCDPv20_042804.pdf available from 78631dd1a885b6d7e9f6f51b4e5b311c2bb04c323cJustin P. Mattock <http://www.dig64.org/specifications/> 791da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvalds 806c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunkeconfig DELL_RBU 816c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke tristate "BIOS update support for DELL systems via sysfs" 826c52f1377d9cc4bedec5d4e1e3b22756b8978399Dave Jones depends on X86 836c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke select FW_LOADER 846c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke help 856c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke Say m if you want to have the option of updating the BIOS for your 866c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke DELL system. Note you need a Dell OpenManage or Dell Update package (DUP) 87095096038d637c477ef3c1b674612bcbc4d60c2dMatt LaPlante supporting application to communicate with the BIOS regarding the new 886c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke image for the image update to take effect. 896c54c28e69f2a374ad708fba37cbe1c5bb94e283Abhay Salunke See <file:Documentation/dell_rbu.txt> for more details on the driver. 9090563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha 9190563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzechaconfig DCDBAS 9290563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha tristate "Dell Systems Management Base Driver" 930d078f6f96809c95c69b99d6605a502b0ac63d3dBrian Gerst depends on X86 9490563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha help 9590563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha The Dell Systems Management Base Driver provides a sysfs interface 9690563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha for systems management software to perform System Management 9790563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha Interrupts (SMIs) and Host Control Actions (system power cycle or 9890563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha power off after OS shutdown) on certain Dell systems. 9990563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha 10090563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha See <file:Documentation/dcdbas.txt> for more details on the driver 10190563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha and the Dell systems on which Dell systems management software makes 10290563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha use of this driver. 10390563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha 10490563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha Say Y or M here to enable the driver for use by Dell systems 10590563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha management software such as Dell OpenManage. 10690563ec4129f14d19f018240d1d3ff5c0e5e6392Doug Warzecha 1074f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poetteringconfig DMIID 1084f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering bool "Export DMI identification via sysfs to userspace" 1094f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering depends on DMI 1104f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering default y 1114f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering help 1124f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering Say Y here if you want to query SMBIOS/DMI system identification 1134f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering information from userspace through /sys/class/dmi/id/ or if you want 1144f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering DMI-based module auto-loading. 1154f5c791a850e5305a5b1b48d0e4b4de248dc96f9Lennart Poettering 116948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychisonconfig DMI_SYSFS 117948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison tristate "DMI table support in sysfs" 118948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison depends on SYSFS && DMI 119948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison default n 120948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison help 121948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison Say Y or M here to enable the exporting of the raw DMI table 122948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison data via sysfs. This is useful for consuming the data without 123948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison requiring any access to /dev/mem at all. Tables are found 124948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison under /sys/firmware/dmi when this option is enabled and 125948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison loaded. 126948af1f0bbc8526448e8cbe3f8d3bf211bdf5181Mike Waychison 127138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutekconfig ISCSI_IBFT_FIND 128138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek bool "iSCSI Boot Firmware Table Attributes" 129138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek depends on X86 130138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek default n 131138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek help 132138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek This option enables the kernel to find the region of memory 133138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek in which the ISCSI Boot Firmware Table (iBFT) resides. This 134138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek is necessary for iSCSI Boot Firmware Table Attributes module to work 135138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek properly. 136138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek 137138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutekconfig ISCSI_IBFT 138138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek tristate "iSCSI Boot Firmware Table Attributes module" 139b33a84a384776fb2593dac4d77c72050f9e181b0Mike Christie select ISCSI_BOOT_SYSFS 1403e0f686e6bf347eea4a41d7d415f003c2f42b1a0Randy Dunlap depends on ISCSI_IBFT_FIND && SCSI && SCSI_LOWLEVEL 141138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek default n 142138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek help 143138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek This option enables support for detection and exposing of iSCSI 144138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to 145138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek detect iSCSI boot parameters dynamically during system boot, say Y. 146138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek Otherwise, say N. 147138fe4e069798d9aa948a5402ff15e58f483ee4eKonrad Rzeszutek 14874c5b31c6618f01079212332b2e5f6c42f2d6307Mike Waychisonsource "drivers/firmware/google/Kconfig" 14974c5b31c6618f01079212332b2e5f6c42f2d6307Mike Waychison 1501da177e4c3f41524e886b7f1b8a0c1fc7321cacLinus Torvaldsendmenu 151