From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
R Sricharan <r.sricharan@ti.com>
Subject: Re: [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address space.
Date: Thu, 10 May 2012 12:41:35 +0530 [thread overview]
Message-ID: <4FAB6A27.3050509@ti.com> (raw)
In-Reply-To: <20120509154849.GA10375@n2100.arm.linux.org.uk>
On Wednesday 09 May 2012 09:18 PM, Russell King - ARM Linux wrote:
> On Wed, May 09, 2012 at 06:00:10PM +0530, Shilimkar, Santosh wrote:
>> On Wed, May 9, 2012 at 5:53 PM, Russell King - ARM Linux
>> <linux@arm.linux.org.uk> wrote:
>>> On Wed, May 09, 2012 at 02:20:28PM +0530, Shilimkar, Santosh wrote:
>>>> The only change done common code is clearing 'XN' bit for DRAM
>>>> region in page table entries. The other change of setting the DACR
>>>> register is done in ARMv7 specific code.
>>>
>>> Yes, XN is an ARMv6+ thing. Before ARMv5, it was implementation defined.
>>>
>>> Some implementations used the bit to mean "allow writes to update the
>>> cache". Other implementations labelled this bit as "should be zero"
>>> while others labelled it as "should be one".
>>>
>> Good to know.
>>
>>> The upshot of this is, we know that having this bit as '1' means that
>>> all the CPUs we support today work. I would be _very_ concerned to
>>> change this bit to zero as we _really_ don't know how the pre-ARMv6
>>> CPUs would react.
>>>
>> I agree.
>>
>>> The solution to this is pretty simple - if ARMv6+ needs a different
>>> base section mapping value, then we need to extract that from the code
>>> and pass in the base section mapping value.
>>>
>>> I'll sort out a patch later today for this.
>> Great.
>
> This works for my 4430SDP board. I haven't booted it on anything else yet.
> Please can you check that this solves the issue for you? Thanks.
>
Yes it does.
Are you planning to merge below patch as is or split
the patch like 1) Refactoring 2) ARMv7 fix
Either is fine with me.
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Regards
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address space.
Date: Thu, 10 May 2012 12:41:35 +0530 [thread overview]
Message-ID: <4FAB6A27.3050509@ti.com> (raw)
In-Reply-To: <20120509154849.GA10375@n2100.arm.linux.org.uk>
On Wednesday 09 May 2012 09:18 PM, Russell King - ARM Linux wrote:
> On Wed, May 09, 2012 at 06:00:10PM +0530, Shilimkar, Santosh wrote:
>> On Wed, May 9, 2012 at 5:53 PM, Russell King - ARM Linux
>> <linux@arm.linux.org.uk> wrote:
>>> On Wed, May 09, 2012 at 02:20:28PM +0530, Shilimkar, Santosh wrote:
>>>> The only change done common code is clearing 'XN' bit for DRAM
>>>> region in page table entries. The other change of setting the DACR
>>>> register is done in ARMv7 specific code.
>>>
>>> Yes, XN is an ARMv6+ thing. Before ARMv5, it was implementation defined.
>>>
>>> Some implementations used the bit to mean "allow writes to update the
>>> cache". Other implementations labelled this bit as "should be zero"
>>> while others labelled it as "should be one".
>>>
>> Good to know.
>>
>>> The upshot of this is, we know that having this bit as '1' means that
>>> all the CPUs we support today work. I would be _very_ concerned to
>>> change this bit to zero as we _really_ don't know how the pre-ARMv6
>>> CPUs would react.
>>>
>> I agree.
>>
>>> The solution to this is pretty simple - if ARMv6+ needs a different
>>> base section mapping value, then we need to extract that from the code
>>> and pass in the base section mapping value.
>>>
>>> I'll sort out a patch later today for this.
>> Great.
>
> This works for my 4430SDP board. I haven't booted it on anything else yet.
> Please can you check that this solves the issue for you? Thanks.
>
Yes it does.
Are you planning to merge below patch as is or split
the patch like 1) Refactoring 2) ARMv7 fix
Either is fine with me.
Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Regards
Santosh
next prev parent reply other threads:[~2012-05-10 7:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 13:42 [PATCH] ARM: decompressor: Fix mmu mapping for non-DRAM address space Santosh Shilimkar
2012-05-07 13:42 ` Santosh Shilimkar
2012-05-08 12:41 ` Catalin Marinas
2012-05-08 12:41 ` Catalin Marinas
2012-05-08 14:01 ` Shilimkar, Santosh
2012-05-08 14:01 ` Shilimkar, Santosh
2012-05-08 14:16 ` Catalin Marinas
2012-05-08 14:16 ` Catalin Marinas
2012-05-08 14:20 ` Santosh Shilimkar
2012-05-08 14:20 ` Santosh Shilimkar
2012-05-08 14:23 ` Catalin Marinas
2012-05-08 14:23 ` Catalin Marinas
2012-05-08 14:43 ` Santosh Shilimkar
2012-05-08 14:43 ` Santosh Shilimkar
2012-05-08 21:55 ` Russell King - ARM Linux
2012-05-08 21:55 ` Russell King - ARM Linux
2012-05-09 8:50 ` Shilimkar, Santosh
2012-05-09 8:50 ` Shilimkar, Santosh
2012-05-09 10:23 ` Catalin Marinas
2012-05-09 10:23 ` Catalin Marinas
2012-05-09 12:23 ` Russell King - ARM Linux
2012-05-09 12:23 ` Russell King - ARM Linux
2012-05-09 12:30 ` Shilimkar, Santosh
2012-05-09 12:30 ` Shilimkar, Santosh
2012-05-09 15:48 ` Russell King - ARM Linux
2012-05-09 15:48 ` Russell King - ARM Linux
2012-05-09 20:44 ` Buckley, Bryan
2012-05-09 20:44 ` Buckley, Bryan
2012-05-09 21:40 ` Russell King - ARM Linux
2012-05-09 21:40 ` Russell King - ARM Linux
2012-05-15 18:55 ` Buckley, Bryan
2012-05-15 18:55 ` Buckley, Bryan
2012-05-10 7:11 ` Santosh Shilimkar [this message]
2012-05-10 7:11 ` Santosh Shilimkar
2012-05-10 8:53 ` Russell King - ARM Linux
2012-05-10 8:53 ` Russell King - ARM Linux
2012-05-10 9:41 ` Santosh Shilimkar
2012-05-10 9:41 ` Santosh Shilimkar
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=4FAB6A27.3050509@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=r.sricharan@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.