qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 3/6] hw/arm_boot.c: Check for RAM sizes exceeding ATAGS capacity
Date: Fri, 6 Jul 2012 08:25:55 +0100	[thread overview]
Message-ID: <CAFEAcA8FjahxFKaXL5WUQcSXs8bPwHowEbkmt1dtsw77Xn0tAw@mail.gmail.com> (raw)
In-Reply-To: <CAEgOgz6q9Qg8JBzHbVpZ2n_FqgJCqnoKLLF+BF2-4Z778m2VKA@mail.gmail.com>

On 6 July 2012 03:05, Peter Crosthwaite <peter.crosthwaite@petalogix.com> wrote:
> On Fri, Jul 6, 2012 at 3:00 AM, Peter Maydell <peter.maydell@linaro.org> wrote:
>> +            if (info->ram_size >= (1ULL << 32)) {
>> +                fprintf(stderr, "qemu: RAM size must be less than 4GB to boot"
>> +                        " Linux kernel without device tree\n");
>
> Error message is a bit weird. Shouldnt it be "RAM size must be less
> than 4GB to boot Linux kernel with ATAG command line". DTB shouldnt be
> the only way to boot with >4GB.

I'm trying to steer the user toward the way to solve their problem,
which is to use a device tree. I expect less than 1 QEMU user in 100
has any idea what ATAGS are.

> DTB shouldnt be the only way to boot with >4GB.

I'm not sure what you mean here -- we have two boot methods and
only DTB handles large RAM sizes. Or do you mean machines with eg
flash where you could boot by putting a bootloader in flash?

-- PMM

  reply	other threads:[~2012-07-06  7:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-05 17:00 [Qemu-devel] [PATCH 0/6] arm_boot/vexpress-a15: Support >4GB of RAM Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 1/6] hw/arm_boot.c: Make ram_size a target_phys_addr_t Peter Maydell
2012-07-06  1:58   ` Peter Crosthwaite
2012-07-06 13:48   ` Andreas Färber
2012-07-06 13:54     ` Alexander Graf
2012-07-06 14:02       ` Andreas Färber
2012-07-06 14:04     ` Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 2/6] hw/arm_boot.c: Consistently use ram_size from arm_boot_info struct Peter Maydell
2012-07-06  2:00   ` Peter Crosthwaite
2012-07-06  7:23     ` Peter Maydell
2012-07-05 17:00 ` [Qemu-devel] [PATCH 3/6] hw/arm_boot.c: Check for RAM sizes exceeding ATAGS capacity Peter Maydell
2012-07-06  2:05   ` Peter Crosthwaite
2012-07-06  7:25     ` Peter Maydell [this message]
2012-07-05 17:00 ` [Qemu-devel] [PATCH 4/6] device_tree: Add support for reading device tree properties Peter Maydell
2012-07-06  1:56   ` Peter Crosthwaite
2012-07-06  7:18     ` Peter Maydell
2012-07-06 15:34     ` Peter Maydell
2012-07-06 15:44       ` Peter Maydell
2012-07-10  6:54       ` Peter Crosthwaite
2012-07-10  7:52         ` Peter Maydell
2012-07-10 13:03         ` Peter Maydell
2012-07-13  1:24   ` Peter Crosthwaite
2012-07-05 17:00 ` [Qemu-devel] [PATCH 5/6] hw/arm_boot.c: Support DTBs which use 64 bit addresses Peter Maydell
2012-07-05 18:53   ` Blue Swirl
2012-07-05 19:26     ` Peter Maydell
2012-07-06  2:19   ` Peter Crosthwaite
2012-07-05 17:00 ` [Qemu-devel] [PATCH 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=CAFEAcA8FjahxFKaXL5WUQcSXs8bPwHowEbkmt1dtsw77Xn0tAw@mail.gmail.com \
    --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).