diff options
author | Andrew F. Davis <afd@ti.com> | 2016-11-21 14:37:09 -0600 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2016-12-04 13:55:03 -0500 |
commit | 44402fe709f5a116083934e07d97b4c77ba52ec1 (patch) | |
tree | d93c8c0185d32b3c140b3a82a700e799548c77a6 /arch/arm/mach-stm32 | |
parent | a7747affae98636f5dd18401538513056771343e (diff) | |
download | u-boot-imx-44402fe709f5a116083934e07d97b4c77ba52ec1.zip u-boot-imx-44402fe709f5a116083934e07d97b4c77ba52ec1.tar.gz u-boot-imx-44402fe709f5a116083934e07d97b4c77ba52ec1.tar.bz2 |
common: image: Remove FIT header update from image post-processing
After an image is selected out of a FIT blob for further processing we
run an optional, platform specific, post-processing function on this
component. This post-processing may modify the position and size of the
image, so after post-processing we update the location and size for this
image in the FIT header. This can cause problems as the position of
subsequent components in the FIT blob are only referenced by relative
position to the end of the last component. When we resize or move a
component the following components position will be calculated
incorrectly. To fix this, we do not update the FIT header but instead
only update our local understanding of the image data. This also allows
us to re-run post-processing steps if needed.
Signed-off-by: Andrew F. Davis <afd@ti.com>
Tested-by: Carlos Hernandez <ceh@ti.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Diffstat (limited to 'arch/arm/mach-stm32')
0 files changed, 0 insertions, 0 deletions