Re: [PATCH v2 0/7] Qualcomm: teach the build system to emit signed ELF images

[Stephan Gerhold <stephan.gerhold@linaro.org>]

On Mon, Jun 02, 2025 at 06:10:51PM +0200, Casey Connolly wrote:
> With several new Qualcomm platforms appearing on the mailing list, all
> of which build U-Boot as an ELF, sign it, and then flash it to some
> partition on the board, we're getting a lot of defconfigs which just
> contain a debug UART and a TEXT_BASE address. This leads to needless
> rebuilds in CI of effectively the same image, and needless duplication
> of build instructions.
> 
> To address this, let's introduce a new tool "mkmbn.py", this is based
> on the existing qtestsign[1] tool but is (currently) hardcoded to
> only handle the Dragonwing and IPQ boards which use MBN header v6.

It doesn't feel right to limit the use of this tool to v6 boards, given
that qtestsign supports v3 boards such as the DragonBoard 410c as well,
which is also using the CONFIG_REMAKE_ELF functionality right now.

Which changes are needed to make this work for DB410c as well? Looking
more at the diff in v2, I think the hardcoding of v6 is actually already
gone(?), since there are entries for qcom,apq8016/qcom,msm8916 now. What
else is needed to use this for DB410c?

I'm happy to test on DB410c if needed, just ping me in the chat.

Thanks,
Stephan