On Mon, May 11, 2026 at 03:57:47PM +0200, Casey Connolly wrote:

> Add a qualcomm specific Makefile fragment to make u-boot.mbn a build
> target and introduce a kconfig option to build it by default on relevant
> platforms via CONFIG_BUILD_TARGET.
> 
> Signed-off-by: Casey Connolly <[email protected]>
> ---
>  Kconfig                          |  1 +
>  arch/arm/mach-snapdragon/Kconfig | 11 +++++++++++
>  board/qualcomm/config.mk         | 14 ++++++++++++++
>  3 files changed, 26 insertions(+)
> 
> diff --git a/Kconfig b/Kconfig
> index 8428d039a1c0..183c8096030d 100644
> --- a/Kconfig
> +++ b/Kconfig
> @@ -557,8 +557,9 @@ config BUILD_TARGET
>       default "u-boot-with-spl.sfp" if ARCH_SOCFPGA_GEN5
>       default "u-boot.itb" if !BINMAN && SPL_LOAD_FIT && (ARCH_ROCKCHIP || \
>                               RISCV || ARCH_ZYNQMP)
>       default "u-boot.kwb" if (ARCH_KIRKWOOD || ARMADA_32BIT) && !SPL
> +     default "u-boot.mbn" if ARCH_SNAPDRAGON && QCOM_GENERATE_MBN
>       help
>         Some SoCs need special image types (e.g. U-Boot binary
>         with a special header) as build targets. By defining
>         CONFIG_BUILD_TARGET in the SoC / board header, this
> diff --git a/arch/arm/mach-snapdragon/Kconfig 
> b/arch/arm/mach-snapdragon/Kconfig
> index d3de8693b5a8..6329cbb9215e 100644
> --- a/arch/arm/mach-snapdragon/Kconfig
> +++ b/arch/arm/mach-snapdragon/Kconfig
> @@ -41,5 +41,16 @@ config SYS_CONFIG_NAME
>         This option contains information about board configuration name.
>         Based on this option include/configs/<CONFIG_SYS_CONFIG_NAME>.h header
>         will be used for board configuration.
>  
> +config QCOM_GENERATE_MBN
> +     bool "Generate an MBN-compatible ELF binary"
> +     default n

The default is always "n" so we only need default n if ... statements
when we would otherwise default y. There's other examples to clean up,
so only fix this if there's a v8. Thanks.

-- 
Tom

Attachment: signature.asc
Description: PGP signature

Reply via email to