Lines Matching +full:boot +full:- +full:up
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
41 tristate "BIOS Enhanced Disk Drive calls determine boot disk"
46 BIOS tries boot from. This information is then exported via sysfs.
48 This option is experimental and is known to fail to boot on some
62 bool "Add firmware-provided memory map to sysfs" if EXPERT
65 Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
66 That memory map is used for example by kexec to set up parameter area
69 See also Documentation/ABI/testing/sysfs-firmware-memmap.
78 DMI-based module auto-loading.
95 bool "iSCSI Boot Firmware Table Attributes"
100 in which the ISCSI Boot Firmware Table (iBFT) resides. This
101 is necessary for iSCSI Boot Firmware Table Attributes module to work
105 tristate "iSCSI Boot Firmware Table Attributes module"
112 Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
113 detect iSCSI boot parameters dynamically during system boot, say Y.
164 The RSU provides a way for customers to update the boot
193 bootloader or kernel can show basic video-output during boot for
194 user-guidance and debugging. Historically, x86 used the VESA BIOS
195 Extensions and EFI-framebuffers for this, which are mostly limited
198 framebuffers so the new generic system-framebuffer drivers can be
201 drivers like efifb, vesafb and uvesafb can pick it up.
206 not be able to pick up generic system framebuffers if this option
234 Some devices (including most early Tegra-based consumer devices on
242 bindings for "tlm,trusted-foundations" for details on how to use it.
254 This driver communicates with the firmware on the Cortex-M3 secure