From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Steffen Görtz" <contrib@steffen-goertz.de>
Cc: qemu-devel@nongnu.org, Joel Stanley <joel@jms.id.au>,
Jim Mussared <jim@groklearning.com>,
Julia Suvorova <jusual@mail.ru>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [RFC v3 0/2] Add NRF51 SOC non-volatile memory controller
Date: Wed, 18 Jul 2018 14:20:46 +0100 [thread overview]
Message-ID: <20180718132046.GJ21825@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180712101219.32707-1-contrib@steffen-goertz.de>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
On Thu, Jul 12, 2018 at 12:12:17PM +0200, Steffen Görtz wrote:
> Add some non-volatile memories and a non-volatile
> memory controller for the nRF51.
> Furthermore, a testsuite for the bbc:microbit and
> nrf51 soc was added.
>
> Examination of the real device showed that
> NVMs remained unchanged when the write/erase enabled
> bits are not set in the controller, so we can
> safely ignore all writes.
> More: https://github.com/douzepouze/gsoc18-qemu/blob/master/notes.md#test-nvmc-behavior-out-of-micropython-repl
>
> The CODE/FLASH NVM is not currently included in this
> peripheral. It is hosted in the SOC and must be read-only
> to provide an accurate model.
>
> Steffen Görtz (2):
> arm: Add NRF51 SOC non-volatile memory controller
> tests: Add bbc:microbit / nRF51 test suite
Please include a changelog in the cover letter so that it's clear what
has changed in this revision.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2018-07-18 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 10:12 [Qemu-devel] [RFC v3 0/2] Add NRF51 SOC non-volatile memory controller Steffen Görtz
2018-07-12 10:12 ` [Qemu-devel] [RFC v3 1/2] arm: " Steffen Görtz
2018-07-18 14:18 ` Stefan Hajnoczi
2018-07-12 10:12 ` [Qemu-devel] [RFC v3 2/2] tests: Add bbc:microbit / nRF51 test suite Steffen Görtz
2018-07-18 14:19 ` Stefan Hajnoczi
2018-07-18 13:20 ` Stefan Hajnoczi [this message]
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=20180718132046.GJ21825@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=contrib@steffen-goertz.de \
--cc=jim@groklearning.com \
--cc=joel@jms.id.au \
--cc=jusual@mail.ru \
--cc=peter.maydell@linaro.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).