linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/9] ARM: multi-platform kconfig cleanup and mach-virt removal
Date: Wed, 12 Feb 2014 19:20:49 +0100	[thread overview]
Message-ID: <2009777.sVGA4zpnfU@wuerfel> (raw)
In-Reply-To: <20140212181527.GK29132@mudshark.cambridge.arm.com>

On Wednesday 12 February 2014 18:15:27 Will Deacon wrote:
> On Wed, Feb 12, 2014 at 06:07:56PM +0000, Arnd Bergmann wrote:
> > On Wednesday 12 February 2014 17:16:21 Will Deacon wrote:
> > > On Wed, Feb 12, 2014 at 05:11:45PM +0000, Marc Zyngier wrote:
> > > > On 12/02/14 16:53, Arnd Bergmann wrote:
> > > > > 
> > > > > On the topic of V6, we don't support CPU_V6T2 at all, though I assume that
> > > > > there is an ARM1156 core tile for integrator and realview, and we support
> > > > > running the V6/V6K parts with MMU turned off. Would all revisions of ARM1156
> > > > > work with CPU_V6K and !MMU?
> > > > 
> > > > CPU_V6 and !MMU should work. V6K might, but that requires close
> > > > inspection (WFE, SEV shouldn't be used in UP context)...
> > > 
> > > Well I can boot Debian on my 1136 r0p1 (no v6k) using a v6/v7 kernel, so the
> > > lack of MMU shouldn't change that.
> > 
> > I was more worried about ARM1156 not being a strict superset of V6K, i.e.
> > stuff other than the MMU missing from it that the kernel would rely on.
> 
> ARM1156 doesn't implement v6k, so you mean subset, right? My point was that
> 1136 works fine, so the only remaining part should be the lack of MMU.

I meant superset of the no-mmu subset of v6k. ARM1156 introduced Thumb2
support, so it's clearly not just a subset but also contains stuff that
wasn't part of v6k.

	Arnd

  reply	other threads:[~2014-02-12 18:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 21:11 [PATCH v2 0/9] ARM: multi-platform kconfig cleanup and mach-virt removal Rob Herring
2014-02-11 21:11 ` [PATCH v2 1/9] ARM: centralize common multi-platform kconfig options Rob Herring
2014-02-14 10:40   ` Linus Walleij
2014-02-14 14:02     ` Rob Herring
2014-02-24  9:41       ` Linus Walleij
2014-02-28 18:37   ` Kevin Hilman
2014-02-28 20:15     ` Arnd Bergmann
2014-02-28 20:22       ` Kevin Hilman
2014-02-28 20:33         ` Arnd Bergmann
2014-04-20 10:56           ` Daniel Willmann
2014-02-11 21:11 ` [PATCH 2/9] ARM: select HAVE_SMP for V7 multi-platform Rob Herring
2014-02-14 10:41   ` Linus Walleij
2014-02-11 21:11 ` [PATCH 3/9] ARM: select MIGHT_HAVE_CACHE_L2X0 " Rob Herring
2014-02-12 20:32   ` Stephen Warren
2014-02-13 13:10     ` Rob Herring
2014-02-11 21:11 ` [PATCH 4/9] ARM: Select V6K instead of V6 by default for multi-platform Rob Herring
2014-02-11 21:22   ` Arnd Bergmann
2014-02-11 21:26     ` Rob Herring
2014-02-11 21:27       ` Arnd Bergmann
2014-02-12  4:07   ` Shawn Guo
2014-02-11 21:11 ` [PATCH 5/9] ARM: bcm2835: enable V6K instead of plain V6 Rob Herring
2014-02-11 21:11 ` [PATCH 6/9] ARM: cns3xxx: " Rob Herring
2014-02-11 21:11 ` [PATCH 7/9] ARM: vt8500: " Rob Herring
2014-02-11 21:11 ` [PATCH 8/9] ARM: virt: make mach-virt just a kconfig option Rob Herring
2014-02-12 14:03   ` Marc Zyngier
2014-02-11 21:11 ` [PATCH 9/9] ARM: virt: select ARM_AMBA Rob Herring
2014-02-12 13:26 ` [PATCH v2 0/9] ARM: multi-platform kconfig cleanup and mach-virt removal Arnd Bergmann
2014-02-12 13:46   ` Will Deacon
2014-02-12 14:07     ` Rob Herring
2014-02-12 16:53       ` Arnd Bergmann
2014-02-12 17:11         ` Marc Zyngier
2014-02-12 17:16           ` Will Deacon
2014-02-12 18:07             ` Arnd Bergmann
2014-02-12 18:15               ` Will Deacon
2014-02-12 18:20                 ` Arnd Bergmann [this message]
2014-02-12 20:38 ` Stephen Warren
2014-02-13  2:30 ` Stephen Warren

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=2009777.sVGA4zpnfU@wuerfel \
    --to=arnd@arndb.de \
    --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).