/linux/Documentation/arch/riscv/ |
H A 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/Documentation/arch/arm/ |
H A 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/drivers/pci/ |
H A D | Kconfig | 265 as booting with 'pci=pcie_bus_tune_off'. 280 is the same as booting with 'pci=pcie_bus_safe'. 289 parent. This is the same as booting with 'pci=pcie_bus_perf'. 300 This is the same as booting with 'pci=pcie_bus_peer2peer'.
|
/linux/arch/arm/boot/dts/samsung/ |
H A 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
|
H A 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/Documentation/devicetree/bindings/mtd/partitions/ |
H A 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
|
H A 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
|
/linux/Documentation/admin-guide/nfs/ |
H A 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/Documentation/power/ |
H A 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/Documentation/devicetree/bindings/remoteproc/ |
H A D | wkup_m3_rproc.txt | 8 the firmware and booting of the CM3. 29 booting the wkup_m3 remote processor.
|
/linux/include/linux/ |
H A D | crash_dump.h | 59 * is_kdump_kernel() checks whether this kernel is booting after a panic of 64 * return true if CONFIG_CRASH_DUMP=y and if kernel is booting after a panic 74 /* is_vmcore_usable() checks if the kernel is booting after a panic and
|
/linux/Documentation/arch/s390/ |
H A 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/Documentation/devicetree/bindings/nvmem/layouts/ |
H A 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/Documentation/ABI/testing/ |
H A 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/arch/arm/mach-s3c/ |
H A 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/Documentation/translations/zh_TW/arch/arm/ |
H A D | Booting | 1 Chinese translated version of Documentation/arch/arm/booting.rst 12 Documentation/arch/arm/booting.rst 的中文翻譯
|
/linux/Documentation/translations/zh_CN/arch/arm/ |
H A D | Booting | 1 Chinese translated version of Documentation/arch/arm/booting.rst 12 Documentation/arch/arm/booting.rst 的中文翻译
|
/linux/arch/m68k/include/uapi/asm/ |
H A 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/Documentation/translations/zh_CN/arch/arm64/ |
H A D | booting.txt | 1 Chinese translated version of Documentation/arch/arm64/booting.rst 13 Documentation/arch/arm64/booting.rst 的中文翻译
|
/linux/Documentation/translations/zh_TW/arch/arm64/ |
H A D | booting.txt | 3 Chinese translated version of Documentation/arch/arm64/booting.rst 16 Documentation/arch/arm64/booting.rst 的中文翻譯
|
/linux/Documentation/arch/xtensa/ |
H A D | index.rst | 11 booting
|
/linux/arch/powerpc/configs/ |
H A D | security.config | 3 # This is the equivalent of booting with lockdown=integrity
|
/linux/arch/arm64/boot/dts/qcom/ |
H A D | pmi8996.dtsi | 9 * whose the bootloader has to check to continue booting
|
/linux/Documentation/arch/loongarch/ |
H A D | index.rst | 12 booting
|
/linux/arch/arm/mach-qcom/ |
H A D | Kconfig | 14 ARM32 signed firmware that does not allow booting ARM64 kernels.
|