qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cole Robinson <crobinso@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, Paul Whalen <pwhalen@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hw/arm_boot.c: bump initrd address (again) to accommodate large kernels
Date: Mon, 22 Oct 2012 17:06:58 -0400	[thread overview]
Message-ID: <5085B572.4050100@redhat.com> (raw)
In-Reply-To: <CAFEAcA9dLBvumaQAydBVvM_XcnqT0=aLFvotsCb=aNhbw85eXA@mail.gmail.com>

On 10/07/2012 06:36 PM, Peter Maydell wrote:
> On 7 October 2012 23:27, Cole Robinson <crobinso@redhat.com> wrote:
>> From: Paul Whalen <pwhalen@redhat.com>
>>
>> Fedora ARM is generating kernels that exceed the hardcoded size limits:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=862766
>>
>> Bump the load address, as was previously done in 756ba3b
>>
>> Signed-off-by: Cole Robinson <crobinso@redhat.com>
>> ---
>>  hw/arm_boot.c | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/hw/arm_boot.c b/hw/arm_boot.c
>> index a6e9143..3cabb71 100644
>> --- a/hw/arm_boot.c
>> +++ b/hw/arm_boot.c
>> @@ -18,7 +18,7 @@
>>
>>  #define KERNEL_ARGS_ADDR 0x100
>>  #define KERNEL_LOAD_ADDR 0x00010000
>> -#define INITRD_LOAD_ADDR 0x00d00000
>> +#define INITRD_LOAD_ADDR 0x01d00000
> 
> This makes me sad but I still have no idea what we could
> do that would be better than this...
> 

Hi Peter,

I agree it's unfortunate, but in the absence of a better solution, could this
patch be applied?

Thanks,
Cole

  parent reply	other threads:[~2012-10-22 21:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 22:27 [Qemu-devel] [PATCH] hw/arm_boot.c: bump initrd address (again) to accommodate large kernels Cole Robinson
2012-10-07 22:36 ` Peter Maydell
2012-10-08  0:09   ` Peter Crosthwaite
2012-10-08  7:34     ` Peter Maydell
2012-10-22 21:06   ` Cole Robinson [this message]
2012-10-26  8:48     ` Peter Maydell
2012-10-26 10:32       ` 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=5085B572.4050100@redhat.com \
    --to=crobinso@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=pwhalen@redhat.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).