From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: clean-up common multi-platform kconfig options
Date: Sat, 7 Dec 2013 18:10:52 +0000 [thread overview]
Message-ID: <20131207181052.GR4360@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAL_JsqJmwPwVmNzibr8S-RH8ibwCzXVFMdJA-STPTHG+H0113w@mail.gmail.com>
On Fri, Dec 06, 2013 at 02:01:51PM -0600, Rob Herring wrote:
> On Fri, Dec 6, 2013 at 10:41 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > This prevents you from building a plain v6 SMP kernel, and we've
> > had a variation of that since CONFIG_SMP was first marked non-BROKEN.
>
> I'm saying a v6k enabled kernel would not work on pure v6 h/w. But
> since all implementations appear to support doubleword exclusives and
> there may not be any pure v6 only h/w, then we may never have a
> problem with the code below.
I wonder why we have the SMP_ON_UP option. It's there so that we can
do exactly this - build a SMP kernel (so, one for V6K or later) _and_
have it run on non-SMP capable V6 platforms.
Now, while it's true that ARMv6 doesn't have the WFI instruction, and
that was introduced in ARMv6K, when we include support for ARMv6, we
don't use that instruction - we use its MCR equivalent.
Remember, we've specifically put work into the kernel so that ARMv6
can operate as part of the single zImage kernel precisely because we
have mixtures of SoCs which have this spread of architectures.
So, as far as I'm aware, today, a kernel which has V6, V6K and V7
will work across all those CPUs.
What's rather annoying in this thread is that you and Arnd are running
around seemingly making decisions on this without bothering to find out
the details, in persuit of endless cleanups. Where is this heading?
Yet more fscking breakage of the ARM kernel, leading to platforms which
won't boot. I'm getting rather sick and tired of cleaning up after
this kind of activity, so I'm going to tell you right now to stop this.
I've had to push a whole load of footbridge patches into stable kernels
during the last fortnight because of this. For instance, Rob, your
changes to the way that VGA was supported on ARM pretty much broke the
whole thing leading to an oops on boot at 0xb80000.
Please stop this madness.
next prev parent reply other threads:[~2013-12-07 18:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 16:58 [PATCH] ARM: clean-up common multi-platform kconfig options Rob Herring
2013-12-05 20:25 ` Arnd Bergmann
2013-12-05 21:34 ` Rob Herring
2013-12-05 21:50 ` Arnd Bergmann
2013-12-06 4:10 ` Rob Herring
2013-12-06 16:41 ` Arnd Bergmann
2013-12-06 16:59 ` Nicolas Pitre
2013-12-06 20:01 ` Rob Herring
2013-12-07 4:52 ` Arnd Bergmann
2013-12-07 17:41 ` Tony Lindgren
2013-12-07 18:10 ` Russell King - ARM Linux [this message]
2013-12-07 20:49 ` Rob Herring
2013-12-08 2:21 ` Nicolas Pitre
2013-12-08 3:02 ` Arnd Bergmann
2013-12-08 3:39 ` Arnd Bergmann
2013-12-07 18:02 ` Russell King - ARM Linux
2013-12-07 18:31 ` Arnd Bergmann
2013-12-11 16:41 ` Michal Simek
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=20131207181052.GR4360@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).