From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: map ATAGs when not in first 1MB of RAM
Date: Thu, 27 Jan 2011 17:46:03 +0000 [thread overview]
Message-ID: <20110127174603.GB605@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D41AE4A.1000105@gmail.com>
On Thu, Jan 27, 2011 at 11:41:30AM -0600, Rob Herring wrote:
> Russell,
>
> On 01/27/2011 10:31 AM, Russell King - ARM Linux wrote:
>> On Thu, Jan 27, 2011 at 09:50:43AM -0600, Rob Herring wrote:
>>> + /*
>>> + * Otherwise map the 1MB region r2 points to (atags or dtb)
>>> + */
>>> +1: mov r0, r2, lsr #20
>>> + mov r0, r0, lsl #20
>>> + sub r3, r0, #(PHYS_OFFSET& 0xff000000)
>>> + .if (PHYS_OFFSET& 0x00f00000)
>>> + sub r3, r3, #(PHYS_OFFSET& 0x00f00000)
>>
>> This introduces new PHYS_OFFSET uses which we're trying hard to get
>> rid of. This will need to be reworked.
>
> Yeah, I didn't really like that either. How about this? It's untested.
> It replaces the whole section mapping the 1st 1MB and should make
> replacing this instance of PHYS_OFFSET with a variable easier.
With the p2v patches, queued for the next merge window, PHYS_OFFSET
becomes:
extern unsigned long __pv_phys_offset;
#define PHYS_OFFSET __pv_phys_offset
so using PHYS_OFFSET in any way in assembly isn't going to work too
well. Luckily, the p2v patches supply __create_page_tables with a
value of PHYS_OFFSET in r8.
What this means is that there's an fundamental interdependence between
your patches and mine. Your patches can work without the p2v patches.
Or they can be made to work with the p2v patches applied.
So I think this needs to wait until after the next merge window, or it
needs to be prepared against the p2v patches (see my p2v branch) and
applied there once everyone's happy with it.
next prev parent reply other threads:[~2011-01-27 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 15:50 [PATCH] ARM: map ATAGs when not in first 1MB of RAM Rob Herring
2011-01-27 16:31 ` Russell King - ARM Linux
2011-01-27 17:41 ` Rob Herring
2011-01-27 17:46 ` Russell King - ARM Linux [this message]
2011-02-02 3:26 ` Grant Likely
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=20110127174603.GB605@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