summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCasey Connolly <[email protected]>2025-06-16 18:25:31 +0200
committerTom Rini <[email protected]>2025-06-24 07:54:51 -0600
commit7f4af4c5509ab1bf605bf1af96c854b2c9c354e6 (patch)
tree98b5cc94c07a730bd08458c2c6461dddf4513fbc
parent35a03711cec0d7da6844c2ffe1c58022ed8df65f (diff)
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/[email protected] Signed-off-by: Casey Connolly <[email protected]>
-rw-r--r--doc/board/qualcomm/dragonwing.rst13
1 files changed, 8 insertions, 5 deletions
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``.