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 <casey.connolly@linaro.org>
This commit is contained in:
Casey Connolly
2025-06-16 18:25:31 +02:00
committed by Tom Rini
parent 35a03711ce
commit 7f4af4c550

View File

@@ -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``.