qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Joel Stanley <joel@jms.id.au>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>, Andrew Jeffery <andrew@aj.id.au>,
	Jim Mussared <jim.mussared@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] arm: Add Nordic Semiconductor nRF51 SoC
Date: Tue, 8 May 2018 13:01:46 +0100	[thread overview]
Message-ID: <20180508120146.GJ19710@stefanha-x1.localdomain> (raw)
In-Reply-To: <CAFEAcA_4EiWXdSNdbiEWO_Q2Sac7qzNduhyWVNwW-crc5=w_nA@mail.gmail.com>

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

On Thu, May 03, 2018 at 10:17:51AM +0100, Peter Maydell wrote:
> On 3 May 2018 at 10:05, Joel Stanley <joel@jms.id.au> wrote:
> I'm a bit reluctant to take these patches until we have an
> actual cortex-m0 model, because anything we take into QEMU
> master is then something we have to support. My rule of thumb
> is that it's ok to have board models that are missing
> functionality, but we should avoid models that have wrong
> functionality (like the wrong CPU) where we can.

For the purposes of the micro:bit emulation project we're not sure yet
how far the M3 model will take us.  The M0 is a subset of the M3 and we
intend to use it during bring-up...and even afterwards if software runs
okay with it.

If you don't want to merge this into qemu.git/master we'll have to
maintain a "microbit" project branch on which Julia and Steffen (and
others) can work during the Google Summer of Code and Outreachy period.

My concern about keeping it out-of-tree is that we want Julia and
Steffen to participate in the upstream community and get their patches
merged.  Anything out-of-tree could still be rejected at a later date
:(.

Can we mark the machine type "experimental" and merge it in
qemu.git/master with the understanding that it may be removed if there
is no active development?

Stefan

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

  reply	other threads:[~2018-05-08 12:02 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 [this message]
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

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=20180508120146.GJ19710@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).