All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Davidsaver <mdavidsaver@gmail.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-arm] Any progress with the Cortex-M4 emulation?
Date: Wed, 6 Apr 2016 20:46:30 -0400	[thread overview]
Message-ID: <5705ADE6.3070502@gmail.com> (raw)
In-Reply-To: <D2CD166F-5E77-4BA1-B468-64296F379D05@livius.net>

On 04/06/2016 06:23 PM, Liviu Ionescu wrote:
> 
>> On 07 Apr 2016, at 01:04, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> ... Somebody needs to do the necessary work to fix the
>> code review issues. ...
> 
> in this case I'll probably wait for this process to be completed and reevaluate the situation by then.

Liviu,

I haven't had time to complete a revision of my patch set so far this year.  I've been busy with other work (good for me, bad for qemu), and don't see this situation changing for an least the next two months.  It sounds like you have time and inclination to do part of what I've started.  I hope my having done half of a too big job won't keep you from finishing part of it.

If you decide to work on this problem, please don't hesitate to appropriate, or ignore, what I've done so far.

For what it's worth, I did start another revision back in February.  It does include the change Peter requested to the storage of priorities wrt. prigroup, but doesn't break up the big "rewrite NVIC" patch.

https://github.com/mdavidsaver/qemu/tree/fixirq2

Separately, I have a set of target test programs which I can run both with qemu and a real board.  They mostly agree.  Aside from test8.c (MPU) they might be of interest.

https://github.com/mdavidsaver/baremetal/tree/qemutest



Michael

WARNING: multiple messages have this Message-ID (diff)
From: Michael Davidsaver <mdavidsaver@gmail.com>
To: Liviu Ionescu <ilg@livius.net>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Any progress with the Cortex-M4 emulation?
Date: Wed, 6 Apr 2016 20:46:30 -0400	[thread overview]
Message-ID: <5705ADE6.3070502@gmail.com> (raw)
In-Reply-To: <D2CD166F-5E77-4BA1-B468-64296F379D05@livius.net>

On 04/06/2016 06:23 PM, Liviu Ionescu wrote:
> 
>> On 07 Apr 2016, at 01:04, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> ... Somebody needs to do the necessary work to fix the
>> code review issues. ...
> 
> in this case I'll probably wait for this process to be completed and reevaluate the situation by then.

Liviu,

I haven't had time to complete a revision of my patch set so far this year.  I've been busy with other work (good for me, bad for qemu), and don't see this situation changing for an least the next two months.  It sounds like you have time and inclination to do part of what I've started.  I hope my having done half of a too big job won't keep you from finishing part of it.

If you decide to work on this problem, please don't hesitate to appropriate, or ignore, what I've done so far.

For what it's worth, I did start another revision back in February.  It does include the change Peter requested to the storage of priorities wrt. prigroup, but doesn't break up the big "rewrite NVIC" patch.

https://github.com/mdavidsaver/qemu/tree/fixirq2

Separately, I have a set of target test programs which I can run both with qemu and a real board.  They mostly agree.  Aside from test8.c (MPU) they might be of interest.

https://github.com/mdavidsaver/baremetal/tree/qemutest



Michael

  reply	other threads:[~2016-04-07  0:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 21:57 [Qemu-devel] Any progress with the Cortex-M4 emulation? Liviu Ionescu
2016-04-06 12:02 ` Peter Maydell
2016-04-06 12:52   ` Liviu Ionescu
2016-04-06 14:42     ` Peter Maydell
2016-04-06 21:54       ` Liviu Ionescu
2016-04-06 22:04         ` Peter Maydell
2016-04-06 22:23           ` Liviu Ionescu
2016-04-07  0:46             ` Michael Davidsaver [this message]
2016-04-07  0:46               ` Michael Davidsaver
2016-04-07  7:04               ` Liviu Ionescu

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=5705ADE6.3070502@gmail.com \
    --to=mdavidsaver@gmail.com \
    --cc=ilg@livius.net \
    --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 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.