Skip to content
Snippets Groups Projects
Forked from KED Software Projects / Miscellaneous / KED U-Boot Fork
Source project has a limited visibility.
  • Andrew F. Davis's avatar
    44402fe7
    common: image: Remove FIT header update from image post-processing · 44402fe7
    Andrew F. Davis authored
    
    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: default avatarAndrew F. Davis <afd@ti.com>
    Tested-by: default avatarCarlos Hernandez <ceh@ti.com>
    Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
    Reviewed-by: default avatarLokesh Vutla <lokeshvutla@ti.com>
    44402fe7
    History
    common: image: Remove FIT header update from image post-processing
    Andrew F. Davis authored
    
    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: default avatarAndrew F. Davis <afd@ti.com>
    Tested-by: default avatarCarlos Hernandez <ceh@ti.com>
    Reviewed-by: default avatarSimon Glass <sjg@chromium.org>
    Reviewed-by: default avatarLokesh Vutla <lokeshvutla@ti.com>