From: Simon Glass <sjg@chromium.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Tom Rini <trini@konsulko.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Linus Walleij <linus.walleij@linaro.org>,
u-boot@lists.denx.de, Peter Hoyes <peter.hoyes@arm.com>,
Liviu Dudau <Liviu.Dudau@foss.arm.com>,
David Feng <fenghua@phytium.com.cn>
Subject: Re: [PATCH 1/2] doc: Add documentation for the Arm VExpress64 board configs
Date: Fri, 17 Dec 2021 09:37:12 -0700 [thread overview]
Message-ID: <CAPnjgZ2uo6szvSMf_w6iNe4tquz4W+1gt7wHaHWj-Oe3+mUGsA@mail.gmail.com> (raw)
In-Reply-To: <20211214175539.3173701-2-andre.przywara@arm.com>
Hi Andre,
On Tue, 14 Dec 2021 at 10:55, Andre Przywara <andre.przywara@arm.com> wrote:
>
> From: Peter Hoyes <Peter.Hoyes@arm.com>
>
> Create a new documentation section for Arm Ltd boards with a sub-page
> for the FVP VExpress64 system.
>
> Signed-off-by: Peter Hoyes <Peter.Hoyes@arm.com>
> [Andre: remove Juno stub]
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>
> ---
> doc/board/armltd/fvp64.rst | 30 ++++++++++++++++++++++++++++++
> doc/board/armltd/index.rst | 10 ++++++++++
> doc/board/index.rst | 1 +
> 3 files changed, 41 insertions(+)
> create mode 100644 doc/board/armltd/fvp64.rst
> create mode 100644 doc/board/armltd/index.rst
>
> diff --git a/doc/board/armltd/fvp64.rst b/doc/board/armltd/fvp64.rst
> new file mode 100644
> index 0000000000..9817b0aa3f
> --- /dev/null
> +++ b/doc/board/armltd/fvp64.rst
> @@ -0,0 +1,30 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +Fixed Virtual Platforms
> +=======================
> +
> +The Fixed Virtual Platforms (FVP) are complete software simulations of an Arm
> +system, including processor, memory and peripherals. They are set out in a
> +"programmer's view", which gives a comprehensive model on which to build and
> +test software.
> +
> +The supported FVPs are available free of charge and can be downloaded from the
> +Arm developer site [1]_ (user registration might be required).
> +
> +Supported features:
> +
> + * GICv3
> + * Generic timer
> + * PL011 UART
> +
> +The default configuration assumes that U-Boot is bootstrapped using a suitable
> +bootloader, such as Trusted Firmware-A [4]_. The u-boot binary can be passed
TF-A has become a bootloader?!
> +into the TF-A build: ``make PLAT=<platform> all fip BL33=u-boot.bin``
What is <platform> in this case?
> +
> +The FVPs can be debugged using Arm Development Studio [2]_.
> +
> +References
> +----------
> +
> +.. [1] https://developer.arm.com/tools-and-software/simulation-models/fixed-virtual-platforms
> +.. [2] https://developer.arm.com/tools-and-software/embedded/arm-development-studio
> diff --git a/doc/board/armltd/index.rst b/doc/board/armltd/index.rst
> new file mode 100644
> index 0000000000..caa6fd2bb0
> --- /dev/null
> +++ b/doc/board/armltd/index.rst
> @@ -0,0 +1,10 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +.. Copyright (C) 2021 Arm Ltd.
> +
> +ARM Ltd. boards and emulated systems
> +====================================
> +
> +.. toctree::
> + :maxdepth: 2
> +
> + fvp64
> diff --git a/doc/board/index.rst b/doc/board/index.rst
> index 74ea33e081..78b486538b 100644
> --- a/doc/board/index.rst
> +++ b/doc/board/index.rst
> @@ -11,6 +11,7 @@ Board-specific doc
> AndesTech/index
> amlogic/index
> apple/index
> + armltd/index
> atmel/index
> congatec/index
> coreboot/index
> --
> 2.25.1
>
Regards,
Simon
next prev parent reply other threads:[~2021-12-17 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 17:55 [PATCH 0/2] Arm Juno board documentation Andre Przywara
2021-12-14 17:55 ` [PATCH 1/2] doc: Add documentation for the Arm VExpress64 board configs Andre Przywara
2021-12-15 12:45 ` Sudeep Holla
2021-12-17 16:37 ` Simon Glass [this message]
2021-12-20 17:46 ` Andre Przywara
2021-12-14 17:55 ` [PATCH 2/2] doc: add Arm Juno board documentation Andre Przywara
2021-12-15 12:44 ` Sudeep Holla
2021-12-16 17:55 ` Andre Przywara
2021-12-15 15:33 ` Robin Murphy
2021-12-16 17:56 ` Andre Przywara
2021-12-17 16:37 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPnjgZ2uo6szvSMf_w6iNe4tquz4W+1gt7wHaHWj-Oe3+mUGsA@mail.gmail.com \
--to=sjg@chromium.org \
--cc=Liviu.Dudau@foss.arm.com \
--cc=andre.przywara@arm.com \
--cc=fenghua@phytium.com.cn \
--cc=linus.walleij@linaro.org \
--cc=peter.hoyes@arm.com \
--cc=sudeep.holla@arm.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).