Home
last modified time | relevance | path

Searched full:bootloaders (Results 1 – 10 of 10) sorted by relevance

/Documentation/devicetree/bindings/mmc/
Dmmc-pwrseq-emmc.txt10 broken) ROM bootloaders are unable to read second stage from the emmc
/Documentation/x86/
Dzero-page.rst40 1EF/001 ALL sentinel Used to detect broken bootloaders
/Documentation/devicetree/bindings/arm/
Dqcom.yaml13 Some qcom based bootloaders identify the dtb blob based on a set of
/Documentation/arm/
Duefi.rst36 lightweight bootloaders like Gummiboot or rEFInd.
/Documentation/devicetree/
Dbooting-without-of.txt296 Some bootloaders only support a single entry point, at the start of the
297 kernel image. Other bootloaders will jump to the ELF start address.
313 Legacy bootloaders do not use this convention, and they do not pass in a
323 Device-tree-compatible SH bootloaders are expected to provide the physical
324 address of the device tree blob in r4. Since legacy bootloaders did not
326 inter-operate with old bootloaders must either use a builtin DTB or
448 particularly useful for bootloaders which need to make
Dusage-model.txt58 kexec, and other bootloaders were modified to support both passing a
/Documentation/arm/sa1100/
Dassabet.rst27 A couple of bootloaders able to boot Linux on Assabet are available:
/Documentation/arm64/
Dbooting.rst66 bootloaders that do not implement this requirement, the uncompressed
/Documentation/spi/
Dspi-summary.rst263 * visible on the relevant pins ... bootloaders on
/Documentation/admin-guide/
Dkernel-parameters.txt2537 Some bootloaders may need an escape character before '$',