diff options
| author | Juan Castillo <juan.castillo@arm.com> | 2015-12-10 15:49:17 +0000 |
|---|---|---|
| committer | Juan Castillo <juan.castillo@arm.com> | 2015-12-14 12:31:16 +0000 |
| commit | f59821d51255f14e0ac00eef7bc98ef75c686876 (patch) | |
| tree | 2a62aec945a1c30ed695ba2a3336c08d94183ab3 /docs/auth-framework.md | |
| parent | 516beb585c23056820a854b12c77a6f62cbc5c8b (diff) | |
| download | platform_external_arm-trusted-firmware-f59821d51255f14e0ac00eef7bc98ef75c686876.tar.gz platform_external_arm-trusted-firmware-f59821d51255f14e0ac00eef7bc98ef75c686876.tar.bz2 platform_external_arm-trusted-firmware-f59821d51255f14e0ac00eef7bc98ef75c686876.zip | |
Replace all SCP FW (BL0, BL3-0) references
This patch replaces all references to the SCP Firmware (BL0, BL30,
BL3-0, bl30) with the image terminology detailed in the TF wiki
(https://github.com/ARM-software/arm-trusted-firmware/wiki):
BL0 --> SCP_BL1
BL30, BL3-0 --> SCP_BL2
bl30 --> scp_bl2
This change affects code, documentation, build system, tools and
platform ports that load SCP firmware. ARM plaforms have been
updated to the new porting API.
IMPORTANT: build option to specify the SCP FW image has changed:
BL30 --> SCP_BL2
IMPORTANT: This patch breaks compatibility for platforms that use BL2
to load SCP firmware. Affected platforms must be updated as follows:
BL30_IMAGE_ID --> SCP_BL2_IMAGE_ID
BL30_BASE --> SCP_BL2_BASE
bl2_plat_get_bl30_meminfo() --> bl2_plat_get_scp_bl2_meminfo()
bl2_plat_handle_bl30() --> bl2_plat_handle_scp_bl2()
Change-Id: I24c4c1a4f0e4b9f17c9e4929da815c4069549e58
Diffstat (limited to 'docs/auth-framework.md')
| -rw-r--r-- | docs/auth-framework.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/auth-framework.md b/docs/auth-framework.md index b910eaebf..f6455b9ed 100644 --- a/docs/auth-framework.md +++ b/docs/auth-framework.md @@ -211,8 +211,9 @@ It is responsible for: 3. Tracking which images have been verified. In case an image is a part of multiple CoTs then it should be verified only once e.g. the Trusted World Key Certificate in the TBBR-Client spec. contains information to verify - BL3-0, BL3-1, BL3-2 each of which have a separate CoT. (This responsibility - has not been described in this document but should be trivial to implement). + SCP_BL2, BL3-1, BL3-2 each of which have a separate CoT. (This + responsibility has not been described in this document but should be + trivial to implement). 4. Reusing memory meant for a data image to verify authentication images e.g. in the CoT described in Diagram 2, each certificate can be loaded and @@ -632,7 +633,7 @@ is, however, a minimum set of images that are mandatory in the Trusted Firmware and thus all CoTs must present: * `BL2` -* `BL3-0` (platform specific) +* `SCP_BL2` (platform specific) * `BL3-1` * `BL3-2` (optional) * `BL3-3` |