From: Casey Connolly Date: Mon, 16 Jun 2025 16:25:31 +0000 (+0200) Subject: doc: board/qualcomm: remove signing references from dragonwing.rst X-Git-Tag: v2025.10-rc1~91^2~44^2 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7f4af4c5509ab1bf605bf1af96c854b2c9c354e6;p=pandora-u-boot.git doc: board/qualcomm: remove signing references from dragonwing.rst The mkmbn tool isn't available yet, so it's still necessary to use qtestsign for signing. Update the docs to describe it, this can be reverted once mkmbn and the associated tooling is merged. Link: https://lore.kernel.org/u-boot/20250616162626.247802-1-casey.connolly@linaro.org Signed-off-by: Casey Connolly --- diff --git a/doc/board/qualcomm/dragonwing.rst b/doc/board/qualcomm/dragonwing.rst index 12a0bfb3544..d4899415309 100644 --- a/doc/board/qualcomm/dragonwing.rst +++ b/doc/board/qualcomm/dragonwing.rst @@ -22,11 +22,14 @@ First, setup ``CROSS_COMPILE`` for aarch64. Then, build U-Boot for ``QCS615``, ` $ make qcom_qcs8300_defconfig $ make -j8 u-boot.mbn -This will build the signed ``u-boot.mbn`` in the configured output directory. -The firmware expects firmware ELF images to be "signed". The signature -does not provide any security in this case, but it provides the firmware -with some required metadata. More information -about image signing can be found in :doc:`signing`. +Although the board does not have secure boot set up by default, +the firmware still expects firmware ELF images to be "signed". The signature +does not provide any security in this case, but it provides the firmware with +some required metadata. + +To "sign" ``u-boot.elf`` you can use e.g. `qtestsign`_:: + + $ qtestsign -v6 aboot -o u-boot.mbn u-boot.elf Then flash the resulting ``u-boot.mbn`` to the ``uefi_a`` partition on your device with ``fastboot flash uefi_a u-boot.mbn``.