All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Joel Stanley <joel@jms.id.au>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>, Andrew Jeffery <andrew@aj.id.au>,
	Jim Mussared <jim.mussared@gmail.com>,
	Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] arm: Add nRF51 SoC and micro:bit machine
Date: Thu, 3 May 2018 10:24:22 +0100	[thread overview]
Message-ID: <CAFEAcA_dP5QRrZoX8P67xjNVpv7QssnMP9yd5sXqAEu2tQ5Lww@mail.gmail.com> (raw)
In-Reply-To: <20180503090532.3113-1-joel@jms.id.au>

On 3 May 2018 at 10:05, Joel Stanley <joel@jms.id.au> 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!

Hi; thanks for this patchset. I've done some quick overview review.
It looks broadly ok but there are some details which don't follow
our current preferences/practices for board and SoC models (we have
a lot of legacy code in the codebase that follows older approaches
or is just buggy, so it can be hard to get those right. The mps2
boards and the iotkit SoC are the most recent I've written so
probably not a bad pattern to look at.)
We should probably not put this into master until we've got at least
the cortex-m0 model, though.

thanks
-- PMM

  parent reply	other threads:[~2018-05-03  9:24 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 [this message]
2018-06-27 14:35   ` Joel Stanley
2018-05-08 12:08 ` 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=CAFEAcA_dP5QRrZoX8P67xjNVpv7QssnMP9yd5sXqAEu2tQ5Lww@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=andrew@aj.id.au \
    --cc=jim.mussared@gmail.com \
    --cc=joel@jms.id.au \
    --cc=qemu-arm@nongnu.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.