Home
last modified time | relevance | path

Searched refs:FDT (Results 1 – 25 of 48) sorted by relevance

12

/external/u-boot/doc/uImage.FIT/
Dcommand_syntax_extensions.txt21 i.e., without passing the Flattened Device Tree (FDT), and new way, where the
22 kernel is passed a pointer to the FDT. The boot method is indicated for each
52 - boot method: non-FDT
63 #ifdef CONFIG_OF_* | non-FDT | FDT |
64 #ifndef CONFIG_OF_* | non-FDT | non-FDT |
72 - boot method: non-FDT
75 ramdisk image, and <addr3> is the address of a FDT binary blob. Kernel is
77 - boot method: FDT
80 a FDT binary blob. Kernel is booted without initrd.
81 - boot method: FDT
[all …]
Dkernel_fdt.its2 * Simple U-Boot uImage source file containing a single kernel and FDT blob
8 description = "Simple image with single Linux kernel and FDT blob";
46 description = "Boot Linux kernel with FDT blob";
Dsource_file_format.txt15 replace direct passing of 'struct bd_info' which was used to boot pre-FDT
19 compatibility for platforms which are not FDT ready. Number of elements
20 playing role in the booting process has increased and now includes the FDT
21 blob. Kernel image, FDT blob and possibly ramdisk image - all must be placed
23 missing: FDT is not present for legacy platforms, ramdisk is always optional.
44 This document defines new uImage structure by providing FDT bindings for new
50 To avoid confusion with the kernel FDT the following naming convention is
265 The FDT blob is required to properly boot FDT based kernel, so the minimal
266 configuration for 2.6 FDT kernel is (kernel, fdt) pair.
268 Older, 2.4 kernel and 2.6 non-FDT kernel do not use FDT blob, in such cases
[all …]
Dhowto.txt69 Example 1 -- old-style (non-FDT) kernel booting
73 development host is to be booted old-style (non-FDT) by U-Boot on an embedded
181 Example 2 -- new-style (FDT) kernel booting
185 new-style, i.e., with a FDT blob. In this case there are two prerequisite data
186 files: vmlinux.bin.gz (Linux kernel) and target.dtb (FDT blob). The uImage can
197 FIT description: Simple image with single Linux kernel and FDT blob
224 Description: Boot Linux kernel with FDT blob
226 FDT: fdt-1
246 FIT description: Simple image with single Linux kernel and FDT blob
275 Description: Boot Linux kernel with FDT blob
[all …]
Dupdate3.its8 description = "Automatic software updates: kernel, ramdisk, FDT";
34 description = "FDT blob";
Dmulti.its2 * U-Boot uImage source file with multiple kernels, ramdisks and FDT blobs
8 description = "Various kernels, ramdisks and FDT blobs";
Dsign-images.its4 description = "Chrome OS kernel image with one or more FDT blobs";
Dsign-configs.its4 description = "Chrome OS kernel image with one or more FDT blobs";
Dmulti-with-fpga.its2 * U-Boot uImage source file with multiple kernels, ramdisks and FDT blobs
Dmulti-with-loadables.its2 * U-Boot uImage source file with multiple kernels, ramdisks and FDT blobs
Dverified-boot.txt91 tree (FDT) in a particular format, with images contained within. FITs
/external/u-boot/doc/
DREADME.commands.spl10 fdt: exports the FDT
25 call with FDT:
29 spl export fdt 0x82000000 - 0x80000100 /* export FDT */
DREADME.falcon116 or prepared FDT) from temporary storage in RAM into persistant storage
119 highly on your system setup and your provided data (ATAGS or FDT).
121 RAM address of temporary storage. The RAM address of FDT will also be
123 prepared FDT will be set in the environment variable 'fdtargslen'.
125 FDT to persistent storage.
133 The "spl export" command is prepared to work with ATAGS and FDT. However,
134 using FDT is at the moment untested. The ppc port (see a3m071 example
199 Example with FDT: a3m071 board
DREADME.zynq68 - Added basic FDT support for zynq boards
73 - Add FDT support on individual drivers
DREADME.arm6425 3. Earlier Linux kernel versions required the FDT to be placed at a
DREADME.fdt-overlays1 U-Boot FDT Overlay usage
DREADME.update94 ramdisk and FDT blob stored in Flash. The procedure for preparing the update
/external/u-boot/board/warp7/
DKconfig18 hex "FDT load address"
21 The address the FDT file should be loaded to.
/external/u-boot/lib/
DKconfig308 bool "Enable the FDT library"
311 This enables the FDT library (libfdt). It provides functions for
318 bool "Enable the FDT library overlay support"
322 This enables the FDT library (libfdt) overlay support.
325 bool "Enable the FDT library for SPL"
328 This enables the FDT library (libfdt). It provides functions for
/external/u-boot/test/py/tests/vboot/
Dsign-images-sha1.its4 description = "Chrome OS kernel image with one or more FDT blobs";
Dsign-configs-sha256.its4 description = "Chrome OS kernel image with one or more FDT blobs";
Dsign-images-sha256.its4 description = "Chrome OS kernel image with one or more FDT blobs";
Dsign-configs-sha1.its4 description = "Chrome OS kernel image with one or more FDT blobs";
/external/u-boot/doc/driver-model/
Dremoteproc-framework.txt119 TO DM/FDT.
/external/u-boot/
DKconfig228 Flattened Image Tree. FIT is formally a FDT, which can include
229 images of various types (kernel, FDT blob, ramdisk, etc.)
453 Enable FDT memory map syncup before OS boot. This feature can be

12