From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: nommu: re-enable use of vexpress without ARCH_MULTIPLATFORM
Date: Thu, 10 Jan 2013 10:16:44 +0000 [thread overview]
Message-ID: <201301101016.44708.arnd@arndb.de> (raw)
In-Reply-To: <50EE3ADA.2070100@gmail.com>
On Thursday 10 January 2013, Rob Herring wrote:
> >
> > What I actually suggested is that we should be aiming for the DT side
> > of things to get to the point where DT is just another single platform
> > as far as that code goes, and that DT should describe the hardware
> > sufficiently well that we don't have multiple machine_desc things to
> > select via DT - so a DT kernel would have exactly one machine_desc (or
> > maybe even zero! - with the linker script check conditional on !CONFIG_OF)
> >
> > That then gets rid of the issue entirely.
>
> I agree completely. I look at mach-highbank (and mach-virt) as what else
> needs to be done in terms of refactoring or moving to DT.
It's also what we are doing on arm64 from the start, where there is
no machine descriptor already. Any experience we make with arm64 will
also help us improve arm in the long run, I hope.
> That's certainly a long term goal, but what is the short term solution?
I'd certainly be happy with
* removing the intentional build error for ARCH_MULTIPLATFORM, but leaving
it in for !ARCH_MULTIPLATFORM
* having mach-virt enabled by default on ARCH_MULTIPLATFORM, and only
visible for EXPERT.
* making mach-virt compatible with all CPUs starting with ARM7.
That would make allnoconfig, allyesconfig and allmodconfig work (besides
all the other bugs) on qemu at least, avoid build errors with randconfig
and make it hard enough to build a kernel that doesn't run on anything.
Arnd
next prev parent reply other threads:[~2013-01-10 10:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 18:15 [PATCH] ARM: nommu: re-enable use of vexpress without ARCH_MULTIPLATFORM Jonathan Austin
2013-01-09 18:30 ` Nicolas Pitre
2013-01-09 18:41 ` Will Deacon
2013-01-09 19:17 ` [PATCH v2] " Jonathan Austin
2013-01-09 18:43 ` [PATCH] " Arnd Bergmann
2013-01-09 18:54 ` Nicolas Pitre
2013-01-09 20:22 ` Arnd Bergmann
2013-01-09 20:39 ` Rob Herring
2013-01-09 20:48 ` Russell King - ARM Linux
2013-01-10 3:51 ` Rob Herring
2013-01-10 10:16 ` Arnd Bergmann [this message]
2013-01-10 13:20 ` Christopher Covington
2013-01-10 13:45 ` Marc Zyngier
2013-01-09 21:09 ` Nicolas Pitre
2013-01-09 21:00 ` Nicolas Pitre
2013-01-09 21:15 ` Arnd Bergmann
2013-01-09 21:37 ` Nicolas Pitre
2013-01-09 22:14 ` Arnd Bergmann
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=201301101016.44708.arnd@arndb.de \
--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 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.