starfive-tech/u-boot.git/doc/mkimage.1, branch rtthread_AMP

mkimage: Allow updating the FIT timestamp

2020-07-25T20:46:57+00:00

Normally the FIT timestamp is created the first time mkimage is run on a FIT, when converting the source .its to the binary .fit file. This corresponds to using the -f flag. But if the original input to mkimage is a binary file (already compiled) then the timestamp is assumed to have been set previously. Add a -t flag to allow setting the timestamp in this case. Signed-off-by: Simon Glass Reviewed-by: Bin Meng

Revert "Merge tag 'dm-pull-20jul20' of git://git.denx.de/u-boot-dm"

2020-07-24T12:42:06+00:00

This reverts commit 5d3a21df6694ebd66d5c34c9d62a26edc7456fc7, reversing changes made to 56d37f1c564107e27d873181d838571b7d7860e7. Unfortunately this is causing CI failures: https://travis-ci.org/github/trini/u-boot/jobs/711313649 Signed-off-by: Tom Rini

mkimage: Allow updating the FIT timestamp

2020-07-20T17:37:47+00:00

mkimage: Allow including a ramdisk in FIT auto mode

2016-11-06T12:33:42+00:00

Adds -i option that allows specifying a ramdisk file to be added to the FIT image when we are using the automatic FIT mode (no ITS file). This makes adding Depthcharge support to LAVA much more convenient, as no additional configuration files need to be kept around in the machine that dispatches jobs to the boards. Signed-off-by: Tomeu Vizoso Cc: Simon Glass Cc: Matt Hart Cc: Neil Williams Reviewed-by: Simon Glass

doc: typo fix addess -> address

2016-10-07T00:58:17+00:00

Signed-off-by: Jelle van der Waa

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: fix argument parsing on BSD systems

2016-05-02T22:37:09+00:00

The getopt(3) optstring '-' is a GNU extension which is not available on BSD systems like OS X. Remove this dependency by implementing argument parsing in another way. This will also change the lately introduced '-b' switch behaviour. Signed-off-by: Andreas Bießmann Reviewed-by: Simon Glass

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

mkimage: Support adding device tree files to a FIT

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

To make the auto-FIT feature useful we need to be able to provide a list of device tree files on the command line for mkimage to add into the FIT. Add support for this feature. So far there is no support for hashing or verified boot using this method. For those cases, a .its file must still be provided. Signed-off-by: Simon Glass

mkimage: Support automatic creating of a FIT without a .its

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

At present, when generating a FIT, mkimage requires a .its file containing the structure of the FIT and referring to the images to be included. Creating the .its file is a separate step that makes it harder to use FIT. This is not required for creating legacy images. Often the FIT is pretty standard, consisting of an OS image, some device tree files and a single configuration. We can handle this case automatically and avoid needing a .its file at all. To start with, support automatically generate the FIT using a new '-f auto' option. Initially this only supports adding a single image (e.g. a linux kernel) and a single configuration. Signed-off-by: Simon Glass