Skip to content

Commit 64b25a3

Browse files
committed
docs: Update secure-boot link in readme
1 parent 6f8549e commit 64b25a3

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

Readme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -184,4 +184,4 @@ Example metadata file contents written to `metadata/SERIAL_NUMBER.json`
184184

185185
<a name="secure-boot"></a>
186186
## Secure Boot
187-
This repository contains the low-level tools and firmware images for enabling secure-boot/verified boot on Compute Module 4 and Compute Module 5.
187+
See: [secure-boot](docs/secure-boot.md) reference.

docs/secure-boot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ Secure-boot uses cryptographic signing to ensure the OS kernel and all required
2222
If any signature or hash verification fails, the current boot mode is aborted and the firmware advances to the next boot mode.
2323

2424
See also:-
25-
* Secure boot BCM2711 [chain of trust diagram](docs/secure-boot-chain-of-trust-2711.pdf).
26-
* Secure boot BCM2712 [chain of trust diagram](docs/secure-boot-chain-of-trust-2712.pdf).
25+
* Secure boot BCM2711 [chain of trust diagram](secure-boot-chain-of-trust-2711.pdf).
26+
* Secure boot BCM2712 [chain of trust diagram](secure-boot-chain-of-trust-2712.pdf).
2727

2828
## boot.img files
2929
Secure-boot requires a self-contained ramdisk (`boot.img`) FAT image containing the GPU firmware, kernel and any other dependencies that would normally be loaded from the boot partition.

0 commit comments

Comments
 (0)