diff options
author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2021-09-17 14:40:44 +0200 |
---|---|---|
committer | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2021-09-20 11:27:27 +0200 |
commit | 079e293684fea95f5026d2bd7df719879e4dea98 (patch) | |
tree | 0c8e816beda1c8eb75dcf3df57e822cdb9b15ae2 /classes/kernel-itbimage.bbclass | |
parent | 72f59d35816cd2be6159013e4d96d03abf7f1c4b (diff) | |
download | meta-freescale-079e293684fea95f5026d2bd7df719879e4dea98.tar.gz |
imx-boot-container.bbclass: support having more than one UBOOT_CONFIG
The whole purpose of the UBOOT_CONFIG machinery is to allow one to
build multiple versions of U-Boot within the same recipe, e.g. one for
writing to an eMMC boot partition, and one for use with an SD card for
bootstrapping/recovery. But the current code here assumes UBOOT_CONFIG
consists of just a single word (and normally leading whitespace in that
variable would be harmless).
So use the variable ${type} which gets set in turn to each individual
word in UBOOT_CONFIG, which was probably the original intention
anyway. Add a comment about what the u-boot.itb and flash.bin symlinks
will end up pointing at.
When UBOOT_CONFIG does indeed consist of a single word only, this
changes nothing. But this unbreaks the build and makes the different
artifacts available for the UBOOT_CONFIG = "sd emmc ..." case that may
be used by custom boards.
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Diffstat (limited to 'classes/kernel-itbimage.bbclass')
0 files changed, 0 insertions, 0 deletions