From: Liviu Ionescu <ilg@livius.net>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Julia Suvorova" <jusual@mail.ru>,
qemu-devel <qemu-devel@nongnu.org>,
"Joel Stanley" <joel@jms.id.au>,
"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: Thu, 7 Jun 2018 06:46:26 -0400 [thread overview]
Message-ID: <CAG7hfcLE7jJgsAmmOD0TQSN42kPg8ixJ_RQnpmZk-NNJ2MuZ_Q@mail.gmail.com> (raw)
In-Reply-To: <20180607103628.GE19032@stefanha-x1.localdomain>
On 7 June 2018 at 13:36:30, Stefan Hajnoczi (stefanha@gmail.com) wrote:
> If you do want to upstream the code you linked, please let us know
> the
> details of how you want to do it and how long it might take. Maybe
> there is a way to work together on it...
yes, I considered this, but I do not have a schedule yet, probably in Q4.
I first plan to upgrade from 2.8 and only later to re-evaluate the
entire project, to bring it closer to the upstream version.
the main change I envision is to untangle the Cortex-M code from the
current ARM code. maybe now the status is better, but when I did my
changes I had lots of problems.
regards,
Liviu
next prev parent reply other threads:[~2018-06-07 10:46 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
2018-06-04 11:15 ` Liviu Ionescu
2018-06-07 10:36 ` Stefan Hajnoczi
2018-06-07 10:46 ` Liviu Ionescu [this message]
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=CAG7hfcLE7jJgsAmmOD0TQSN42kPg8ixJ_RQnpmZk-NNJ2MuZ_Q@mail.gmail.com \
--to=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 \
--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 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).