diff options
| author | Jean-Jacques Hiblot <jjhiblot@ti.com> | 2019-10-22 16:39:10 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2020-01-07 11:12:47 -0500 |
| commit | 6b8b98d54d8e74c8b4c6cfe431e88c90efcea72d (patch) | |
| tree | 8af385460d373efdec7d87cbb98bfbcf05c95f73 /Kconfig | |
| parent | e3cd06be93e7e669a93d5786d131f421f346a925 (diff) | |
| download | u-boot-6b8b98d54d8e74c8b4c6cfe431e88c90efcea72d.zip u-boot-6b8b98d54d8e74c8b4c6cfe431e88c90efcea72d.tar.gz u-boot-6b8b98d54d8e74c8b4c6cfe431e88c90efcea72d.tar.bz2 | |
spl: fit: don't load the firmware twice
When u-boot.img is a FIT image generated automatically by mkimage, the
configuration node has the following structure:
conf-1 {
description = "k3-am654-base-board";
firmware = "firmware-1";
loadables = "firmware-1";
fdt = "fdt-1";
};
The firmware is referenced twice. Once by the 'firmware' property and
once by the 'loadables' property. Currently this result in the firmware
being loaded twice. This is not a big problem but has an impact on the
boot time.
Fixing it by not loading a loadable image if it is also the firmware image.
Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
Tested-by: Andreas Dannenberg <dannenberg@ti.com>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions