Home
last modified time | relevance | path

Searched refs:FIT (Results 1 – 25 of 149) sorted by relevance

123456

/OK3568_Linux_fs/u-boot/
H A DKconfig178 config FIT config
182 Flattened Image Tree. FIT is formally a FDT, which can include
186 FIT is very flexible, supporting compression, multiple images,
190 if FIT
193 bool "Support SHA256 checksum of FIT image contents"
197 Enable this to support SHA256 checksum of FIT image contents. A
207 bool "Support RSA4096 verification of FIT image contents"
211 Enable this to support RSA4096 checksum of FIT image contents. A
219 bool "Enable signature verification of FIT uImages"
224 This option enables signature verification of FIT uImages,
[all …]
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.multi-dtb-fit1 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 DREADME.update10 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 DREADME.splashprepare24 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 DREADME.bcm7xxx13 - 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 DREADME.fdt-overlays63 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
H A DREADME.dfutftp96 FIT image format for download
99 To create FIT image for download one should follow the update tftp README file
102 The original snippet of ./doc/uImage.FIT/update_uboot.its
/OK3568_Linux_fs/buildroot/package/uboot-tools/
H A DConfig.in11 bool "Flattened Image Tree (FIT) support"
16 Enables support for Flattened Image Tree (FIT).
19 Flattened Image Tree. FIT is formally a FDT, which can include
24 comment "u-boot tools FIT support needs a toolchain w/ dynamic library"
30 bool "FIT signature verification support"
33 Enables support for FIT Signature Verification.
35 Flat Image Trees (FIT) supports hashing of images so that
57 allows FIT image signature validation on target system.
H A DConfig.in.host11 bool "Flattened Image Tree (FIT) support"
14 Enables support for Flattened Image Tree (FIT).
17 Flattened Image Tree. FIT is formally a FDT, which can include
25 bool "FIT signature verification support"
27 Enables support for FIT Signature Verification.
29 Flat Image Trees (FIT) supports hashing of images so that
/OK3568_Linux_fs/kernel/arch/mips/generic/
H A DKconfig20 comment "Legacy (non-UHI/non-FIT) Boards"
46 comment "FIT/UHI Boards"
52 from Imagination Technologies in the FIT kernel image. You should
60 National Instruments in the FIT kernel image.
66 from Imagination Technologies in the FIT kernel image.
73 from Microsemi in the FIT kernel image.
/OK3568_Linux_fs/u-boot/doc/uImage.FIT/
H A Dsignature.txt1 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
125 - hashed-strings: The start and size of the string region of the FIT that
152 normally verified by the FIT image booting algorithm. Valid values are
[all …]
H A Dhowto.txt26 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 Dx86-fit-boot.txt1 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 Dsource_file_format.txt53 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
277 It is also possible for this data to reside outside the FIT itself. This
278 allows the FIT to be quite small, so that it can be loaded and scanned
294 Normal kernel FIT image has data embedded within FIT structure. U-Boot image
301 Please see doc/uImage.FIT/*.its for actual image source files.
H A Doverlay-fdt-boot.txt1 U-Boot FDT Overlay FIT usage
6 In many cases it is desirable to have a single FIT image support a multitude
11 This document focuses on specifically using overlays as part of a FIT image.
208 hand in the FIT image. For the add-on boards the extra config selection method
H A Dbeaglebone_vboot.txt28 tree with the kernel binary. U-Boot supports the latter with its flexible FIT
195 Linux kernel into a FIT (Flat Image Tree, a flexible file format that U-Boot
212 FIT description: Beaglebone black
253 ## Loading kernel from FIT Image at 7fc6ee469000 ...
276 ## Loading fdt from FIT Image at 7fc6ee469000 ...
293 ## Loading ramdisk from FIT Image at 7fc6ee469000 ...
326 ## Loading kernel from FIT Image at 7f5a39571000 ...
349 ## Loading fdt from FIT Image at 7f5a39571000 ...
366 ## Loading ramdisk from FIT Image at 7f5a39571000 ...
523 ## Loading kernel from FIT Image at 82000000 ...
[all …]
H A Dverified-boot.txt88 Flattened Image Tree (FIT)
90 The FIT format is already widely used in U-Boot. It is a flattened device
96 a standard place. Then when a FIT is loaded it can be verified using that
/OK3568_Linux_fs/u-boot/lib/rsa/
H A DKconfig6 RSA support. This enables the RSA algorithm used for FIT image
8 See doc/uImage.FIT/signature.txt for more details.
26 algorithm used in FIT image verification. It required RSA Key as
28 See doc/uImage.FIT/signature.txt for more details.
/OK3568_Linux_fs/u-boot/cmd/
H A Ddisk.c24 #if CONFIG_IS_ENABLED(FIT) in common_diskboot()
84 #if CONFIG_IS_ENABLED(FIT) in common_diskboot()
110 #if CONFIG_IS_ENABLED(FIT) in common_diskboot()
/OK3568_Linux_fs/u-boot/dts/
H A DKconfig137 control. These will be packaged into a FIT. At run-time, U-boot
154 bool "Support embedding several DTBs in a FIT image for u-boot"
157 appended FIT image and enable board specific code to then select
164 bool "Support embedding several DTBs in a FIT image for the SPL"
167 DTB at runtime from an appended FIT image containing several DTBs.
180 control in the SPL. These will be packaged into a FIT. At run-time,
196 Compress the FIT image containing the DTBs available for the SPL
204 Compress the FIT image containing the DTBs available for the SPL
210 Do not compress the FIT image containing the DTBs available for the SPL.
240 the FIT image containing the DTBs is uncompressed in an area defined
[all …]
/OK3568_Linux_fs/u-boot/board/theobroma-systems/lion_rk3368/
H A Dfit_spl_atf.its4 * Minimal dts for a SPL FIT image payload.
12 description = "FIT image with U-Boot proper, ATF bl31, DTB";
H A DREADME24 Build the full U-Boot and a FIT image including the ATF
32 Copy the SPL to offset 32k and the FIT image containing the payloads
/OK3568_Linux_fs/u-boot/board/theobroma-systems/puma_rk3399/
H A Dfit_spl_atf.its4 * Minimal dts for a SPL FIT image payload.
12 description = "FIT image with U-Boot proper, ATF bl31, M0 Firmware, DTB";
/OK3568_Linux_fs/u-boot/common/
H A Dimage-fdt.c368 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
383 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
413 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
485 #if CONFIG_IS_ENABLED(FIT) in boot_get_fdt()
/OK3568_Linux_fs/device/rockchip/common/configs/
H A DConfig.in.security15 select RK_USE_FIT_IMG # Security feature depends on FIT image
35 string "its script for FIT security ramboot image"

123456