From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Change of TEXT_OFFSET for multi_v7_defconfig
Date: Tue, 22 Apr 2014 11:07:02 +0100 [thread overview]
Message-ID: <20140422100702.GS24070@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <53563C03.7090401@linaro.org>
On Tue, Apr 22, 2014 at 10:53:07AM +0100, Daniel Thompson wrote:
> On 17/04/14 22:35, Russell King - ARM Linux wrote:
> > On Thu, Apr 17, 2014 at 04:18:45PM -0500, Rob Herring wrote:
> >> The problem here is more than just the TEXT_OFFSET changed. From what
> >> I've heard, there are some QC chips which need much more reserved RAM
> >> than the 2MB discussed here. Changing the TEXT_OFFSET is a hack that
> >> doesn't scale.
> >
> > You may think it's a hack, but we really can't get around this. There
> > really are platforms out there where we must do this kind of stuff. I
> > invite you next time you meet up to talk to Michal Simek. There's no
> > way they can load the kernel at 32K into RAM.
>
> After reading this thread I have noticed that the sort order for the
> textofs part of this makefile is numeric (based on textofs) rather than
> alphabetic.
Correct.
> Is this an intentional mechanism? Certainly the result of numeric
> sorting is that the kernel will rise to the highest point in memory that
> suits all enabled platforms (based on the assumption that platforms are
> much more likely to reserve memory right at the start of RAM than
> slightly offset into it).
Also correct.
> If so would you welcome a comment only patch explaining this?
If you're willing to provide one.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.
prev parent reply other threads:[~2014-04-22 10:07 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
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 ` [Qemu-devel] " Michal Simek
2014-04-22 17:00 ` 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 [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=20140422100702.GS24070@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).