summaryrefslogtreecommitdiff
path: root/tools/imagetool.h
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2016-02-22 22:55:51 -0700
committerTom Rini <trini@konsulko.com>2016-03-14 19:18:28 -0400
commit8e35bb07eb68e524804f2ef53dd18c7cec0b06fc (patch)
tree6e4b4062aad571ec3b94243d06723bfc09fe74b6 /tools/imagetool.h
parentcef2e51489567260857984c3e95d98eb03c97fe9 (diff)
downloadu-boot-8e35bb07eb68e524804f2ef53dd18c7cec0b06fc.tar.gz
u-boot-8e35bb07eb68e524804f2ef53dd18c7cec0b06fc.tar.bz2
u-boot-8e35bb07eb68e524804f2ef53dd18c7cec0b06fc.zip
mkimage: Support automatic creating of a FIT without a .its
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 <sjg@chromium.org>
Diffstat (limited to 'tools/imagetool.h')
-rw-r--r--tools/imagetool.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/tools/imagetool.h b/tools/imagetool.h
index 3cf42ac96a..4f426e40a0 100644
--- a/tools/imagetool.h
+++ b/tools/imagetool.h
@@ -61,6 +61,7 @@ struct image_tool_params {
int require_keys; /* 1 to mark signing keys as 'required' */
int file_size; /* Total size of output file */
int orig_file_size; /* Original size for file before padding */
+ bool auto_its; /* Automatically create the .its file */
int fit_image_type; /* Image type to put into the FIT */
};