From: "Steffen Görtz" <contrib@steffen-goertz.de>
To: qemu-devel@nongnu.org
Cc: "Stefan Hajnoczi" <stefanha@gmail.com>,
"Joel Stanley" <joel@jms.id.au>,
"Jim Mussared" <jim@groklearning.com>,
"Julia Suvorova" <jusual@mail.ru>,
"Steffen Görtz" <contrib@steffen-goertz.de>
Subject: [Qemu-devel] [RFC 0/8] arm: Changes to Microbit Board and NRF51 SOC
Date: Wed, 27 Jun 2018 09:33:43 +0200 [thread overview]
Message-ID: <20180627073351.856-1-contrib@steffen-goertz.de> (raw)
This is a series of changes to the NRF51 SOC and the microbit board.
The changes can not be posted as patches as the nrf51 is not mergable
yet due to missing cortex-m0/armv6 support.
"arm: Add NRF51 random number generator peripheral" was already
posted to devel and is being discussed in <20180626104943.2756-1-contrib@steffen-goertz.de>
"arm: Add NRF51 SOC non-volatile memory controller" was already
posted to devel and is being discussed in
<20180626093204.27612-1-contrib@steffen-goertz.de>
Steffen Görtz (8):
arm: NRF51/Microbit Memory container and SOC variants
arm: NRF51 Add unimplemented device for MMIO
arm: NRF51 create UART in-place, error handling
arm: NRF51 Calculate peripheral id from base address
arm: Add NRF51 random number generator peripheral
arm: Add UICR/FICR handling to NRF51 SOC
arm: Add NRF51 SOC non-volatile memory controller
arm: Instantiate NVMC in NRF51.
hw/arm/microbit.c | 8 +-
hw/arm/nrf51_soc.c | 332 ++++++++++++++++++++++++++--------
hw/char/nrf51_uart.c | 10 +-
hw/misc/Makefile.objs | 1 +
hw/misc/nrf51_rng.c | 243 +++++++++++++++++++++++++
hw/nvram/Makefile.objs | 1 +
hw/nvram/nrf51_nvmc.c | 168 +++++++++++++++++
include/hw/arm/nrf51_soc.h | 38 +++-
include/hw/char/nrf51_uart.h | 26 +--
include/hw/misc/nrf51_rng.h | 73 ++++++++
include/hw/nvram/nrf51_nvmc.h | 51 ++++++
11 files changed, 845 insertions(+), 106 deletions(-)
create mode 100644 hw/misc/nrf51_rng.c
create mode 100644 hw/nvram/nrf51_nvmc.c
create mode 100644 include/hw/misc/nrf51_rng.h
create mode 100644 include/hw/nvram/nrf51_nvmc.h
--
2.17.1
next reply other threads:[~2018-06-27 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 7:33 Steffen Görtz [this message]
2018-06-27 7:33 ` [Qemu-devel] [RFC 1/8] arm: NRF51/Microbit Memory container and SOC variants Steffen Görtz
2018-06-27 9:53 ` Stefan Hajnoczi
2018-06-27 7:33 ` [Qemu-devel] [RFC 2/8] arm: NRF51 Add unimplemented device for MMIO Steffen Görtz
2018-06-27 7:33 ` [Qemu-devel] [RFC 3/8] arm: NRF51 create UART in-place, error handling Steffen Görtz
2018-06-27 7:33 ` [Qemu-devel] [RFC 4/8] arm: NRF51 Calculate peripheral id from base address Steffen Görtz
2018-06-27 7:33 ` [Qemu-devel] [RFC 5/8] arm: Add NRF51 random number generator peripheral Steffen Görtz
2018-07-05 16:51 ` Peter Maydell
2018-07-05 17:19 ` Steffen Görtz
2018-06-27 7:33 ` [Qemu-devel] [RFC 6/8] arm: Add UICR/FICR handling to NRF51 SOC Steffen Görtz
2018-06-27 9:57 ` Stefan Hajnoczi
2018-06-27 7:33 ` [Qemu-devel] [RFC 7/8] arm: Add NRF51 SOC non-volatile memory controller Steffen Görtz
2018-06-27 7:33 ` [Qemu-devel] [RFC 8/8] arm: Instantiate NVMC in NRF51 Steffen Görtz
2018-06-27 9:46 ` [Qemu-devel] [RFC 0/8] arm: Changes to Microbit Board and NRF51 SOC Stefan Hajnoczi
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=20180627073351.856-1-contrib@steffen-goertz.de \
--to=contrib@steffen-goertz.de \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=jusual@mail.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).