summaryrefslogtreecommitdiff
path: root/doc/mkimage.1
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2020-07-10 03:39:43 +0300
committerSimon Glass <sjg@chromium.org>2020-07-20 20:37:47 +0300
commit4c63d21754a2583df1d85d3af6f0a5bf5c300d20 (patch)
treeb68e81534295133503f11ee2e1e1ceaae50d227c /doc/mkimage.1
parent8200d8871a6a87834e26e38ca5cd475f86733dfd (diff)
downloadu-boot-4c63d21754a2583df1d85d3af6f0a5bf5c300d20.tar.xz
mkimage: Allow updating the FIT timestamp
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 <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'doc/mkimage.1')
-rw-r--r--doc/mkimage.19
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/mkimage.1 b/doc/mkimage.1
index 3dcdcedcef..fea5288784 100644
--- a/doc/mkimage.1
+++ b/doc/mkimage.1
@@ -167,6 +167,15 @@ Specifies that keys used to sign the FIT are required. This means that they
must be verified for the image to boot. Without this option, the verification
will be optional (useful for testing but not for release).
+.TP
+.BI "\-t
+Update the timestamp in the FIT.
+
+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.
+
.SH EXAMPLES
List image information: