| /openbmc/u-boot/doc/ |
| H A D | README.multi-dtb-fit | 1 MULTI DTB FIT and SPL_MULTI_DTB_FIT
4 from a FIT appended at the end of the binary.
12 The relevant DTBs are packed into a FIT (list provided by CONFIG__OF_LIST). The
13 FIT is automatically generated at the end of the compilation and appended to
15 the FIT.
27 The relevant DTBs are packed into a FIT. This FIT is automatically generated
29 that SPL can locate it and select the correct DTB from inside the FIT.
33 FIT is uncompressed is dynamicaly allocated but this behaviour can be changed
35 FIT.
37 FIT (same as what the SPL uses to select the DTB for U-Boot).
|
| H A D | README.splashprepare | 24 formatted with a file system or a FIT image. In case of a filesystem, the splash
28 To enable loading the splash image from a FIT image, CONFIG_FIT must be
30 name within the FIT and the FIT should start at the 'offset' field address in
|
| H A D | README.update | 10 boot. The update file should be a FIT file, and can contain one or more
22 one must enable FIT and LIBFDT support:
48 Since the update file is in FIT format, it is created from an *.its file using
51 to be prepared. Refer to the doc/uImage.FIT/ directory for more details on FIT
63 - doc/uImage.FIT/update_uboot.its
91 - doc/uImage.FIT/update3.its
|
| H A D | README.uniphier | 115 You will find details documents in the doc/uImage.FIT directory.
130 2. Describe FIT source
132 You need to write an FIT (Flattened Image Tree) source file to describe the
208 The FIT file name is arbitrary. Let's say you saved it into "fit.its".
210 3. Compile U-Boot with FIT and signature enabled
270 ## Loading kernel from FIT Image at 84100000 ...
287 ## Loading ramdisk from FIT Image at 84100000 ...
303 ## Loading fdt from FIT Image at 84100000 ...
370 [2] FIT
372 - FIT blob
[all …]
|
| H A D | README.bcm7xxx | 13 - support for loading FIT images
17 - support for FIT-provided DTBs instead of relying on the
45 What follows is an example FIT image source file. Build it with:
61 description = "BCM7445 FIT";
|
| H A D | README.fdt-overlays | 63 1. Include and define overlays within a FIT image and have overlays
69 approach. For information on using overlays as part of a FIT image please see:
70 doc/uImage.FIT/overlay-fdt-boot.txt
|
| /openbmc/u-boot/arch/arm/cpu/armv8/fsl-layerscape/doc/ |
| H A D | README.falcon | 4 RAM version U-Boot. Instead, it loads FIT image and boot directly to Linux.
5 CONFIG_SPL_OS_BOOT enables falcon boot. CONFIG_SPL_LOAD_FIT enables the FIT
10 booting U-Boot is not the first choice. The kernel FIT image needs to be put
12 determine if this is a FIT image. If true, FIT image components are parsed and
13 copied or decompressed (if applicable) to their destinations. If FIT image is
24 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS. However, when FIT image is used for
25 Linux, the device tree stored in FIT image overwrites the memory loaded by spl
28 signature header and needs to be loaded before the FIT image. So it is important
29 to understand the device tree in FIT image should be the one actually used, or
30 leave it absent to favor the stored sectors. It is easier to deploy the FIT
[all …]
|
| /openbmc/u-boot/ |
| H A D | Kconfig | 253 config FIT config
259 Flattened Image Tree. FIT is formally a FDT, which can include
263 FIT is very flexible, supporting compression, multiple images,
267 if FIT
280 bool "Support SHA256 checksum of FIT image contents"
284 Enable this to support SHA256 checksum of FIT image contents. A
289 bool "Support SHA384 checksum of FIT image contents"
293 Enable this to support SHA384 checksum of FIT image contents. A
299 bool "Support SHA512 checksum of FIT image contents"
303 Enable this to support SHA512 checksum of FIT image contents. A
[all …]
|
| /openbmc/linux/arch/mips/generic/ |
| H A D | Kconfig | 20 comment "Legacy (non-UHI/non-FIT) Boards"
51 comment "FIT/UHI Boards"
57 from Imagination Technologies in the FIT kernel image. You should
65 from Imagination Technologies in the FIT kernel image.
71 National Instruments in the FIT kernel image.
77 from Imagination Technologies in the FIT kernel image.
84 from Microsemi in the FIT kernel image.
92 from Microsemi in the FIT kernel image.
100 from Microsemi in the FIT kernel image.
108 from Microsemi in the FIT kernel image.
|
| /openbmc/u-boot/lib/rsa/ |
| H A D | Kconfig | 7 RSA support. This enables the RSA algorithm used for FIT image
9 See doc/uImage.FIT/signature.txt for more details.
27 algorithm used in FIT image verification. It required RSA Key as
29 See doc/uImage.FIT/signature.txt for more details.
|
| /openbmc/u-boot/doc/uImage.FIT/ |
| H A D | signature.txt | 1 U-Boot FIT Signature Verification
6 FIT supports hashing of images so that these hashes can be checked on
24 - hash an image in the FIT
26 - store the resulting signature in the FIT
30 - read the FIT
32 - extract the signature from the FIT
33 - hash the image from the FIT
83 The following properties are required in the FIT's signature node(s) to
128 - hashed-strings: The start and size of the string region of the FIT that
155 normally verified by the FIT image booting algorithm. Valid values are
[all …]
|
| H A D | howto.txt | 26 doc/uImage.FIT/source_file_format.txt. The actual data that is to be included in
77 doc/uImage.FIT/kernel.its (note that kernel.its assumes that vmlinux.bin.gz is
87 FIT description: Simple image with single Linux kernel
130 FIT image found
131 FIT description: Simple image with single Linux kernel
153 ## Booting kernel from FIT Image at 00900000 ...
187 be produced using image source file doc/uImage.FIT/kernel_fdt.its like this
197 FIT description: Simple image with single Linux kernel and FDT blob
245 FIT image found
246 FIT description: Simple image with single Linux kernel and FDT blob
[all …]
|
| H A D | x86-fit-boot.txt | 1 Booting Linux on x86 with FIT
166 Create a FIT
169 To create a FIT you will need a source file describing what should go in the
170 FIT. See kernel.its for an example for x86 and also instructions on setting
176 saw above). This means that you will need to load your FIT to a different
189 # Build a FIT image
198 FIT description: Simple image with single Linux kernel on x86
226 Booting the FIT
239 If you want a ramdisk you can add it as normal with FIT. If you want a device
266 Various files in the same directory as this file describe the FIT format.
|
| H A D | source_file_format.txt | 53 FIT - Flattened uImage Tree
55 FIT is formally a flattened device tree (in the libfdt meaning), which
87 To identify FIT sub-nodes representing images, hashes, configurations (which
279 It is also possible for this data to reside outside the FIT itself. This
280 allows the FIT to be quite small, so that it can be loaded and scanned
296 Normal kernel FIT image has data embedded within FIT structure. U-Boot image
303 Please see doc/uImage.FIT/*.its for actual image source files.
|
| /openbmc/u-boot/cmd/ |
| H A D | disk.c | 23 #if CONFIG_IS_ENABLED(FIT) in common_diskboot()
83 #if CONFIG_IS_ENABLED(FIT) in common_diskboot()
109 #if CONFIG_IS_ENABLED(FIT) in common_diskboot()
|
| /openbmc/linux/Documentation/arch/arm/google/ |
| H A D | chromebook-boot-flow.rst | 8 depthcharge_ bootloader. Depthcharge_ expects the OS to be packaged as a `FIT
10 is up to depthcharge_ to pick the right device tree from the `FIT Image`_ and
34 Depthcharge_ will look through all device trees in the `FIT Image`_ trying to
36 through all device trees in the `FIT Image`_ trying to find the one that
69 .. _`FIT Image`: https://doc.coreboot.org/lib/payloads/fit.html
|
| /openbmc/openbmc/meta-evb/meta-evb-arm/meta-evb-fvp-base/recipes-bsp/u-boot/files/ |
| H A D | fvp.cfg | 9 # Enable FIT support
18 # Hash support for FIT image
|
| H A D | fvp.env | 18 …conf}; echo Error loading kernel FIT image with fitconfig ${fitconfig}; bootm ${loadaddr}; echo Er…
|
| /openbmc/u-boot/dts/ |
| H A D | Kconfig | 127 control. These will be packaged into a FIT. At run-time, U-boot
144 bool "Support embedding several DTBs in a FIT image for u-boot"
147 appended FIT image and enable board specific code to then select
154 bool "Support embedding several DTBs in a FIT image for the SPL"
157 DTB at runtime from an appended FIT image containing several DTBs.
170 control in the SPL. These will be packaged into a FIT. At run-time,
186 Compress the FIT image containing the DTBs available for the SPL
194 Compress the FIT image containing the DTBs available for the SPL
200 Do not compress the FIT image containing the DTBs available for the SPL.
230 the FIT image containing the DTBs is uncompressed in an area defined
[all …]
|
| /openbmc/u-boot/board/aspeed/ |
| H A D | ast2600_openbmc_mmc.txt | 7 …conf}; echo Error loading kernel FIT image with fitconfig ${fitconfig}; bootm ${loadaddr}; echo Er…
|
| /openbmc/openbmc/meta-aspeed/recipes-bsp/u-boot/files/ |
| H A D | u-boot-env-ast2600.txt | 7 …conf}; echo Error loading kernel FIT image with fitconfig ${fitconfig}; bootm ${loadaddr}; echo Er…
|
| /openbmc/u-boot/board/theobroma-systems/lion_rk3368/ |
| H A D | fit_spl_atf.its | 5 * Minimal dts for a SPL FIT image payload.
11 description = "FIT image with U-Boot proper, ATF bl31, DTB";
|
| /openbmc/u-boot/board/theobroma-systems/puma_rk3399/ |
| H A D | fit_spl_atf.its | 5 * Minimal dts for a SPL FIT image payload.
11 description = "FIT image with U-Boot proper, ATF bl31, M0 Firmware, DTB";
|
| /openbmc/u-boot/common/ |
| H A D | image-fdt.c | 275 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
293 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
323 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
395 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
|
| /openbmc/qemu/docs/specs/ |
| H A D | acpi_nvdimm.rst | 177 Read FIT
218 | fit data | Varies | 8 | contains FIT data. This field is present |
222 The FIT offset is maintained by the OSPM itself, current offset plus
224 OSPM should read. When all FIT data has been read out, zero fit data
227 If it returns status code 0x100, OSPM should restart to read FIT (read
|