All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: "Julia Suvorova" <jusual@mail.ru>,
	"Joel Stanley" <joel@jms.id.au>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Steffen Görtz" <mail@steffen-goertz.de>,
	"Jim Mussared" <jim@groklearning.com>
Subject: Re: [Qemu-devel] Cortex M0 emulation tasks
Date: Mon, 4 Jun 2018 12:10:07 +0100	[thread overview]
Message-ID: <CAJSP0QW4dDpifDJgyuLKo3Ar53OGwUMP16e++HnDe69NA3-Mmw@mail.gmail.com> (raw)
In-Reply-To: <CAG7hfcJxiPYou5dNaWcL8p9uQxHUX1Qa7PDaku_z80Qx-S=yGg@mail.gmail.com>

On Sun, Jun 3, 2018 at 2:14 PM, Liviu Ionescu <ilg@livius.net> wrote:
> On 2 June 2018 at 17:15:15, Stefan Hajnoczi (stefanha@gmail.com) wrote:
>
>> > I have put together a basic Cortex M0 ARMv6-M CPU that can serve
>> as
>> the basis for this work. Please see the RFC patches that I've sent
>> separately.
>
> you can also take a look at the Cortex-M implementation in the GNU MCU
> Eclipse QEMU.
>
> https://gnu-mcu-eclipse.github.io/qemu/
>
> it is a bit old now; a refresh is planned, but no date is set yet.

Thanks for mentioning it.

What is the status of the Cortex M0 in that source tree?  Is it complete?

Thanks,
Stefan

  reply	other threads:[~2018-06-04 11:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 14:26 [Qemu-devel] Cortex M0 emulation tasks Stefan Hajnoczi
2018-05-29 18:09 ` Peter Maydell
2018-06-01 12:22   ` Stefan Hajnoczi
2018-06-02 14:13 ` Stefan Hajnoczi
2018-06-03 13:14   ` Liviu Ionescu
2018-06-04 11:10     ` Stefan Hajnoczi [this message]
2018-06-04 11:15       ` Liviu Ionescu
2018-06-07 10:36         ` Stefan Hajnoczi
2018-06-07 10:46           ` Liviu Ionescu
2018-06-08  7:53             ` Stefan Hajnoczi
2018-06-07 10:42         ` Stefan Hajnoczi
2018-06-08 15:06 ` 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=CAJSP0QW4dDpifDJgyuLKo3Ar53OGwUMP16e++HnDe69NA3-Mmw@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=ilg@livius.net \
    --cc=jim@groklearning.com \
    --cc=joel@jms.id.au \
    --cc=jusual@mail.ru \
    --cc=mail@steffen-goertz.de \
    --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 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.