qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Joel Stanley <joel@jms.id.au>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, qemu-arm@nongnu.org,
	Andrew Jeffery <andrew@aj.id.au>,
	Jim Mussared <jim.mussared@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] arm: Add nRF51 SoC and micro:bit machine
Date: Tue, 8 May 2018 13:08:44 +0100	[thread overview]
Message-ID: <20180508120844.GL19710@stefanha-x1.localdomain> (raw)
In-Reply-To: <20180503090532.3113-1-joel@jms.id.au>

[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]

On Thu, May 03, 2018 at 06:35:30PM +0930, Joel Stanley wrote:
> Hello,
> 
> This short series implements a minimal definition of the Nordic
> Semiconductor nRF51, a Cortex-M0 ARM SoC, and the BBC micro:bit, a
> machine that will use this SoC.
> 
> This work will serve as the base for our Google Summer of Code and
> Outreachy interns who will work on implementing a number of features on
> top of this base.
> 
> I've tested this with a microbit micropython firmware, and checked that
> it starts running by looking at it with gdb.
> 
> I chose to keep the nrf51 and the microbit seperate, to not confuse the
> peripherals that are on the microbit but are not part of the nrf51, and
> vice versa.
> 
> Please review!
> 
> Joel Stanley (2):
>   arm: Add Nordic Semiconductor nRF51 SoC
>   arm: Add BBC micro:bit machine
> 
>  default-configs/arm-softmmu.mak |   1 +
>  hw/arm/Makefile.objs            |   1 +
>  hw/arm/microbit.c               |  33 +++++++++++
>  hw/arm/nrf51_soc.c              | 101 ++++++++++++++++++++++++++++++++
>  include/hw/arm/nrf51_soc.h      |  31 ++++++++++
>  5 files changed, 167 insertions(+)
>  create mode 100644 hw/arm/microbit.c
>  create mode 100644 hw/arm/nrf51_soc.c
>  create mode 100644 include/hw/arm/nrf51_soc.h

Thanks for sending this!

Please add a MAINTAINERS file entry.  If you're up for it, I suggest
adding yourself for now.  Julia and Steffen could add themselves later,
depending on their willingness to stay involved after GSoC and Outreachy
end.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

      parent reply	other threads:[~2018-05-08 12:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-03  9:05 [Qemu-devel] [PATCH 0/2] arm: Add nRF51 SoC and micro:bit machine Joel Stanley
2018-05-03  9:05 ` [Qemu-devel] [PATCH 1/2] arm: Add Nordic Semiconductor nRF51 SoC Joel Stanley
2018-05-03  9:17   ` Peter Maydell
2018-05-08 12:01     ` Stefan Hajnoczi
2018-05-08 12:05   ` Stefan Hajnoczi
2018-05-03  9:05 ` [Qemu-devel] [PATCH 2/2] arm: Add BBC micro:bit machine Joel Stanley
2018-05-03  9:21   ` Peter Maydell
2018-05-03  9:14 ` [Qemu-devel] [PATCH 0/2] arm: Add nRF51 SoC and " no-reply
2018-05-03  9:14 ` no-reply
2018-05-03  9:16 ` no-reply
2018-05-03  9:24 ` Peter Maydell
2018-06-27 14:35   ` Joel Stanley
2018-05-08 12:08 ` 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=20180508120844.GL19710@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=jim.mussared@gmail.com \
    --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).