Clarify "Getting the TF source code" in user guide

Remove the following redundant sentence from the user guide, which
implies the user should use the TF version from the Linaro release,
which was not the intention:

"However, the rest of this document assumes that you got the
Trusted Firmware as part of the Linaro release."

Also, tidied up the grammar in this section.

Change-Id: I5dae0b68d3683e2a85a7b3c6a31222182a66f6c8
This commit is contained in:
Dan Handley 2015-12-21 16:44:37 +00:00
parent f162c536ca
commit 3f61835baf
1 changed files with 16 additions and 20 deletions

View File

@ -57,47 +57,43 @@ optional tools may be needed:
4. Getting the Trusted Firmware source code 4. Getting the Trusted Firmware source code
-------------------------------------------- --------------------------------------------
The Trusted Firmware source code can be obtained as part of the standard Linaro The Trusted Firmware (TF) source code can be obtained as part of the standard
releases, which provide a full software stack, including the Trusted Firmware, Linaro releases, which provide a full software stack, including TF, normal
normal world firmware, Linux kernel and device tree, file system as well as any world firmware, Linux kernel and device tree, file system as well as any
additional micro-controller firmware required by the platform. This version of additional micro-controller firmware required by the platform. This TF version
Trusted Firmware is tested with the [Linaro 15.10 Release][Linaro Release Notes]. is tested with the [Linaro 15.10 Release][Linaro Release Notes].
Note 1: Both the LSK kernel or the latest tracking kernel can be used with the Note 1: Both the LSK kernel or the latest tracking kernel can be used with TF;
ARM Trusted Firmware, choose the one that best suits your needs. choose the one that best suits your needs.
Note 2: Currently to run the latest tracking kernel on FVP with GICv3 driver, Note 2: Currently to run the latest tracking kernel on FVP with GICv3 driver,
some modifications are required to UEFI. Refer some modifications are required to UEFI. Refer
[here](#11--changes-required-for-booting-linux-on-fvp-in-gicv3-mode) [here](#11--changes-required-for-booting-linux-on-fvp-in-gicv3-mode)
for more details. for more details.
The Trusted Firmware source code can then be found in the `arm-tf/` directory. The TF source code will then be in `arm-tf/`. This is the upstream git
This is the full git repository cloned from Github. The revision checked out by repository cloned from GitHub. The revision checked out by the `repo` tool is
the `repo` tool is indicated by the manifest file. Depending on the manifest indicated by the manifest file. Depending on the manifest file you're using,
file you're using, this might not be the latest development version. To this might not be the latest upstream version. To synchronize your copy of the
synchronize your copy of the repository and get the latest updates, use the repository and get the latest updates, use the following commands:
following commands:
# Change to the Trusted Firmware directory. # Change to the Trusted Firmware directory.
cd arm-tf cd arm-tf
# Download the latest code from Github. # Download the latest code from GitHub.
git fetch github git fetch github
# Update your working copy to the latest master. # Update your working copy to the latest master.
# This command will create a local branch master that tracks the remote # This command will create a local branch master that tracks the remote
# branch master from Github. # branch master from GitHub.
git checkout --track github/master git checkout --track github/master
Alternatively, the Trusted Firmware source code can be fetched on its own Alternatively, the TF source code can be separately cloned from the upstream
from GitHub: GitHub repository:
git clone https://github.com/ARM-software/arm-trusted-firmware.git git clone https://github.com/ARM-software/arm-trusted-firmware.git
However, the rest of this document assumes that you got the Trusted Firmware
as part of the Linaro release.
5. Building the Trusted Firmware 5. Building the Trusted Firmware
--------------------------------- ---------------------------------