From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Kumar Gala" <kumar.gala@linaro.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: [PATCH v2 0/3] target/arm: New boards mps2-an386, mps2-an500
Date: Thu, 3 Sep 2020 21:20:45 +0100 [thread overview]
Message-ID: <20200903202048.15370-1-peter.maydell@linaro.org> (raw)
This series adds two new board models in the mps2 family.
The AN386 is identical to the AN385 but with a Cortex-M4.
The AN500 is a Cortex-M7 image which is almost the same as
the AN385 but has a few minor differences, most notably the
base address of the PSRAM and of the ethernet controller.
The AN500 is interesting because we don't currently have any
boards in-tree which use the Cortex-M7.
Changes since v1:
* patch 1 now also updates the docs to mention the new board
* new patch 2 defines the mps2-an500 board
* new patch 3 makes some minor cleanup to the docs for these boards
Richard, Philippe: I kept your reviewed-by tags on patch 1
because the only change was the trivial docs addition and
there were no code changes.
thanks
-- PMM
Peter Maydell (3):
hw/arm/mps2: New board model mps2-an386
hw/arm/mps2: New board model mps2-an500
docs/system/arm/mps2.rst: Make board list consistent
docs/system/arm/mps2.rst | 20 +++++----
hw/arm/mps2.c | 97 ++++++++++++++++++++++++++++++++++------
2 files changed, 95 insertions(+), 22 deletions(-)
--
2.20.1
next reply other threads:[~2020-09-03 20:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 20:20 Peter Maydell [this message]
2020-09-03 20:20 ` [PATCH v2 1/3] hw/arm/mps2: New board model mps2-an386 Peter Maydell
2020-09-03 20:20 ` [PATCH v2 2/3] hw/arm/mps2: New board model mps2-an500 Peter Maydell
2020-09-04 13:38 ` Philippe Mathieu-Daudé
2020-09-10 20:06 ` Peter Maydell
2020-09-03 20:20 ` [PATCH v2 3/3] docs/system/arm/mps2.rst: Make board list consistent Peter Maydell
2020-09-04 13:38 ` Philippe Mathieu-Daudé
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=20200903202048.15370-1-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=f4bug@amsat.org \
--cc=kumar.gala@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@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).