Commit 28dab587 authored by Soby Mathew's avatar Soby Mathew Committed by TrustedFirmware Code Review
Browse files

Merge "Doc: Update link to TBBR-CLIENT specification" into integration

parents c3e4e088 c1491eba
...@@ -80,7 +80,7 @@ Chain of Trust ...@@ -80,7 +80,7 @@ Chain of Trust
A CoT is basically a sequence of authentication images which usually starts with A CoT is basically a sequence of authentication images which usually starts with
a root of trust and culminates in a single data image. The following diagram a root of trust and culminates in a single data image. The following diagram
illustrates how this maps to a CoT for the BL31 image described in the illustrates how this maps to a CoT for the BL31 image described in the
TBBR-Client specification. `TBBR-Client specification`_.
:: ::
...@@ -969,3 +969,4 @@ of SHA-256 with smaller memory footprint (~1.5 KB less) but slower (~30%). ...@@ -969,3 +969,4 @@ of SHA-256 with smaller memory footprint (~1.5 KB less) but slower (~30%).
.. _Trusted Board Boot: ./trusted-board-boot.rst .. _Trusted Board Boot: ./trusted-board-boot.rst
.. _Platform Porting Guide: ./porting-guide.rst .. _Platform Porting Guide: ./porting-guide.rst
.. _TBBR-Client specification: https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a
...@@ -2655,8 +2655,7 @@ kernel at boot time. These can be found in the ``fdts`` directory. ...@@ -2655,8 +2655,7 @@ kernel at boot time. These can be found in the ``fdts`` directory.
References References
---------- ----------
.. [#] Trusted Board Boot Requirements CLIENT PDD (Arm DEN0006C-1). Available .. [#] `Trusted Board Boot Requirements CLIENT (TBBR-CLIENT) Armv8-A (ARM DEN0006D)`_
under NDA through your Arm account representative.
.. [#] `Power State Coordination Interface PDD`_ .. [#] `Power State Coordination Interface PDD`_
.. [#] `SMC Calling Convention PDD`_ .. [#] `SMC Calling Convention PDD`_
.. [#] `TF-A Interrupt Management Design guide`_. .. [#] `TF-A Interrupt Management Design guide`_.
...@@ -2684,5 +2683,6 @@ References ...@@ -2684,5 +2683,6 @@ References
.. _Xlat_tables design: xlat-tables-lib-v2-design.rst .. _Xlat_tables design: xlat-tables-lib-v2-design.rst
.. _Exception Handling Framework: exception-handling.rst .. _Exception Handling Framework: exception-handling.rst
.. _ROMLIB Design: romlib-design.rst .. _ROMLIB Design: romlib-design.rst
.. _Trusted Board Boot Requirements CLIENT (TBBR-CLIENT) Armv8-A (ARM DEN0006D): https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a
.. |Image 1| image:: diagrams/rt-svc-descs-layout.png?raw=true .. |Image 1| image:: diagrams/rt-svc-descs-layout.png?raw=true
...@@ -12,9 +12,9 @@ the platform by authenticating all firmware images up to and including the ...@@ -12,9 +12,9 @@ the platform by authenticating all firmware images up to and including the
normal world bootloader. It does this by establishing a Chain of Trust using normal world bootloader. It does this by establishing a Chain of Trust using
Public-Key-Cryptography Standards (PKCS). Public-Key-Cryptography Standards (PKCS).
This document describes the design of Trusted Firmware-A (TF-A) TBB, which is This document describes the design of Trusted Firmware-A (TF-A) TBB, which is an
an implementation of the Trusted Board Boot Requirements (TBBR) specification, implementation of the `Trusted Board Boot Requirements (TBBR)`_ specification,
Arm DEN0006C-1. It should be used in conjunction with the `Firmware Update`_ Arm DEN0006D. It should be used in conjunction with the `Firmware Update`_
design document, which implements a specific aspect of the TBBR. design document, which implements a specific aspect of the TBBR.
Chain of Trust Chain of Trust
...@@ -206,7 +206,7 @@ Authentication Framework ...@@ -206,7 +206,7 @@ Authentication Framework
The authentication framework included in TF-A provides support to implement The authentication framework included in TF-A provides support to implement
the desired trusted boot sequence. Arm platforms use this framework to the desired trusted boot sequence. Arm platforms use this framework to
implement the boot requirements specified in the TBBR-client document. implement the boot requirements specified in the `TBBR-client`_ document.
More information about the authentication framework can be found in the More information about the authentication framework can be found in the
`Auth Framework`_ document. `Auth Framework`_ document.
...@@ -230,9 +230,11 @@ for building and using the tool can be found in the `User Guide`_. ...@@ -230,9 +230,11 @@ for building and using the tool can be found in the `User Guide`_.
-------------- --------------
*Copyright (c) 2015-2018, Arm Limited and Contributors. All rights reserved.* *Copyright (c) 2015-2019, Arm Limited and Contributors. All rights reserved.*
.. _Firmware Update: firmware-update.rst .. _Firmware Update: firmware-update.rst
.. _X.509 v3: https://tools.ietf.org/rfc/rfc5280.txt .. _X.509 v3: https://tools.ietf.org/rfc/rfc5280.txt
.. _User Guide: user-guide.rst .. _User Guide: user-guide.rst
.. _Auth Framework: auth-framework.rst .. _Auth Framework: auth-framework.rst
.. _TBBR-client: https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a
.. _Trusted Board Boot Requirements (TBBR): `TBBR-client`_
...@@ -12,7 +12,7 @@ at Exception Level 3 (EL3). It implements various Arm interface standards, ...@@ -12,7 +12,7 @@ at Exception Level 3 (EL3). It implements various Arm interface standards,
such as: such as:
- The `Power State Coordination Interface (PSCI)`_ - The `Power State Coordination Interface (PSCI)`_
- Trusted Board Boot Requirements (TBBR, Arm DEN0006C-1) - `Trusted Board Boot Requirements CLIENT (TBBR-CLIENT)`_
- `SMC Calling Convention`_ - `SMC Calling Convention`_
- `System Control and Management Interface (SCMI)`_ - `System Control and Management Interface (SCMI)`_
- `Software Delegated Exception Interface (SDEI)`_ - `Software Delegated Exception Interface (SDEI)`_
...@@ -320,6 +320,7 @@ Security advisories ...@@ -320,6 +320,7 @@ Security advisories
.. _Secure Monitor: http://www.arm.com/products/processors/technologies/trustzone/tee-smc.php .. _Secure Monitor: http://www.arm.com/products/processors/technologies/trustzone/tee-smc.php
.. _Power State Coordination Interface (PSCI): PSCI_ .. _Power State Coordination Interface (PSCI): PSCI_
.. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf .. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf
.. _Trusted Board Boot Requirements CLIENT (TBBR-CLIENT): https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a
.. _SMC Calling Convention: http://infocenter.arm.com/help/topic/com.arm.doc.den0028b/ARM_DEN0028B_SMC_Calling_Convention.pdf .. _SMC Calling Convention: http://infocenter.arm.com/help/topic/com.arm.doc.den0028b/ARM_DEN0028B_SMC_Calling_Convention.pdf
.. _System Control and Management Interface (SCMI): SCMI_ .. _System Control and Management Interface (SCMI): SCMI_
.. _SCMI: http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/DEN0056A_System_Control_and_Management_Interface.pdf .. _SCMI: http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/DEN0056A_System_Control_and_Management_Interface.pdf
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment