From: vladimir.murzin@arm•com (Vladimir Murzin)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] ARM: nommu: R-class fixes
Date: Wed, 27 Apr 2016 11:55:12 +0100 [thread overview]
Message-ID: <57209A90.5070707@arm.com> (raw)
In-Reply-To: <5212316.Wg9FOfdsuU@wuerfel>
On 27/04/16 10:50, Arnd Bergmann wrote:
> On Wednesday 27 April 2016 10:10:19 Vladimir Murzin wrote:
>>> On the other hand, separating the two has the advantage of keeping it
>>> simple, as we don't have to worry about all the ARMv7-A platforms
>>> and whether we actually want to allow their kernels to be built with
>>> MMU disabled.
>>>
>>
>> Ok, what if we start with your approach explicitly saying which platform
>> wants to be listed when CONFIG_MMU is deselected (I think R-class is the
>> first user here) gradually extending such list with ARMv7-A? There is
>> (little?) chance that at some point we can support kernel which can run
>> on both configurations.
>
> Do you mean adding a ARM_SINGLE_ARMV7R option, or ARCH_MULTI_V7R?
I'd think that ARCH_MULTI_V7R would make more sense since it is close
rather to the CPU variant than platform, so for the imaginary case where
ARMv7-A platform want to run without MMU can adjust it's dependency to
depends on ARCH_MULTI_V7 || ARCH_MULTI_V7R
where
config ARCH_MULTI_V7
bool "ARMv7 based platforms (Cortex-A, PJ4, Scorpion, Krait)"
depends on MMU
...
config ARCH_MULTI_V7R
bool "MMU-less ARMv7 based platforms (Cortex-R)"
depends on !MMU
...
It is also should work for purely R-class platform, although I'm not
keen on Kconfig and may be totally wrong here :(
Cheers
Vladimir
>
> Arnd
>
>
next prev parent reply other threads:[~2016-04-27 10:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 11:43 [PATCH 0/3] ARM: nommu: R-class fixes Vladimir Murzin
2016-04-22 11:43 ` [PATCH 1/3] ARM: nommu: fix PMSAv7 setup Vladimir Murzin
2016-04-22 11:43 ` [PATCH 2/3] ARM: nommu: change memory reserve for the vectors Vladimir Murzin
2016-04-22 11:43 ` [PATCH 3/3] ARM: domain: move {set,get}_domain under config guard Vladimir Murzin
2016-04-27 10:49 ` [PATCH 3/3] ARM: domain: move {set, get}_domain " Russell King - ARM Linux
2016-04-27 12:16 ` Vladimir Murzin
2016-04-28 13:50 ` Russell King - ARM Linux
2016-04-28 14:44 ` Vladimir Murzin
2016-04-28 14:59 ` Russell King - ARM Linux
2016-04-28 15:06 ` Vladimir Murzin
2016-04-23 6:54 ` [PATCH 0/3] ARM: nommu: R-class fixes Afzal Mohammed
2016-04-25 7:55 ` Vladimir Murzin
2016-04-25 12:59 ` Arnd Bergmann
2016-04-25 13:30 ` Afzal Mohammed
2016-04-26 8:17 ` Vladimir Murzin
2016-04-26 8:17 ` Vladimir Murzin
2016-04-26 9:10 ` Arnd Bergmann
2016-04-26 10:57 ` Vladimir Murzin
2016-04-26 11:59 ` Arnd Bergmann
2016-04-26 12:24 ` Vladimir Murzin
2016-04-26 18:12 ` Arnd Bergmann
2016-04-27 9:10 ` Vladimir Murzin
2016-04-27 9:50 ` Arnd Bergmann
2016-04-27 10:55 ` Vladimir Murzin [this message]
2016-04-27 11:18 ` Arnd Bergmann
2016-04-26 15:23 ` Afzal Mohammed
2016-04-28 9:41 ` Maxime Coquelin
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=57209A90.5070707@arm.com \
--to=vladimir.murzin@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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