Hi,
I just updated the technical report https://docs.google.com/document/d/1CLkhLRaz_zcCq44DLGmPZQFPbYHOC6nzPowaL0XmRk0/edit?usp=sharing with a section on "Trusting DT" that is the result of my analysis of the discussion we had (not what I presented).
Please comment, correct, update...
Cordially,
FF
On 24.07.20 17:14, François Ozog wrote:
We should make sure that the report does not become unnecessarily architecture or OS specific.
Based on the EBBR we can boot on x86, ARM, RISC-V into operating system like OpenBSD, FreeBSD, Linux, Windows.
The first stage firmware can be OpenBSI, U-Boot SPL, or TF-A.
The term BL33 is specific to TF-A. In most instances the firmware providing the UEFI API or otherwise loading the operating system is meant.
I have appended a commented/edited version. Activate View->Track Changes in LibreOffice to see where I modified the text.
Best regards
Heinrich
Sorry for the late reply. 3 weeks vacation + get up to speed on all topics...
On Fri, 24 Jul 2020 at 19:46, Heinrich Schuchardt xypron.glpk@gmx.de wrote:
Based on the EBBR we can boot on x86, ARM, RISC-V into operating system
precise definition in the context of the TR.
I have appended a commented/edited version. Activate View->Track Changes
in LibreOffice to see where I modified the text.
I have MS Word.I think I see your changes but not fully sure. I am merging
your changes, let me know if that worked (should be implemented by tomorrow).
Best regards
Heinrich
On Thu, 27 Aug 2020 at 15:46, François Ozog francois.ozog@linaro.org wrote:
In the intent to be fully agnostic (architecture, platform,firmware framework,OS...), the Terminology section have defined: Booted Payload - the thing that is booted Firmware Framework - (TF-A and U-Boot are such frameworks Handover Function - The component that stages Booted Payload in memory and transfer control to it (and may implement UEFI interface) Platform Initialization Function (new)
I have updated text to deliver on genericity.
boot-architecture@lists.linaro.org