From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Steffen Görtz" <contrib@steffen-goertz.de>,
qemu-arm@nongnu.org, "Joel Stanley" <joel@jms.id.au>
Subject: Re: [PATCH 2/4] hw/arm/nrf51_soc: Mark some peripherals as unimplemented
Date: Mon, 4 May 2020 10:13:40 -0700 [thread overview]
Message-ID: <a5278614-a9b5-f41a-53ea-f89331d6a3ca@linaro.org> (raw)
In-Reply-To: <20200504072822.18799-3-f4bug@amsat.org>
On 5/4/20 12:28 AM, Philippe Mathieu-Daudé wrote:
> Map some peripherals used by Zephyr Project:
>
> https://github.com/zephyrproject-rtos/zephyr/blob/zephyr-v2.2.0/dts/arm/nordic/nrf51822.dtsi
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
> include/hw/arm/nrf51.h | 4 ++++
> hw/arm/nrf51_soc.c | 11 +++++++++++
> 2 files changed, 15 insertions(+)
There's a fair few more devices listed in the manual, and not all of the ones
that you add here are referenced in the dts files. So what criteria are you
using to choose?
Perhaps it would be easier to add them all?
r~
next prev parent reply other threads:[~2020-05-04 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 7:28 [PATCH 0/4] hw/arm/nrf51: Extend tracing Philippe Mathieu-Daudé
2020-05-04 7:28 ` [PATCH 1/4] hw/arm/nrf51: Add NRF51_PERIPHERAL_SIZE definition Philippe Mathieu-Daudé
2020-05-04 17:02 ` Richard Henderson
2020-05-04 7:28 ` [PATCH 2/4] hw/arm/nrf51_soc: Mark some peripherals as unimplemented Philippe Mathieu-Daudé
2020-05-04 17:13 ` Richard Henderson [this message]
2020-05-04 17:43 ` Philippe Mathieu-Daudé
2020-05-04 7:28 ` [PATCH 3/4] hw/timer/nrf51_timer: Display timer ID in trace events Philippe Mathieu-Daudé
2020-05-04 17:15 ` Richard Henderson
2020-05-04 7:28 ` [PATCH 4/4] hw/timer/nrf51_timer: Add trace event of counter value update Philippe Mathieu-Daudé
2020-05-04 17:16 ` Richard Henderson
2020-05-11 10:45 ` [PATCH 0/4] hw/arm/nrf51: Extend tracing Peter Maydell
2020-05-11 12:23 ` 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=a5278614-a9b5-f41a-53ea-f89331d6a3ca@linaro.org \
--to=richard.henderson@linaro.org \
--cc=contrib@steffen-goertz.de \
--cc=f4bug@amsat.org \
--cc=joel@jms.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).