diff options
| author | Simon Glass <sjg@chromium.org> | 2020-07-09 18:39:43 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-07-20 11:37:47 -0600 |
| commit | 4c63d21754a2583df1d85d3af6f0a5bf5c300d20 (patch) | |
| tree | b68e81534295133503f11ee2e1e1ceaae50d227c /doc/README.commands.itest | |
| parent | 8200d8871a6a87834e26e38ca5cd475f86733dfd (diff) | |
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/README.commands.itest')
0 files changed, 0 insertions, 0 deletions