From: Daniel Lezcano <daniel.lezcano@free.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [rfc 0/3] arm : dynamically choose initrd load address
Date: Mon, 6 Sep 2010 16:12:50 +0200 [thread overview]
Message-ID: <1283782373-4797-1-git-send-email-daniel.lezcano@free.fr> (raw)
Hi all,
after compiling my kernel on the arm architecture I was not able to
start it because qemu was segfaulting or going to an infinite loop.
After google'ing I found on launchpad the bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/524893
Following the indications, I rebuilt qemu with an higher initrd load
address and the kernel booted correctly.
I am trying to make the things easier and/or to fail gracefully with
patchset but I am not familiar with the ARM architecture neither qemu
internals, so may be I am totally wrong :)
The first patch raise an error if there is an overlapping error.
But the two next patches makes to compute automatically an address
for initrd to loaded.
Daniel Lezcano (3):
arm : raise an error if the kernel size will overlap the initrd
arm : factor out set_kernel_args[_old]
arm : make initrd load address dynamic
hw/arm-misc.h | 1 +
hw/arm_boot.c | 40 +++++++++++++++++++---------------------
2 files changed, 20 insertions(+), 21 deletions(-)
next reply other threads:[~2010-09-06 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 14:12 Daniel Lezcano [this message]
2010-09-06 14:12 ` [Qemu-devel] [rfc 1/3] arm : raise an error if the kernel size will overlap the initrd Daniel Lezcano
2010-09-06 14:12 ` [Qemu-devel] [rfc 2/3] arm : factor out set_kernel_args[_old] Daniel Lezcano
2010-09-06 14:12 ` [Qemu-devel] [rfc 3/3] arm : make initrd load address dynamic Daniel Lezcano
2010-09-08 11:47 ` [Qemu-devel] [rfc 0/3] arm : dynamically choose initrd load address Daniel Lezcano
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=1283782373-4797-1-git-send-email-daniel.lezcano@free.fr \
--to=daniel.lezcano@free.fr \
--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).