Searched full:bootloaders (Results 1 – 19 of 19) sorted by relevance
6 Device-tree compatible SH bootloaders are expected to provide the physical7 address of the device tree blob in r4. Since legacy bootloaders did not9 inter-operate with old bootloaders must either use a builtin DTB or
6 Some bootloaders only support a single entry point, at the start of the7 kernel image. Other bootloaders will jump to the ELF start address.23 Legacy bootloaders do not use this convention, and they do not pass in a
16 easier for systems with primitive bootloaders that did not allow for
20 broken) ROM bootloaders are unable to read second stage from the emmc
17 CFE and U-Boot bootloaders.
42 1EF/001 ALL sentinel Used to detect broken bootloaders
867 by the bootloaders.981 .long 0x01234567 /* Some fixed size data for the bootloaders. */983 example_struct: /* Some variable size data for the bootloaders. */989 example_strings: /* Some variable size data for the bootloaders. */1022 used by the bootloaders to detect supported fixed size fields in the kernel_info
10 This document describes what the RISC-V kernel expects from bootloaders and19 The RISC-V kernel expects the following of bootloaders and platform firmware:
36 lightweight bootloaders like Gummiboot or rEFInd.
164 [5] *fastboot "a mechanism for communicating with bootloaders"*
104 expected impact on existing users, such as bootloaders or other operating
27 A couple of bootloaders able to boot Linux on Assabet are available:
109 trusted HW platform with all of the firmware and bootloaders included on
207 The second option also has problems: Linux supports a variety of bootloaders
66 bootloaders that do not implement this requirement, the uncompressed
62 kexec, and other bootloaders were modified to support both passing a
1086 The MSM chipset and hardware revision used Qualcomm bootloaders. It
260 * visible on the relevant pins ... bootloaders on
3429 Some bootloaders may need an escape character before '$',