diff options
authorDaniel Allred <>2016-06-27 09:19:21 -0500
committerKlaus Goger <>2016-09-18 20:22:05 +0200
commitef86fa9a11fc1f92cd682deb46e127c8f274eb73 (patch)
parent46ec59c67ab24a248c7df44c666a81fb286d41d8 (diff)
spl: fit: add support for post-processing of images
The next stage boot loader image and the selected FDT can be post- processed by board/platform/device-specific code, which can include modifying the size and altering the starting source address before copying these binary blobs to their final destination. This might be desired to do things like strip headers or footers attached to the images before they were packaged into the FIT, or to perform operations such as decryption or authentication. Introduce new configuration option CONFIG_SPL_FIT_IMAGE_POST_PROCESS to allow controlling this feature. If enabled, a platform-specific post-process function must be provided. Signed-off-by: Daniel Allred <> Signed-off-by: Andreas Dannenberg <> Reviewed-by: Tom Rini <> Reviewed-by: Simon Glass <>
3 files changed, 56 insertions, 5 deletions
diff --git a/Kconfig b/Kconfig
index e7002edcb9..d5ab9e3a2c 100644
--- a/Kconfig
+++ b/Kconfig
@@ -284,6 +284,29 @@ config SPL_LOAD_FIT
particular it can handle selecting from multiple device tree
and passing the correct one to U-Boot.
+ bool "Enable post-processing of FIT artifacts after loading by the SPL"
+ help
+ Allows doing any sort of manipulation to blobs after they got extracted
+ from the U-Boot FIT image like stripping off headers or modifying the
+ size of the blob, verification, authentication, decryption etc. in a
+ platform or board specific way. In order to use this feature a platform
+ or board-specific implementation of board_fit_image_post_process() must
+ be provided. Also, anything done during this post-processing step would
+ need to be comprehended in how the images were prepared before being
+ injected into the FIT creation (i.e. the blobs would have been pre-
+ processed before being added to the FIT image).
+ bool "Force SPL to on load images with FIT header"
+ depends on SPL_LOAD_FIT
+ help
+ Normally SPL falls back to assuming that loaded images are raw
+ U-Boot binaries, when no FIT header is present. This will cause
+ a crash when probing boot devices and touching one that does not
+ contain a valid image.
depends on ARC || ARCH_SUNXI
int "CPU clock frequency"
diff --git a/common/spl/spl_fit.c b/common/spl/spl_fit.c
index 987470896c..069e94d529 100644
--- a/common/spl/spl_fit.c
+++ b/common/spl/spl_fit.c
@@ -132,7 +132,7 @@ int spl_load_simple_fit(struct spl_load_info *info, ulong sector, void *fit)
int data_offset, data_size;
int base_offset, align_len = ARCH_DMA_MINALIGN - 1;
int src_sector;
- void *dst;
+ void *dst, *src;
* Figure out where the external images start. This is the base for the
@@ -206,8 +206,13 @@ int spl_load_simple_fit(struct spl_load_info *info, ulong sector, void *fit)
return -EIO;
debug("image: dst=%p, data_offset=%x, size=%x\n", dst, data_offset,
- memcpy(dst, dst + get_aligned_image_overhead(info, data_offset),
- data_size);
+ src = dst + get_aligned_image_overhead(info, data_offset);
+ board_fit_image_post_process((void **)&src, (size_t *)&data_size);
+ memcpy(dst, src, data_size);
/* Figure out which device tree the board wants to use */
fdt_len = spl_fit_select_fdt(fit, images, &fdt_offset);
@@ -236,8 +241,14 @@ int spl_load_simple_fit(struct spl_load_info *info, ulong sector, void *fit)
debug("fdt: dst=%p, data_offset=%x, size=%x\n", dst, fdt_offset,
- memcpy(load_ptr + data_size,
- dst + get_aligned_image_overhead(info, fdt_offset), fdt_len);
+ src = dst + get_aligned_image_overhead(info, fdt_offset);
+ dst = load_ptr + data_size;
+ board_fit_image_post_process((void **)&src, (size_t *)&fdt_len);
+ memcpy(dst, src, fdt_len);
return 0;
diff --git a/include/image.h b/include/image.h
index f9ee5649c5..e9f2c80d6b 100644
--- a/include/image.h
+++ b/include/image.h
@@ -1167,4 +1167,21 @@ ulong android_image_get_kload(const struct andr_img_hdr *hdr);
int board_fit_config_name_match(const char *name);
+ * board_fit_image_post_process() - Do any post-process on FIT binary data
+ *
+ * This is used to do any sort of image manipulation, verification, decryption
+ * etc. in a platform or board specific way. Obviously, anything done here would
+ * need to be comprehended in how the images were prepared before being injected
+ * into the FIT creation (i.e. the binary blobs would have been pre-processed
+ * before being added to the FIT image).
+ *
+ * @image: pointer to the image start pointer
+ * @size: pointer to the image size
+ * @return no return value (failure should be handled internally)
+ */
+void board_fit_image_post_process(void **p_image, size_t *p_size);
#endif /* __IMAGE_H__ */