Lines Matching +full:boot +full:- +full:enabled
1 # SPDX-License-Identifier: GPL-2.0-only
4 # see Documentation/kbuild/kconfig-language.rst.
19 provides a mechanism for inter-processor communication between SCP
40 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
45 BIOS tries boot from. This information is then exported via sysfs.
47 This option is experimental and is known to fail to boot on some
57 kernel. Say N if you want EDD enabled by default. EDD can be dynamically set
61 bool "Add firmware-provided memory map to sysfs" if EXPERT
64 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
68 See also Documentation/ABI/testing/sysfs-firmware-memmap.
77 DMI-based module auto-loading.
87 under /sys/firmware/dmi when this option is enabled and
94 bool "iSCSI Boot Firmware Table Attributes"
99 in which the ISCSI Boot Firmware Table (iBFT) resides. This
100 is necessary for iSCSI Boot Firmware Table Attributes module to work
104 tristate "iSCSI Boot Firmware Table Attributes module"
111 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
112 detect iSCSI boot parameters dynamically during system boot, say Y.
130 found under /sys/firmware/fw_cfg when this option is enabled
163 The RSU provides a way for customers to update the boot
168 feature enabled and you want Linux user space control.
192 bootloader or kernel can show basic video-output during boot for
193 user-guidance and debugging. Historically, x86 used the VESA BIOS
194 Extensions and EFI-framebuffers for this, which are mostly limited
196 This option, if enabled, marks VGA/VBE/EFI framebuffers as generic
197 framebuffers so the new generic system-framebuffer drivers can be
209 and others enabled as fallback if a system framebuffer is
215 tristate "Always-On firmware protocol"
221 the kernel through the Always-On protocol, using hardware mailbox as a medium.
244 Some devices (including most early Tegra-based consumer devices on
252 bindings for "tlm,trusted-foundations" for details on how to use it.
264 This driver communicates with the firmware on the Cortex-M3 secure