Boyan Karatotev b50838bae7 docs(build): clarify getting started section ... The Getting started section is very difficult to follow. Building the fip comes before building the files it needs, the BL33 requirement is given in a somewhat hand wavy way, and the Arm Developer website download provides a lot of targets and the guide is not clear which ones are needed on download. Swapping the initial build and supporting tools sections makes the flow more natural and the supporting tools section then becomes clear. Explicitly mentioning the GCC targets avoids confusion for people less familiar with the project (eg. new starters). Signed-off-by: Boyan Karatotev <boyan.karatotev@arm.com> Change-Id: I02e88f8c279db6d8eda68f634e8473c02b733963		2022-11-16 14:06:48 +00:00
..
build-options.rst	feat(cert-create): update for ECDSA brainpoolP256r/t1 support	2022-11-14 11:25:01 +01:00
docs-build.rst	docs(build): clarify docs building instructions	2022-11-16 14:06:48 +00:00
image-terminology.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00
index.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00
initial-build.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00
porting-guide.rst	fix(cpus): update doc and check for plat_can_cmo	2022-11-14 15:31:12 +01:00
prerequisites.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00
psci-lib-integration-guide.rst	docs: document do_panic() and panic() helper functions	2022-11-08 14:09:33 +00:00
rt-svc-writers-guide.rst	docs(rme): add description of TF-A changes for RME	2021-11-15 22:20:07 +01:00
tools-build.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00