On Sat, Jun 25, 2016 at 08:54:19PM -0600, Simon Glass wrote: > Hi Andreas, > > On 24 June 2016 at 09:57, Andreas Dannenberg <[email protected]> wrote: > > From: Daniel Allred <[email protected]> > > > > 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 <[email protected]> > > Signed-off-by: Andreas Dannenberg <[email protected]> > > Reviewed-by: Tom Rini <[email protected]> > > --- > > Kconfig | 4 ++++ > > common/spl/spl_fit.c | 21 ++++++++++++++++----- > > include/image.h | 17 +++++++++++++++++ > > 3 files changed, 37 insertions(+), 5 deletions(-) > > Reviewed-by: Simon Glass <[email protected]> > > Nit below > > > > > diff --git a/Kconfig b/Kconfig > > index 3ceff25..b0a5595 100644 > > --- a/Kconfig > > +++ b/Kconfig > > @@ -313,6 +313,10 @@ config SPL_LOAD_FIT > > particular it can handle selecting from multiple device tree > > and passing the correct one to U-Boot. > > > > +config SPL_FIT_IMAGE_POST_PROCESS > > + bool "Enable post-processing of FIT artifacts after loading by the > > SPL" > > Please can you mention the function that is called in this case and > what that function is able to do?
Hi Simon, good suggestion. Will update and re-submit. Thanks, -- Andreas Dannenberg Texas Instruments Inc _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot

