From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christopher Covington <cov@codeaurora.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Daniel Thompson <daniel.thompson@linaro.org>,
Joel Fernandes <joelf@ti.com>,
linux-arm-msm@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
QEMU Developers <qemu-devel@nongnu.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>
Subject: Re: Change of TEXT_OFFSET for multi_v7_defconfig
Date: Wed, 16 Apr 2014 23:34:54 +0100 [thread overview]
Message-ID: <20140416223454.GN24070@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAFEAcA9bqdHvFyGz_mhdU9=rPYaSc2h8Syccv3OEqH8FRhf=dA@mail.gmail.com>
On Wed, Apr 16, 2014 at 10:36:11PM +0100, Peter Maydell wrote:
> On 16 April 2014 22:08, Christopher Covington <cov@codeaurora.org> wrote:
> > On 04/16/2014 03:14 PM, Nicolas Pitre wrote:
> >> But both QEMU and the boot-wrapper should deal with zImage. That's the
> >> only image format with documented load offset is guaranteed not to
> >> change i.e. it can be loaded at about any offset as zImage knows how to
> >> relocate itself as needed. There is nowhere a guarantee that
> >> TEXT_OFFSET can't change.
> >
> > QEMU definitely does support zImage and I believe it's promoted as the main
> > boot method.
>
> Yes; we also support uImage. The code nominally handling Image
> actually currently loads at 0x10000, so the set of people who actually
> try to use it is obviously not very large :-)
For ARM, that means precisely zero users without modification of that.
We've never supported an offset of 0x10000 in mainline kernels.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
next prev parent reply other threads:[~2014-04-16 22:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 10:44 Change of TEXT_OFFSET for multi_v7_defconfig Daniel Thompson
2014-04-15 17:53 ` Stephen Boyd
2014-04-16 16:18 ` Christopher Covington
2014-04-16 19:14 ` Nicolas Pitre
2014-04-16 21:08 ` Christopher Covington
2014-04-16 21:36 ` Peter Maydell
2014-04-16 22:34 ` Russell King - ARM Linux [this message]
2014-04-16 22:33 ` Russell King - ARM Linux
2014-04-16 23:21 ` Nicolas Pitre
2014-04-17 18:33 ` Christopher Covington
2014-04-17 19:48 ` Nicolas Pitre
2014-04-17 20:49 ` Christopher Covington
2014-04-17 20:54 ` Peter Maydell
2014-04-17 20:35 ` Jason Gunthorpe
2014-04-22 9:44 ` Daniel Thompson
2014-04-22 17:05 ` Jason Gunthorpe
2014-04-22 17:55 ` Nicolas Pitre
2014-04-22 18:36 ` Russell King - ARM Linux
2014-04-22 14:50 ` Michal Simek
2014-04-22 17:00 ` [Qemu-devel] " Jason Gunthorpe
2014-04-22 17:11 ` Russell King - ARM Linux
2014-04-22 17:53 ` Jason Gunthorpe
2014-04-22 18:12 ` Russell King - ARM Linux
2014-04-22 18:32 ` Arnd Bergmann
2014-04-22 18:38 ` Russell King - ARM Linux
2014-04-22 18:45 ` Arnd Bergmann
2014-04-17 17:11 ` Rob Herring
2014-04-17 20:06 ` Nicolas Pitre
2014-04-17 20:16 ` Russell King - ARM Linux
2014-04-17 21:18 ` Rob Herring
2014-04-17 21:35 ` Russell King - ARM Linux
2014-04-18 2:53 ` Rob Herring
2014-04-18 4:34 ` Nicolas Pitre
2014-04-22 10:26 ` Daniel Thompson
2014-04-22 10:40 ` Russell King - ARM Linux
2014-04-22 11:41 ` Daniel Thompson
2014-04-18 8:41 ` Russell King - ARM Linux
2014-04-22 9:53 ` Daniel Thompson
2014-04-22 10:07 ` Russell King - ARM Linux
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=20140416223454.GN24070@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=cov@codeaurora.org \
--cc=daniel.thompson@linaro.org \
--cc=joelf@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=peter.crosthwaite@xilinx.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sboyd@codeaurora.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).