Home
last modified time | relevance | path

Searched full:booting (Results 1 – 25 of 459) sorted by relevance

12345678910>>...19

/Linux-v6.1/Documentation/devicetree/bindings/remoteproc/
Dqcom,q6v5.txt56 modem. They are used for booting and authenticating the
124 booting of the Hexagon core
135 booting of the Hexagon core
143 booting of the Hexagon core
151 booting of the Hexagon core
Dqcom,wcnss-pil.txt49 booting of the WCNSS core
55 booting of the WCNSS core
109 booting of the WCNSS core
Dwkup_m3_rproc.txt8 the firmware and booting of the CM3.
29 booting the wkup_m3 remote processor.
/Linux-v6.1/Documentation/arm/
Duefi.rst16 Booting on a platform with firmware compliant with the UEFI specification
39 booting in non-UEFI environments.
46 When booting in UEFI mode, the stub deletes any memory nodes from a provided DT.
/Linux-v6.1/drivers/pci/
DKconfig224 as booting with 'pci=pcie_bus_tune_off'.
239 is the same as booting with 'pci=pcie_bus_safe'.
248 parent. This is the same as booting with 'pci=pcie_bus_perf'.
259 This is the same as booting with 'pci=pcie_bus_peer2peer'.
/Linux-v6.1/Documentation/devicetree/bindings/mtd/partitions/
Dbrcm,bcm4908-partitions.yaml11 for regular booting, the other is treated as fallback.
14 firmware. System can use that information e.g. for booting or flashing
Dlinksys,ns-partitions.yaml11 firmware partitions. One is used for regular booting, the other is treated as
15 firmware. System can use that information e.g. for booting or flashing
/Linux-v6.1/include/linux/
Dcrash_dump.h54 * is_kdump_kernel() checks whether this kernel is booting after a panic of
59 * return true if CONFIG_CRASH_DUMP=y and if kernel is booting after a panic
68 /* is_vmcore_usable() checks if the kernel is booting after a panic and
/Linux-v6.1/Documentation/devicetree/bindings/nvmem/
Du-boot,env.yaml11 configuration. They may be used for booting process, setup or keeping end user
47 description: Command to use for automatic booting
/Linux-v6.1/arch/arm/boot/dts/
Dexynos5420-cpus.dtsi12 * but particular boards choose different booting order.
15 * booting cluster (big or LITTLE) is chosen by IROM code by reading
16 * the gpg2-1 GPIO. By default all Exynos5422 based boards choose booting
Dexynos5422-cpus.dtsi11 * but particular boards choose different booting order.
14 * booting cluster (big or LITTLE) is chosen by IROM code by reading
15 * the gpg2-1 GPIO. By default all Exynos5422 based boards choose booting
/Linux-v6.1/arch/riscv/kernel/
Dcpu_ops_spinwait.c29 * spinwait booting is not the recommended approach for any platforms in cpu_update_secondary_bootdata()
30 * booting Linux in S-mode and can be disabled in the future. in cpu_update_secondary_bootdata()
/Linux-v6.1/Documentation/power/
Dswsusp-dmcrypt.rst122 We will not resume if booting with "noresume" or any parameters
138 file system and continue booting from there. I prefer to unmount
139 the initrd prior to continue booting but it is up to you to modify
/Linux-v6.1/Documentation/admin-guide/nfs/
Dnfsroot.rst252 - Booting from a floppy using syslinux
273 method of booting.
275 - Booting from a cdrom using isolinux
329 This is probably the most elegant way of booting a diskless client.
332 ROMs that support booting Linux over the network. However, there
/Linux-v6.1/Documentation/s390/
Dzfcpdump.rst6 dumps on SCSI disks. The dump process is initiated by booting a dump tool, which
17 system can then trigger a SCSI dump by booting the SCSI disk, where zfcpdump
/Linux-v6.1/Documentation/riscv/
Dboot-image-header.rst11 Write a complete booting guide.
61 - Image size is mandatory for boot loader to load kernel image. Booting will
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-class-mic52 "booting" The MIC device has initiated booting a card OS.
97 booting this card OS, it is possible to pass kernel command line
/Linux-v6.1/Documentation/translations/zh_CN/arm/
DBooting1 Chinese translated version of Documentation/arm/booting.rst
12 Documentation/arm/booting.rst 的中文翻译
/Linux-v6.1/arch/arm/mach-s3c/
Dinit.c10 * NOTE: Code in this file is not used on S3C64xx when booting with
160 /* Not needed when booting with device tree. */ in s3c_arch_init()
/Linux-v6.1/arch/m68k/include/uapi/asm/
Dbootinfo.h154 * bootstrap checks for a matching version of the interface before booting
161 * should be stepped. "Backwards-compatible" means that booting will work,
/Linux-v6.1/Documentation/powerpc/
Dbooting.rst3 DeviceTree Booting
65 implement "hot" booting of a new kernel from a previous
/Linux-v6.1/Documentation/xtensa/
Dindex.rst11 booting
/Linux-v6.1/arch/powerpc/configs/
Dsecurity.config1 # This is the equivalent of booting with lockdown=integrity
/Linux-v6.1/arch/arm64/boot/dts/qcom/
Dpmi8996.dtsi9 * whose the bootloader has to check to continue booting
/Linux-v6.1/Documentation/loongarch/
Dindex.rst12 booting

12345678910>>...19