Sandrine Bailleux 292585be90 docs(porting): move porting guide upper in table of contents ... The porting guide is currently hosted under the 'Getting started' section. Yet, porting the full firmware to a new platform is probably not the first thing that one would do. Before delving into the details, one would probably start by building the code for an emulated platform, such as Arm FVP. Furthermore, the porting guide is such a big and important document that it probably deserves being visible in the main table of contents. Thus, move it just above the list of supported platforms. Signed-off-by: Sandrine Bailleux <sandrine.bailleux@arm.com> Change-Id: I51b3d2a93832505ab90d73c823f06f9540e84c77		2023-04-11 10:11:04 +02:00
..
build-internals.rst	build: restrict usage of CTX_INCLUDE_EL2_REGS	2022-12-01 12:04:40 +02:00
build-options.rst	docs(sve): update defaults for FEAT_SVE	2023-04-03 17:05:57 +01:00
docs-build.rst	Merge changes If90a18ee,I02e88f8c,Iea447fb5,Ie0570481,Ieeb14cfc into integration	2022-11-16 16:18:54 +01:00
image-terminology.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00
index.rst	docs(porting): move porting guide upper in table of contents	2023-04-11 10:11:04 +02:00
initial-build.rst	docs(build): clarify getting started section	2022-11-16 14:06:48 +00:00
prerequisites.rst	fix(docs): make required compiler version == rather than >=	2023-02-13 15:57:25 +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