[Buildroot] [PATCH v3 1/4] boot/arm-trusted-firmware: support alternate image files

Etienne Carriere etienne.carriere at linaro.org
Tue Oct 29 08:19:58 UTC 2019


Hello Thomans and all,

On Sun, 27 Oct 2019 at 15:59, Arnout Vandecappelle <arnout at mind.be> wrote:
>
>
>
> On 22/03/2019 10:58, Etienne Carriere wrote:
> > Some platform may generate specific boot image files instead of
> > the generic files *.bin  when building TF-A package.
>
>  This is still very vague, and it doesn't have any in-tree user. Therefore,
> we're not prepared to merge this patch. Do you have a concrete example,
> preferably with a defconfig that actually makes use of it?

Well, I will consider when there is an in-tree board that needs this :)

Actually, this is some kind of equivalent for optee-os
BR2_TARGET_OPTEE_OS_IMAGE_NAMES
or even u-boot BR2_TARGET_UBOOT_FORMAT_CUSTOM.

Regards,
Etienne

>  I've therefore marked this patch as Changes Requested.
>
>  Regards,
>  Arnout
>
> > This change
> > introduces new configuration directive for the arm-trusted-firmware
> > boot package.
> >
> > BR2_TARGET_ARM_TRUSTED_FIRMWARE_CUSTOM_IMAGE_NAMES is boolean.
> > When disabled, install boot image files are .../*.bin.
> > When enabled, BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL_IMAGE_NAMES shall
> > lists the names of the generated boot image files.
> >
> > Signed-off-by: Etienne Carriere <etienne.carriere at linaro.org>
> [snip]



More information about the buildroot mailing list