[U-Boot] [PATCH PATCH v3 12/12] spl: fit: Allow the board to tell if more images must be loaded from FIT
sjg at chromium.org
Sat Jun 22 19:09:41 UTC 2019
On Thu, 23 May 2019 at 11:39, Jean-Jacques Hiblot <jjhiblot at ti.com> wrote:
> spl_fit_get_image_name() is used to get the names of the images that the
> SPL must load from the FIT. It relies on the content of a property present
> in the FIT. The list of images is thus statically defined in the FIT.
> With this scheme, it becomes quickly hard to manage combinations of more
> than a hand few of images.
> To address this problem, give the board-level code the opportunity to
> add to the list of images. The images from the FIT property are loaded
> first, and then the board_fit_get_additionnal_images() is called to
> get more image names.
> Signed-off-by: Jean-Jacques Hiblot <jjhiblot at ti.com>
> Changes in v3:
> - removed the RFC prefix. This work will be needed soon by TI's AM65x
> platform. and can probably benefit other modular platforms
> - removed the last patch that provided an example of how to use this with
> on a DRA76.
> - removed the patch that made u-boot.img a symlink to u-boot.itb because
> it breaks the build of many platforms (because files required to build the
> ITB are missing)
> - removed the patch to reduce the footprint of the am335x SPL. (already
> - Made the boot flow more permissive (don't fail immediately if an overlay
> is not present) and more verbose when an error occures
> - handle the dependencies of the FIT generation in a more generic way
> - use a dedicated kconfig option to enable the application of the overlays
> by the SPL.
> Changes in v2:
> - reworked board_fit_get_additionnal_images() and how it used in spl_fit.c
> - removed dtbo generation from dtso files and use .dts extension for the
> - add dynamic allocation usage in a separate patch
> - defconfig change for the am335x_evm
> common/spl/spl_fit.c | 28 +++++++++++++++++++++++++---
> include/spl.h | 16 ++++++++++++++++
> 2 files changed, 41 insertions(+), 3 deletions(-)
Can we instead use driver mode for this? E.g. there is a board uclass
which could have functionality added.
More information about the U-Boot