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
50 	tristate "BIOS Enhanced Disk Drive calls determine boot disk"
55 	  BIOS tries boot from.  This information is then exported via sysfs.
57 	  This option is experimental and is known to fail to boot on some
71     bool "Add firmware-provided memory map to sysfs" if EXPERT
74       Add the firmware-provided (unmodified) memory map to /sys/firmware/memmap.
75       That memory map is used for example by kexec to set up parameter area
78       See also Documentation/ABI/testing/sysfs-firmware-memmap.
93 	  you must specify the "console=hcdp" kernel boot argument.
111 	  DMI-based module auto-loading.
128 	bool "iSCSI Boot Firmware Table Attributes"
133 	  in which the ISCSI Boot Firmware Table (iBFT) resides. This
134 	  is necessary for iSCSI Boot Firmware Table Attributes module to work
138 	tristate "iSCSI Boot Firmware Table Attributes module"
145 	  Boot Firmware Table (iBFT) via sysfs to userspace. If you wish to
146 	  detect iSCSI boot parameters dynamically during system boot, say Y.
197 	  The RSU provides a way for customers to update the boot
223 	  warm-restart enter a special debug mode that allows the user to
239 	  bootloader or kernel can show basic video-output during boot for
240 	  user-guidance and debugging. Historically, x86 used the VESA BIOS
241 	  Extensions and EFI-framebuffers for this, which are mostly limited
244 	  framebuffers so the new generic system-framebuffer drivers can be
247 	  drivers like efifb, vesafb and uvesafb can pick it up.
252 	  not be able to pick up generic system framebuffers if this option
280 	  Some devices (including most early Tegra-based consumer devices on
288 	  bindings for "tlm,trusted-foundations" for details on how to use it.
300 	  This driver communicates with the firmware on the Cortex-M3 secure