On 6/4/25 11:21, Stephan Gerhold wrote:
On Mon, Jun 02, 2025 at 06:10:57PM +0200, Casey Connolly wrote:
Remove qcs9100_defconfig since it is now identical to qcom_defconfig.
Additionally remove the load address and REMAKE_ELF from other Qualcomm
defconfigs.
For these platforms you should explicitly build the u-boot.mbn target
which will have the correct load address and Qualcomm MBN signatures.
What is the motivation to require explicitly building the u-boot.mbn
target? Couldn't we do that automatically like before with REMAKE_ELF
(i.e. add u-boot.mbn to INPUTS-y)? Or is this because of the additional
Python dependencies (the cryptography module)?
Oops, the wording here needs updating. This was how it worked in v1, but
v2 uses binman and spits out the u-boot.mbn automagically when building
with qcom_defconfig for a target that mkmbn.py recognises.
BTW: We should probably document the Python "cryptography" requirement
somewhere so people don't get confused? qtestsign is Python 3.7+ and
cryptography 3.1+.
Thanks,
Stephan
--
Casey (she/they)
