u-boot.git/doc/uImage.FIT/source_file_format.txt, branch v2020.10

mkimage: fit_image: Add option to make fit header align

2020-04-24T14:10:01+00:00

The image is usually stored in block device like emmc, SD card, make the
offset of image data aligned to block(512 byte) can avoid data copy
during boot process.
eg. SPL boot from FIT image with external data:
- SPL read the first block of FIT image, and then parse the header;
- SPL read image data separately;
- The first image offset is the base_offset which is the header size;
- The second image offset is just after the first image;
- If the offset of imge does not aligned, SPL will do memcpy;
The header size is a ramdon number, which is very possible not aligned, so
add '-B size'to specify the align size in hex for better performance.

example usage:
  ./tools/mkimage -E -f u-boot.its -B 0x200 u-boot.itb

Signed-off-by: Kever Yang 
Reviewed-by: Punit Agrawal 
Reviewed-by: Tom Rini

cosmetic: Fix spelling and whitespace errors

2019-12-03T13:43:23+00:00

Signed-off-by: Thomas Hebb

fit: Support compat string property in configuration node

2019-07-29T13:32:08+00:00

This patch adds support for an optional optimization to compatible
string matching where the compatible string property from the root node
of the kernel FDT can be copied into the configuration node of the FIT
image. This is most useful when using compressed FDTs or when using FDT
overlays, where the traditional extraction of the compatible string from
the kernel FDT itself is not easily possible.

Signed-off-by: Julius Werner 
Reviewed-by: Simon Glass

doc: FIT image: clarify usage of "compression" property

2018-08-10T17:45:33+00:00

Compressed images should have their compression property
set to "none" if U-Boot should leave them compressed.

This is especially the case for compressed ramdisks that
should be uncompressed by the kernel only.

Signed-off-by: Simon Goldschmidt

doc: FIT image: fix incorrect description of DT node unit address

2018-01-16T01:29:21+00:00

The DT spec demands a unit-address in a node name to match the "reg"
property in that node. Newer dtc versions will throw warnings if this is
not the case.
Fix all occurences in the FIT image documentation files where this was not
observed, to not give bad examples to the reader.

Signed-off-by: Andre Przywara

SPL: Add FIT data-position property support

2017-12-13T02:33:38+00:00

For external data, FIT has a optional property "data-position" which
can set the external data to a fixed offset to FIT beginning.
Add the support for this property in SPL FIT.

Signed-off-by: Ye Li 
Signed-off-by: Peng Fan 
Reviewed-by: Simon Glass 
Reviewed-by: Tomas Melin 
Cc: Pantelis Antoniou 
Cc: "Andrew F. Davis" 
Cc: Igor Grinberg 
Cc: "tomas.melin@vaisala.com" 
Cc: Kever Yang 
Cc: Andre Przywara 
Cc: York Sun 
Cc: Lokesh Vutla 
Cc: "Cooper Jr., Franklin" 
Cc: George McCollister 
Cc: Tuomas Tynkkynen 
Cc: Jean-Jacques Hiblot 
Cc: Rick Altherr 
Cc: Tom Rini 
Reviewed-by: Lokesh Vutla 
Reviewed-by: York Sun

fit: fdt overlays doc

2017-09-15T11:27:49+00:00

Signed-off-by: Pantelis Antoniou 
Reviewed-by: Łukasz Majewski
Acked-by: Simon Glass

spl: fit: Support both external and embedded data

2017-09-11T14:55:36+00:00

SPL supports U-Boot image in FIT format which has data outside of
FIT structure. This adds support for embedded data for normal FIT
images.

Signed-off-by: York Sun 
Reviewed-by: Tom Rini 
Reviewed-by: Simon Glass

FIT: List kernel_noload in the list of types

2017-07-26T15:29:15+00:00

In the source_file_format.txt file we talk about how to construct a
valid FIT image.  While it already says to look at the source for the
full list, add kernel_noload to the explicit list of types.  This is
arguably the most important type to use as most often we are including a
kernel that will run from wherever it is loaded into memory and execute.

This for example, allows you to create a single FIT image for Linux that
can be used on both OMAP and i.MX devices as the kernel will not need to
be moved in memory.

Signed-off-by: Tom Rini

image: Add FIT image loadable section custom processing

2016-12-03T18:21:19+00:00

To help automate the loading of custom image types we add the ability
to define custom handlers for the loadable section types. When we find
a compatible type while loading a "loadable" image from a FIT image we
run its associated handlers to perform any additional steps needed for
loading this image.

Signed-off-by: Andrew F. Davis 
Reviewed-by: Simon Glass