From 8972e0bff574307d6af50ed71ed6ff4edb465b96 Mon Sep 17 00:00:00 2001 From: Ilias Apalodimas <ilias.apalodimas@linaro.org> Date: Mon, 27 Sep 2021 15:47:57 +0300 Subject: [PATCH] match chapter 1 wording on bootloaders to our conventions Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> --- source/chapter1-about.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/chapter1-about.rst b/source/chapter1-about.rst index cfaab94..26a85cd 100644 --- a/source/chapter1-about.rst +++ b/source/chapter1-about.rst @@ -60,11 +60,11 @@ without UEFI is outside the scope of this document. - The first stage bootloader **must** be able to access our firmware NVCounter. - UEFI capsule updates are the mechanism used for delivering firmware updates. Refer to [#UEFICapsuleUpdateNote]_ for details. -- We assume that the masked ROM can load the first staged boot loader (e.g TF-A) from a dual image. +- We assume that our immutable stage loader can load the second stage boot loader (e.g TF-A) from a dual image. In case the masked ROM can not boot with an alternative location, similar functionality - can be added to the secondary bootloader stage. - In that case updating the Secondary bootloader stage should be disallowed from OTA - update. In person update of Secondary bootloader stage may be possible and may require extra + **must** be added to the secondary bootloader stage. + In that case updating the secondary bootloader stage should be disallowed from OTA + update. In person update of secondary bootloader stage may be possible and may require extra tools or procedures but that is out of the scope of this document. - Update process can target a single firmware component or multiple components. Updating multiple components and multiplexing boot combinations can be very challenging. In this document we treat -- GitLab