From: vladimir.murzin@arm.com (Vladimir Murzin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: versatile: support configuring versatile machine for no-MMU
Date: Mon, 12 Dec 2016 13:06:51 +0000 [thread overview]
Message-ID: <584EA0EB.7040100@arm.com> (raw)
In-Reply-To: <20161209202901.GQ14217@n2100.armlinux.org.uk>
On 09/12/16 20:29, Russell King - ARM Linux wrote:
> On Wed, Dec 07, 2016 at 02:33:53PM +0000, Vladimir Murzin wrote:
>> Hi Linus,
>>
>> On 07/12/16 14:11, Linus Walleij wrote:
>>> Another target I had in mind was the Integrator which
>>> incidentally supports a bunch of the old noMMU core
>>> tiles where we can swap in an ARM946, which I guess
>>> could work with this?
>>
>> Do you mind trying my "Allow NOMMU for MULTIPLATFORM" series [1]? Greg just
>> reported it did a trick for Versatile, there is a good chance it would work
>> for Integrator too ;)
>
> My views on gluing multiplatform and nommu together have already been
> stated several times, and remain unchanged.
>
Should I treat this as the whole series is discarded or there is something you
can pick up?
Cheers
Vladimir
> Greg's patch looks almost sane, but what I'd like to see is instead of
> directly doing this:
>
> config ARCH_VERSATILE
> bool "ARM Ltd. Versatile family"
> - depends on ARCH_MULTI_V5
> + depends on ARCH_MULTI_V5 || ARM_SINGLE_ARMV5
>
> we could do:
>
> config ARCH_VERSATILE
> bool "ARM Ltd. Versatile family" if ARCH_MULTI_V5
> - depends on ARCH_MULTI_V5
> + depends on ARCH_MULTI_V5 || ARM_SINGLE_ARMV5
> default y if ARM_SINGLE_ARCH_VERSATILE
>
> adding the versatile entry in the upper level choice (where it always used
> to be) but with "ARM_SINGLE_ARCH_VERSATILE" instead.
>
> This would have the effect of allowing the multiplatform-converted stuff
> to start being used on nommu (again) but without running into the problems
> I've highlighted.
>
next prev parent reply other threads:[~2016-12-12 13:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 6:59 [PATCH 3/4] ARM: versatile: empty Makefile.boot needed for no-MMU compile Greg Ungerer
2016-12-07 6:59 ` [PATCH 4/4] ARM: versatile: support configuring versatile machine for no-MMU Greg Ungerer
2016-12-07 14:11 ` Linus Walleij
2016-12-07 14:33 ` Vladimir Murzin
2016-12-09 3:02 ` Greg Ungerer
2016-12-09 20:29 ` Russell King - ARM Linux
2016-12-12 5:48 ` Greg Ungerer
2016-12-12 5:50 ` [PATCHv2 4/4] ARM: versatile: support configuring versatile machine for, no-MMU Greg Ungerer
2016-12-12 13:06 ` Vladimir Murzin [this message]
2016-12-07 14:34 ` [PATCH 4/4] ARM: versatile: support configuring versatile machine for no-MMU Greg Ungerer
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=584EA0EB.7040100@arm.com \
--to=vladimir.murzin@arm.com \
--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).