linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/7] Re-organize linker layouts
Date: Mon, 11 Jul 2011 13:17:27 -0700	[thread overview]
Message-ID: <4E1B5A57.3010701@codeaurora.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1107081417080.14596@xanadu.home>

On 7/8/2011 11:24 AM, Nicolas Pitre wrote:
> On Fri, 8 Jul 2011, Stephen Boyd wrote:
>> Why can't this work via atags (or DT for that matter)? atags have always
>> said where ram starts and we should be able to write some code that
>> parses the atags/DT and figures out the final resting place of the
>> decompressed image.
> Possibly.  But that would be an MSM special case.
>

Hmm. I thought ST-Erricson folks had something similar.

Anyway, maybe we've been going about this the wrong way. Couldn't we
just make TEXT_OFFSET be 0x00208000 and then make sure to remove the
first 2MB of memory in a machine->reserve() routine if we're MSM?

Something like PHYS_OFFSET=0xN0000000 and TEXT_OFFSET=0x00208000 so that
our text ends up at the right place (0xN0208000) and AUTO_ZRELADDR will
be happy. This seems to work as long as I fixup the atags to say memory
starts at 0xN000000 instead of 0xN0200000.

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

  reply	other threads:[~2011-07-11 20:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 10:22 [PATCH 0/7] Re-organize linker layouts Russell King - ARM Linux
2011-07-06 10:23 ` [PATCH 1/7] ARM: ensure tag tables are const Russell King - ARM Linux
2011-07-06 10:23 ` [PATCH 2/7] ARM: decompressor: use better output sections Russell King - ARM Linux
2011-07-06 10:23 ` [PATCH 3/7] ARM: vmlinux.lds: move discarded sections to beginning Russell King - ARM Linux
2011-07-06 10:24 ` [PATCH 4/7] ARM: vmlinux.lds: rearrange .init output section Russell King - ARM Linux
2011-07-06 10:24 ` [PATCH 5/7] ARM: vmlinux.lds: remove .rodata/.rodata1 from main .text segment Russell King - ARM Linux
2011-07-06 10:24 ` [PATCH 6/7] ARM: vmlinux.lds: move init sections between text and data sections Russell King - ARM Linux
2011-07-06 10:25 ` [PATCH 7/7] ARM: vmlinux.lds: use _text and _stext the same way as x86 Russell King - ARM Linux
2011-07-06 15:09 ` [PATCH 0/7] Re-organize linker layouts Nicolas Pitre
2011-07-07 17:28 ` Stephen Boyd
2011-07-07 22:36   ` Russell King - ARM Linux
2011-07-08  0:55     ` Stephen Boyd
2011-07-08  9:07       ` Russell King - ARM Linux
2011-07-08 13:46         ` Nicolas Pitre
2011-07-08 16:03           ` Russell King - ARM Linux
2011-07-08 16:56             ` Stephen Boyd
2011-07-08 18:24               ` Nicolas Pitre
2011-07-11 20:17                 ` Stephen Boyd [this message]
2011-07-11 22:14                   ` Nicolas Pitre
2011-07-19 17:22                     ` David Brown
2011-07-19 18:02                       ` Nicolas Pitre
2011-07-19 20:42                         ` David Brown

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=4E1B5A57.3010701@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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).