u-boot.git/doc/uImage.FIT/source_file_format.txt, branch v2017.09

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

mkimage: fit: spl: Add an optional static offset for external data

2016-06-24T21:23:06+00:00

When building a FIT with external data (-E), U-Boot proper may require
absolute positioning for executing the external firmware. To acheive this
use the (-p) switch, which will replace the amended 'data-offset' with
'data-position' indicating the absolute position of external data.

It is considered an error if the requested absolute position overlaps with the
initial data required for the compact FIT.

Signed-off-by: Teddy Reed

mkimage: Report information about fpga

2016-05-24T09:15:02+00:00

Add FIT_FPGA_PROP that user can identify an optional
entry for fpga.

Signed-off-by: Michal Simek 
Reviewed-by: Simon Glass

doc: fix file extension for flattened image tree blob

2016-04-01T21:17:41+00:00

Different sections in the document suggest flattened image tree blob
files have a file name extension of .itb. Fix the list of file extensions
to reflect that.

Signed-off-by: Andreas Dannenberg

mkimage: Support placing data outside the FIT

2016-03-14T23:18:29+00:00

One limitation of FIT is that all the data is 'inline' within it, using a
'data' property in each image node. This means that to find out what is in
the FIT it is necessary to scan the entire file. Once loaded it can be
scanned and then the images can be copied to the correct place in memory.

In SPL it can take a significant amount of time to copy images around in
memory. Also loading data that does not end up being used is wasteful. It
would be useful if the FIT were small, acting as a directory, with the
actual data stored elsewhere.

This allows SPL to load the entire FIT, without the images, then load the
images it wants later.

Add a -E option to mkimage to request that it output an 'external' FIT.

Signed-off-by: Simon Glass

Use correct spelling of "U-Boot"

2016-02-06T11:00:59+00:00

Correct spelling of "U-Boot" shall be used in all written text
(documentation, comments in source files etc.).

Signed-off-by: Bin Meng 
Reviewed-by: Heiko Schocher 
Reviewed-by: Simon Glass 
Reviewed-by: Minkyu Kang

mkimage will now report information about loadable

2015-05-28T12:18:20+00:00

Added FIT_LOADABLE_PROP, so the user can identify an optional entry
named "loadables" in their .its configuration. "loadables" is a comma
separated list in the .its

Documentation can be found in doc/uImage.FIT/source_file_format.txt and
                              doc/uImage.Fit/multi-with-loadables.its

Signed-off-by: Karl Apsite 
Reviewed-by: Simon Glass

doc: fix misspellings

2015-01-29T18:38:40+00:00

Signed-off-by: Guilherme Maciel Ferreira

doc: "os" is also mandatory for "ramdisk" FIT image components

2015-01-29T18:38:40+00:00

According to fit_image_print(), the "os" property from "image" node is required
also when "type=ramdisk".

Signed-off-by: Guilherme Maciel Ferreira