qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <marcin.krzeminski@nokia.com>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org, peter.maydell@linaro.org,
	rfsw-patches@mlist.nokia.com
Subject: [Qemu-devel] [RFC 0/3] MultiCPU changes
Date: Fri, 16 Dec 2016 14:22:36 +0100	[thread overview]
Message-ID: <1481894559-13974-1-git-send-email-marcin.krzeminski@nokia.com> (raw)

From: Marcin Krzeminski <marcin.krzeminski@nokia.com>

Those are changes that I made to create SoC model with 2xCortexA9
and Cortex-M3. Generally all are done to allow move work further,
not to upstreaming (especially patch 3). I would like to start
discossion if those modification could be upstreamed.

Marcin Krzeminski (3):
  nvic: Add CPU numebr property
  ARM: boot: Add option to skip FDT memory node update
  exec: Allow to change Address Space from board level

 exec.c                |  8 ++++++++
 hw/arm/boot.c         | 29 ++++++++++++++++-------------
 hw/intc/armv7m_nvic.c | 24 ++++++++++++++++++------
 include/hw/arm/arm.h  |  5 +++++
 include/qom/cpu.h     |  1 +
 5 files changed, 48 insertions(+), 19 deletions(-)

-- 
2.7.4

             reply	other threads:[~2016-12-16 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 13:22 marcin.krzeminski [this message]
2016-12-16 13:22 ` [Qemu-devel] [RFC 1/3] nvic: Add CPU numebr property marcin.krzeminski
2016-12-16 14:18   ` Peter Maydell
2016-12-30 10:13     ` [Qemu-devel] Odp.: " Krzeminski, Marcin (Nokia - PL/Wroclaw)
2016-12-16 13:22 ` [Qemu-devel] [RFC 2/3] ARM: boot: Add option to skip FDT memory node update marcin.krzeminski
2016-12-16 13:22 ` [Qemu-devel] [RFC 3/3] exec: Allow to change Address Space from board level marcin.krzeminski
2016-12-16 14:07 ` [Qemu-devel] [RFC 0/3] MultiCPU changes no-reply

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=1481894559-13974-1-git-send-email-marcin.krzeminski@nokia.com \
    --to=marcin.krzeminski@nokia.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rfsw-patches@mlist.nokia.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).