On 13 September 2017 at 13:29, Philipp Tomsich <philipp.toms...@theobroma-systems.com> wrote: > During the loading of more complex FIT images (e.g. when the invoked > next stage needs to find additional firmware for a power-management > core... or if there are multiple images for different privilege levels > started in parallel), it is helpful to create a record of what images > are loaded where: if a FDT is loaded for one of the next stages, it > can be used to convey the status and location of loadables. > > This adds a fdt_record_loadable() function that can be invoked to > record the status of each loadable below the /fit-images path. > > Signed-off-by: Philipp Tomsich <philipp.toms...@theobroma-systems.com> > --- > > common/fdt_support.c | 39 +++++++++++++++++++++++++++++++++++++++ > include/fdt_support.h | 20 ++++++++++++++++++++ > 2 files changed, 59 insertions(+)
Reviewed-by: Simon Glass <s...@chromium.org> _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
