diff --git a/docs/change-log.rst b/docs/change-log.rst index 71f24fd..4ef3ac1 100644 --- a/docs/change-log.rst +++ b/docs/change-log.rst @@ -1626,7 +1626,7 @@ - `Power Domain Topology Design`_ - Applied the new image terminology to the code base and documentation, as - described on the `TF-A wiki on GitHub`_. + described in the `image terminology document`_. - The build system has been reworked to improve readability and facilitate adding future extensions. @@ -2420,7 +2420,7 @@ -------------- -*Copyright (c) 2013-2018, Arm Limited and Contributors. All rights reserved.* +*Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.* .. _SDEI Specification: http://infocenter.arm.com/help/topic/com.arm.doc.den0054a/ARM_DEN0054A_Software_Delegated_Exception_Interface.pdf .. _PSCI Integration Guide: ./getting_started/psci-lib-integration-guide.rst @@ -2431,7 +2431,7 @@ .. _Firmware Design: ./design/firmware-design.rst .. _TF-A Reset Design: ./design/reset-design.rst .. _Power Domain Topology Design: ./design/psci-pd-tree.rst -.. _TF-A wiki on GitHub: https://github.com/ARM-software/arm-trusted-firmware/wiki/ARM-Trusted-Firmware-Image-Terminology +.. _image terminology document: ./getting_started/image-terminology.rst .. _Authentication Framework: ./design/auth-framework.rst .. _OP-TEE Dispatcher: ./spd/optee-dispatcher.rst .. _tf-issue#501: https://github.com/ARM-software/tf-issues/issues/501 diff --git a/docs/components/firmware-update.rst b/docs/components/firmware-update.rst index d6bb6ce..30bdc24 100644 --- a/docs/components/firmware-update.rst +++ b/docs/components/firmware-update.rst @@ -392,11 +392,11 @@ -------------- -*Copyright (c) 2015-2018, Arm Limited and Contributors. All rights reserved.* +*Copyright (c) 2015-2019, Arm Limited and Contributors. All rights reserved.* .. _Trusted Board Boot: ../design/trusted-board-boot.rst .. _Porting Guide: ../getting_started/porting-guide.rst -.. _here: https://github.com/ARM-software/arm-trusted-firmware/wiki/ARM-Trusted-Firmware-Image-Terminology +.. _here: ../getting_started/image-terminology.rst .. _Authentication Framework Design: ../design/auth-framework.rst .. _Universally Unique Identifier: https://tools.ietf.org/rfc/rfc4122.txt diff --git a/docs/plat/fvp_ve.rst b/docs/plat/fvp_ve.rst index 5253863..6abf9e5 100644 --- a/docs/plat/fvp_ve.rst +++ b/docs/plat/fvp_ve.rst @@ -1,12 +1,11 @@ Arm Versatile Express ===================== -Versatile Express (VE) family development platform provides an -ultra fast environment for prototyping arm-v7 System-on-Chip designs. -VE Fixed Virtual Platforms (FVP) are simulations of Versatile Express boards. -The platform in arm-trusted-firmware has been verified with Arm Cortex-A5 -and Cortex-A7 VE FVP's. This platform is tested on and only expected to work -with single core models. +Versatile Express (VE) family development platform provides an ultra fast +environment for prototyping Armv7 System-on-Chip designs. VE Fixed Virtual +Platforms (FVP) are simulations of Versatile Express boards. The platform in +Trusted Firmware-A has been verified with Arm Cortex-A5 and Cortex-A7 VE FVP's. +This platform is tested on and only expected to work with single core models. Boot Sequence ------------- @@ -20,7 +19,7 @@ ~~~~~~~~~~~~~~ - `U-boot `__ -- `arm-trusted-firmware `__ +- `Trusted Firmware-A `__ Build Procedure ~~~~~~~~~~~~~~~ @@ -71,7 +70,7 @@ ~~~~~~~~~~~~~ The following model parameters should be used to boot Linux using the build of -arm-trusted-firmware-a made using the above make commands: +Trusted Firmware-A made using the above make commands: .. code:: shell diff --git a/docs/process/platform-compatibility-policy.rst b/docs/process/platform-compatibility-policy.rst index 1c80eb5..a11ba38 100644 --- a/docs/process/platform-compatibility-policy.rst +++ b/docs/process/platform-compatibility-policy.rst @@ -20,18 +20,19 @@ the contributor of the change is expected to make good effort to migrate the upstream platforms to the new interface. -The `Release information`_ documents the deprecated interfaces and the intended -release after which it will be removed. When an interface is deprecated, the -page must be updated to indicate the release after which the interface will be -removed. This must be at least 1 full release cycle in future. For non-trivial -interface changes, a `tf-issue`_ should be posted to notify platforms that they -should migrate away from the deprecated interfaces. Platforms are expected to -migrate before the removal of the deprecated interface. +The deprecated interfaces are listed inside `Release information`_ as well as +the release after which each one will be removed. When an interface is +deprecated, the page must be updated to indicate the release after which the +interface will be removed. This must be at least 1 full release cycle in future. +For non-trivial interface changes, an email should be sent out to the `TF-A +public mailing list`_ to notify platforms that they should migrate away from the +deprecated interfaces. Platforms are expected to migrate before the removal of +the deprecated interface. -------------- -*Copyright (c) 2018, Arm Limited and Contributors. All rights reserved.* +*Copyright (c) 2018-2019, Arm Limited and Contributors. All rights reserved.* .. _Porting Guide: ../getting_started/porting-guide.rst -.. _Release information: https://github.com/ARM-software/arm-trusted-firmware/wiki/TF-A-Release-information#removal-of-deprecated-interfaces -.. _tf-issue: https://github.com/ARM-software/tf-issues/issues +.. _Release information: ./release-information.rst#removal-of-deprecated-interfaces +.. _TF-A public mailing list: https://lists.trustedfirmware.org/mailman/listinfo/tf-a