Searched full:booting (Results 1 – 25 of 476) sorted by relevance
12345678910>>...20
| /linux-6.14.4/Documentation/arch/riscv/ |
| D | boot.rst | 56 using the ``$a1`` register, or when booting with UEFI, it can be passed using the
72 - ``Ordered booting``: the firmware releases only one hart that will execute the
74 extension. The ordered booting method is the preferred booting method for
75 booting the RISC-V kernel because it can support CPU hotplug and kexec.
83 When booting with UEFI, the RISC-V kernel will use only the EFI memory map to
95 When booting with UEFI, the EFI stub requires the boot hartid in order to pass
113 When booting with UEFI, the devicetree is supplemented (or created) by the EFI
|
| /linux-6.14.4/Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,wcnss-pil.yaml | 61 PX regulator to be held on behalf of the booting of the WCNSS core
65 MX regulator to be held on behalf of the booting of the WCNSS core.
69 CX regulator to be held on behalf of the booting of the WCNSS core.
129 Reference to the regulator to be held on behalf of the booting WCNSS
134 Reference to the regulator to be held on behalf of the booting WCNSS
139 Reference to the regulator to be held on behalf of the booting WCNSS
144 Reference to the regulator to be held on behalf of the booting WCNSS
|
| D | wkup_m3_rproc.txt | 8 the firmware and booting of the CM3.
29 booting the wkup_m3 remote processor.
|
| /linux-6.14.4/Documentation/arch/arm/ |
| D | uefi.rst | 16 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-6.14.4/drivers/pci/ |
| D | Kconfig | 255 as booting with 'pci=pcie_bus_tune_off'.
270 is the same as booting with 'pci=pcie_bus_safe'.
279 parent. This is the same as booting with 'pci=pcie_bus_perf'.
290 This is the same as booting with 'pci=pcie_bus_peer2peer'.
|
| /linux-6.14.4/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm4908-partitions.yaml | 11 for regular booting, the other is treated as fallback.
14 firmware. System can use that information e.g. for booting or flashing
|
| D | linksys,ns-partitions.yaml | 11 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-6.14.4/arch/riscv/kernel/ |
| D | cpu_ops_spinwait.c | 29 * 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-6.14.4/arch/arm/boot/dts/samsung/ |
| D | exynos5422-cpus.dtsi | 11 * 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
|
| D | exynos5420-cpus.dtsi | 12 * 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
|
| /linux-6.14.4/Documentation/admin-guide/nfs/ |
| D | nfsroot.rst | 252 - 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-6.14.4/Documentation/power/ |
| D | swsusp-dmcrypt.rst | 122 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-6.14.4/include/linux/ |
| D | crash_dump.h | 57 * is_kdump_kernel() checks whether this kernel is booting after a panic of
62 * return true if CONFIG_CRASH_DUMP=y and if kernel is booting after a panic
72 /* is_vmcore_usable() checks if the kernel is booting after a panic and
|
| /linux-6.14.4/Documentation/arch/s390/ |
| D | zfcpdump.rst | 6 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-6.14.4/Documentation/devicetree/bindings/nvmem/layouts/ |
| D | u-boot,env.yaml | 11 configuration. They may be used for booting process, setup or keeping end user
47 description: Command to use for automatic booting
|
| /linux-6.14.4/Documentation/ABI/testing/ |
| D | sysfs-class-mic | 52 "booting" The MIC device has initiated booting a card OS.
97 booting this card OS, it is possible to pass kernel command line
|
| /linux-6.14.4/arch/arm/mach-s3c/ |
| D | init.c | 10 * NOTE: Code in this file is not used on S3C64xx when booting with
136 /* Not needed when booting with device tree. */ in s3c_arch_init()
|
| /linux-6.14.4/Documentation/translations/zh_TW/arch/arm/ |
| D | Booting | 1 Chinese translated version of Documentation/arch/arm/booting.rst
12 Documentation/arch/arm/booting.rst 的中文翻譯
|
| /linux-6.14.4/Documentation/translations/zh_CN/arch/arm/ |
| D | Booting | 1 Chinese translated version of Documentation/arch/arm/booting.rst
12 Documentation/arch/arm/booting.rst 的中文翻译
|
| /linux-6.14.4/Documentation/arch/powerpc/ |
| D | booting.rst | 3 DeviceTree Booting
65 implement "hot" booting of a new kernel from a previous
|
| /linux-6.14.4/arch/m68k/include/uapi/asm/ |
| D | bootinfo.h | 154 * bootstrap checks for a matching version of the interface before booting
161 * should be stepped. "Backwards-compatible" means that booting will work,
|
| /linux-6.14.4/Documentation/arch/xtensa/ |
| D | index.rst | 11 booting
|
| /linux-6.14.4/arch/powerpc/configs/ |
| D | security.config | 3 # This is the equivalent of booting with lockdown=integrity
|
| /linux-6.14.4/arch/arm64/boot/dts/qcom/ |
| D | pmi8996.dtsi | 9 * whose the bootloader has to check to continue booting
|
| /linux-6.14.4/Documentation/arch/loongarch/ |
| D | index.rst | 12 booting
|
12345678910>>...20