From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Graeme Gregory" <graeme@nuviainc.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Shashi Mallela" <shashi.mallela@linaro.org>,
"open list:ARM TCG CPUs" <qemu-arm@nongnu.org>,
"Leif Lindholm" <leif@nuviainc.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH v2] docs: add some notes on the sbsa-ref machine
Date: Wed, 4 Nov 2020 16:52:54 +0000 [thread overview]
Message-ID: <20201104165254.24822-1-alex.bennee@linaro.org> (raw)
We should at least document what this machine is about.
Reviewed-by: Graeme Gregory <graeme@nuviainc.com>
Cc: Leif Lindholm <leif@nuviainc.com>
Cc: Shashi Mallela <shashi.mallela@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
---
v2
- reworded command line bit as per Leif
- s/cortex-a57 cpus/AArch64 CPUs/
- dropped the trailing .'s
---
docs/system/arm/sbsa.rst | 32 ++++++++++++++++++++++++++++++++
docs/system/target-arm.rst | 1 +
2 files changed, 33 insertions(+)
create mode 100644 docs/system/arm/sbsa.rst
diff --git a/docs/system/arm/sbsa.rst b/docs/system/arm/sbsa.rst
new file mode 100644
index 0000000000..b8ecfdb62f
--- /dev/null
+++ b/docs/system/arm/sbsa.rst
@@ -0,0 +1,32 @@
+Arm Server Base System Architecture Reference board (``sbsa-ref``)
+==================================================================
+
+While the `virt` board is a generic board platform that doesn't match
+any real hardware the `sbsa-ref` board intends to look like real
+hardware. The `Server Base System Architecture
+<https://developer.arm.com/documentation/den0029/latest>` defines a
+minimum base line of hardware support and importantly how the firmware
+reports that to any operating system. It is a static system that
+reports a very minimal DT to the firmware for non-discoverable
+information about components affected by the qemu command line (i.e.
+cpus and memory). As a result it must have a firmware specifically
+built to expect a certain hardware layout (as you would in a real
+machine).
+
+It is intended to be a machine for developing firmware and testing
+standards compliance with operating systems.
+
+Supported devices
+"""""""""""""""""
+
+The sbsa-ref board supports:
+
+ - A configurable number of AArch64 CPUs
+ - GIC version 3
+ - System bus AHCI controller
+ - System bus EHCI controller
+ - CDROM and hard disc on AHCI bus
+ - E1000E ethernet card on PCIe bus
+ - VGA display adaptor on PCIe bus
+ - A generic SBSA watchdog device
+
diff --git a/docs/system/target-arm.rst b/docs/system/target-arm.rst
index fdcf25c237..9636f3fd00 100644
--- a/docs/system/target-arm.rst
+++ b/docs/system/target-arm.rst
@@ -79,6 +79,7 @@ undocumented; you can get a complete list by running
arm/mps2
arm/musca
arm/realview
+ arm/sbsa-ref
arm/versatile
arm/vexpress
arm/aspeed
--
2.20.1
next reply other threads:[~2020-11-04 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 16:52 Alex Bennée [this message]
2020-11-09 11:40 ` [PATCH v2] docs: add some notes on the sbsa-ref machine Peter Maydell
2020-11-09 13:10 ` Peter Maydell
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=20201104165254.24822-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=graeme@nuviainc.com \
--cc=leif@nuviainc.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shashi.mallela@linaro.org \
/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).