From: stefan@agner.ch (Stefan Agner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 07/11] ARM: allow MULTIPLATFORM with !MMU
Date: Mon, 06 Apr 2015 11:33:53 +0200 [thread overview]
Message-ID: <f2b85e294afb55fdca85a16e6ad6c13c@agner.ch> (raw)
In-Reply-To: <20150406085443.GD12732@n2100.arm.linux.org.uk>
On 2015-04-06 10:54, Russell King - ARM Linux wrote:
> On Mon, Apr 06, 2015 at 10:38:10AM +0200, Stefan Agner wrote:
>> We already prevent a kernel image which mixes V4/V4T/V5 and V6/V7. And
>> so we would do with V7M too. Just because it's in multiplatform doesn't
>> mean we need to mix things up.
>
> I don't think you're getting what I'm saying at all... :(
It's not that I don't get it. I'm just arguing against it.
IMHO, it's wrong to create a parallel universe for v7M multiplatform...
Multiplatform as I understand it is mainly about selecting multiple SoC
_platforms_ but not necessarily multiple CPU platforms. It happens to
work well for V6/V7, but does not for others, and preventing
multiselection for incompatible CPU platforms is the way to prevent
creating such images.
> Please read the first bit of my replies again, where I say that we do
> _not_ want to remove the !MMU dependency from multiplatform. This is
> something I feel _very_ strongly about, and something which I've written
> about many times on this list.
Ok, I don't have such a strong feel for multiplatform, it just feels a
bit better to me. I need a top level ARCH which is able to live with
!MMU. Will try the ARCH_SINGLE_ARMV7M approach then.
--
Stefan
next prev parent reply other threads:[~2015-04-06 9:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 19:44 [PATCH v4 00/11] ARM: vf610m4: Add Vybrid Cortex-M4 support Stefan Agner
2015-04-03 19:44 ` [PATCH v4 01/11] genirq: generic chip: support hierarchy domain Stefan Agner
2015-04-03 19:44 ` [PATCH v4 02/11] irqchip: nvic: support hierarchy irq domain Stefan Agner
2015-04-03 19:44 ` [PATCH v4 03/11] irqchip: vf610-mscm: support NVIC parent Stefan Agner
2015-04-03 19:44 ` [PATCH v4 04/11] ARM: ARMv7M: define size of vector table for Vybrid Stefan Agner
2015-04-03 19:44 ` [PATCH v4 05/11] clocksource: add dependencies for Vybrid pit clocksource Stefan Agner
2015-04-03 19:44 ` [PATCH v4 06/11] ARM: unify MMU/!MMU addruart calls Stefan Agner
2015-04-03 19:44 ` [PATCH v4 07/11] ARM: allow MULTIPLATFORM with !MMU Stefan Agner
2015-04-03 20:09 ` Russell King - ARM Linux
2015-04-03 23:56 ` Stefan Agner
2015-04-05 16:10 ` Russell King - ARM Linux
2015-04-05 22:19 ` Stefan Agner
2015-04-05 22:44 ` Russell King - ARM Linux
2015-04-05 23:50 ` Stefan Agner
2015-04-06 8:15 ` Russell King - ARM Linux
2015-04-06 8:38 ` Stefan Agner
2015-04-06 8:54 ` Russell King - ARM Linux
2015-04-06 9:33 ` Stefan Agner [this message]
2015-04-06 10:13 ` Russell King - ARM Linux
2015-04-03 19:44 ` [PATCH v4 08/11] ARM: efm32: move into multiplatform Stefan Agner
2015-04-03 19:44 ` [PATCH v4 09/11] ARM: vf610: enable Cortex-M4 on Vybrid SoC Stefan Agner
2015-04-03 19:44 ` [PATCH v4 10/11] ARM: dts: add support for Vybrid running on Cortex-M4 Stefan Agner
2015-04-03 19:44 ` [PATCH v4 11/11] ARM: vf610m4: add defconfig for Linux on Vybrids Cortex-M4 Stefan Agner
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=f2b85e294afb55fdca85a16e6ad6c13c@agner.ch \
--to=stefan@agner.ch \
--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).