From: Peter Maydell <peter.maydell@linaro.org>
To: Rob Herring <robherring2@gmail.com>
Cc: Rob Herring <rob.herring@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] hw/arm/boot: get AArch64 kernel Image load offset from Image file
Date: Fri, 16 May 2014 11:02:43 +0100 [thread overview]
Message-ID: <CAFEAcA9nv+vdzekd2TKQGjwuHaLht4z_h5Y3pYW-qP6HtQ21ag@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-VKuCDRC8FhcYAcPOHVSV9vQs_5_j=Qi7E90-W-iRf6g@mail.gmail.com>
On 15 May 2014 19:54, Peter Maydell <peter.maydell@linaro.org> wrote:
> One suggestion I've seen for dealing with this is that
> the semantics become such that bootloader code does this:
> if (hdr.res[0] == 0) {
> /* legacy broken kernels, always this address */
> return 0x80000;
> } else {
> return le64_to_cpu(hdr.text_offset);
> }
> (ie hdr.res[0] becomes an indicator of whether the kernel
> is consistent about what text_offset means; if it's zero
> this is an old legacy kernel, which conveniently always uses
> the same fixed address.)
>
> We may need to wait for the kernel patches to appear
> (and the decision about how bootloaders should interpret
> the text_offset field to be resolved) before we can change
> our bootloader code...
Mark Rutland has now posted those kernel patches:
http://archive.arm.linux.org.uk/lurker/message/20140516.095035.4bf1f2bd.en.html
-- PMM
prev parent reply other threads:[~2014-05-16 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 19:30 [Qemu-devel] [PATCH] hw/arm/boot: get AArch64 kernel Image load offset from Image file Rob Herring
2014-05-15 18:54 ` Peter Maydell
2014-05-16 10:02 ` Peter Maydell [this message]
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=CAFEAcA9nv+vdzekd2TKQGjwuHaLht4z_h5Y3pYW-qP6HtQ21ag@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rob.herring@linaro.org \
--cc=robherring2@gmail.com \
/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).