From: John Rigby <john.rigby@linaro.org>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
John Rigby <john.rigby@linaro.org>
Subject: [Qemu-devel] [PATCH v3 0/2] Add mach-virt platform
Date: Fri, 10 May 2013 00:58:35 -0600 [thread overview]
Message-ID: <1368169118-9528-1-git-send-email-john.rigby@linaro.org> (raw)
Modify arm fdt handling so boards can provide a blob
rather than requiring one on command line.
Allow dumping of fdt blob as ppc e500 already does.
Next add mach-virt platform that creates fdt blob from scratch
describing its minimal hw which is a pl011 uart and a sp804 timer.
Tested on amd64 host with full system emulation and also using kvm
on an arndale board
v2 changes:
- remove bogus cruft from mach-virt.c that was leftover
from checkpatch fixing
v3 changes:
- split first patch into two
- rename from mach-virt to virt
- collect scattered constants into a machine info structure
- put qemu device creation and fdt nod creation near one another to make
it easier to keep them in sync
- use CONFIG_KVM and kvm_enabled() to differentiate between tcg and kvm
dependent code
- move memory to 0x0 and io up to 0xfff00000
John Rigby (3):
ARM: Allow boards to provide an fdt blob
ARM: Allow dumping of device tree
ARM: Add mach-virt platform
hw/arm/Makefile.objs | 2 +-
hw/arm/boot.c | 31 ++--
hw/arm/virt.c | 434 +++++++++++++++++++++++++++++++++++++++++++++++++++
include/hw/arm/arm.h | 6 +
4 files changed, 461 insertions(+), 12 deletions(-)
create mode 100644 hw/arm/virt.c
--
1.8.2.2
next reply other threads:[~2013-05-10 7:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 6:58 John Rigby [this message]
2013-05-10 6:58 ` [Qemu-devel] [PATCH v3 1/3] ARM: Allow boards to provide an fdt blob John Rigby
2013-06-13 18:49 ` Peter Maydell
2013-05-10 6:58 ` [Qemu-devel] [PATCH v3 2/3] ARM: Allow dumping of device tree John Rigby
2013-06-13 17:53 ` Peter Maydell
2013-05-10 6:58 ` [Qemu-devel] [PATCH v3 3/3] ARM: Add mach-virt platform John Rigby
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=1368169118-9528-1-git-send-email-john.rigby@linaro.org \
--to=john.rigby@linaro.org \
--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 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).