| Message ID | 20221021111641.27627-1-Sai.Sathujoda@toshiba-tsip.com (mailing list archive) |
|---|---|
| State | Handled Elsewhere |
| Headers | show |
| Series | [isar-cip-core] doc/README.secureboot.md : Add method to check secure boot status in arm arch. | expand |
On 21.10.22 13:16, Sai.Sathujoda@toshiba-tsip.com wrote: > From: Sai <Sai.Sathujoda@toshiba-tsip.com> > > The dmesg will not show secure boot status for arm64 or armhf > architectures. > Signed-off-by: Sai <Sai.Sathujoda@toshiba-tsip.com> > --- > doc/README.secureboot.md | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/doc/README.secureboot.md b/doc/README.secureboot.md > index 26d8c87..714331f 100644 > --- a/doc/README.secureboot.md > +++ b/doc/README.secureboot.md > @@ -217,6 +217,10 @@ After boot check the dmesg for secure boot status like below: > root@demo:~# dmesg | grep Secure > [ 0.008368] Secure boot enabled > ``` > +In case of arm64 or armhf architectures, the secure boot status can be found in bootloader logs like below: > +``` > +EFI stub: UEFI Secure Boot is enabled. > +``` > ## Example: Update the image > > For updating the image, the following steps are necessary: Indeed - thanks, applied. Jan
diff --git a/doc/README.secureboot.md b/doc/README.secureboot.md index 26d8c87..714331f 100644 --- a/doc/README.secureboot.md +++ b/doc/README.secureboot.md @@ -217,6 +217,10 @@ After boot check the dmesg for secure boot status like below: root@demo:~# dmesg | grep Secure [ 0.008368] Secure boot enabled ``` +In case of arm64 or armhf architectures, the secure boot status can be found in bootloader logs like below: +``` +EFI stub: UEFI Secure Boot is enabled. +``` ## Example: Update the image For updating the image, the following steps are necessary: