From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Peter Crosthwaite <peter.crosthwaite@petalogix.com>, patches@linaro.org
Subject: [Qemu-devel] [PATCH v2 0/6] arm_boot/vexpress-a15: Support >4GB of RAM
Date: Mon, 16 Jul 2012 14:24:10 +0100 [thread overview]
Message-ID: <1342445056-9129-1-git-send-email-peter.maydell@linaro.org> (raw)
From: Peter Maydell <petmay01@cam-vm-266.(none)>
This patchset adds support for booting with >4GB of RAM on the
Versatile Express Cortex-A15 model. There are some caveats:
* you need an LPAE A15 kernel
* you need to be booting with device tree
* your device tree blob needs to specify #address-cells and
#size-cells as 2 (so addresses and sizes are 64 bit), which
means you'll need to tweak the stock kernel dtb
[the dtb files for the vexpress boards should be getting this change
soon, although I'm not sure when it will hit upstream]
* you need a minor kernel patch which stops the kernel throwing away
the high 32 bits of the RAM size:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=7465/1
[hopefully coming soon to an upstream kernel near you]
* you need a 64 bit host, obviously
Changes v1->v2:
* now based on master, no other dependencies
* use uint64_t rather than target_phys_addr_t for sizes
* removed debug tracing
* tweaked "ram size too big for ATAGS boot" message
NB that (following discussion with Peter C) the device_tree.c
patch is unchanged from v1.
Peter Maydell (6):
hw/arm_boot.c: Make ram_size a uint64_t
hw/arm_boot.c: Consistently use ram_size from arm_boot_info struct
hw/arm_boot.c: Check for RAM sizes exceeding ATAGS capacity
device_tree: Add support for reading device tree properties
hw/arm_boot.c: Support DTBs which use 64 bit addresses
hw/vexpress.c: Allow >4GB of RAM for Cortex-A15 daughterboard
device_tree.c | 30 ++++++++++++++++++++++++++++++
device_tree.h | 4 ++++
hw/arm-misc.h | 2 +-
hw/arm_boot.c | 46 +++++++++++++++++++++++++++++++++++++++++-----
hw/vexpress.c | 13 ++++++++++---
5 files changed, 86 insertions(+), 9 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-07-16 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 13:24 Peter Maydell [this message]
2012-07-16 13:24 ` [Qemu-devel] [PATCH v2 1/6] hw/arm_boot.c: Make ram_size a uint64_t Peter Maydell
2012-07-18 12:25 ` Peter Crosthwaite
2012-07-16 13:24 ` [Qemu-devel] [PATCH v2 2/6] hw/arm_boot.c: Consistently use ram_size from arm_boot_info struct Peter Maydell
2012-07-16 13:24 ` [Qemu-devel] [PATCH v2 3/6] hw/arm_boot.c: Check for RAM sizes exceeding ATAGS capacity Peter Maydell
2012-07-18 12:28 ` Peter Crosthwaite
2012-07-16 13:24 ` [Qemu-devel] [PATCH v2 4/6] device_tree: Add support for reading device tree properties Peter Maydell
2012-07-18 12:30 ` Peter Crosthwaite
2012-07-16 13:24 ` [Qemu-devel] [PATCH v2 5/6] hw/arm_boot.c: Support DTBs which use 64 bit addresses Peter Maydell
2012-07-16 13:24 ` [Qemu-devel] [PATCH v2 6/6] hw/vexpress.c: Allow >4GB of RAM for Cortex-A15 daughterboard Peter Maydell
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=1342445056-9129-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=patches@linaro.org \
--cc=peter.crosthwaite@petalogix.com \
--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).