Searched full:booting (Results 1 – 25 of 133) sorted by relevance
123456
| /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.
|
| /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
|
| /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
|
| /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.
|
| /Documentation/arch/xtensa/ |
| D | index.rst | 11 booting
|
| /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
|
| /Documentation/arch/loongarch/ |
| D | index.rst | 12 booting
|
| /Documentation/arch/mips/ |
| D | index.rst | 11 booting
|
| /Documentation/arch/sh/ |
| D | booting.rst | 3 DeviceTree Booting
|
| /Documentation/arch/arm64/ |
| D | index.rst | 14 booting
|
| /Documentation/arch/powerpc/ |
| D | index.rst | 11 booting
|
| /Documentation/translations/zh_CN/arch/loongarch/ |
| D | index.rst | 17 booting
|
| /Documentation/translations/zh_TW/arch/loongarch/ |
| D | index.rst | 17 booting
|
| /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
|
| /Documentation/translations/zh_TW/arch/mips/ |
| D | booting.rst | 5 :Original: Documentation/arch/mips/booting.rst
|
| D | index.rst | 19 booting
|
| /Documentation/arch/x86/ |
| D | index.rst | 12 booting-dt
|
| D | booting-dt.rst | 3 DeviceTree Booting
|
| /Documentation/translations/zh_CN/arch/mips/ |
| D | booting.rst | 5 :Original: Documentation/arch/mips/booting.rst
|
| D | index.rst | 19 booting
|
| /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
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | serial.txt | 11 property as described in booting-without-of.txt, section IX.1 in the following
|
| /Documentation/admin-guide/ |
| D | edid.rst | 13 booting or it displays the wrong area. Cases when this happens are:
|
123456