From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] ARM: use early console instead of early debug in allmodconfig kernels
Date: Tue, 28 Oct 2014 15:29:01 +0100 [thread overview]
Message-ID: <3063784.TXO37ZkrnY@wuerfel> (raw)
In-Reply-To: <20141028140536.GF27405@n2100.arm.linux.org.uk>
On Tuesday 28 October 2014 14:05:36 Russell King - ARM Linux wrote:
> On Tue, Oct 28, 2014 at 09:31:35PM +0800, Xia Kaixu wrote:
> > The early debug could break something when booting 'allmodconfig'
> > kernels. So we use early console instead of early debug.
> >
> > The early console didn't work yet on OMAP4460 because of missing
> > earlycon support and I am working on that.
>
> No. bloody. way.
>
> > @@ -78,7 +78,7 @@ config DEBUG_USER
> > # These options are only for real kernel hackers who want to get their hands dirty.
> > config DEBUG_LL
> > bool "Kernel low-level debugging functions (read help!)"
> > - depends on DEBUG_KERNEL
> > + depends on DEBUG_KERNEL && !ARCH_MULTIPLATFORM_STRICT
>
> Firstly, this is well advertised that it can only be applied to a single
> configuration. So I don't think we need this dependency here. Even if
> you want to build a strict multiplatform kernel, it should still be
> possible to enable this for a specific platform.
I've asked Kaixu to do this patch. This is one of the most fundamental
uses of ARCH_MULTIPLATFORM_STRICT: as soon as you turn on DEBUG_LL, the
kernel no longer runs on any other platform, so it can still be built
as a multiplatform kernel, but not a "strict" one that is known to
work on all hardware that is enabled.
> It's a developer option, one which requires the developer to engage their
> brain before using.
Exactly, and I think it's not asking too much from a developer to turn
off ARCH_MULTIPLATFORM_STRICT if they want to turn on DEBUG_LL. Nothing
else should change if you do that.
The main use of the symbol is really to avoid turning on DEBUG_LL is
allmodconfig kernels, which will always enable ARCH_MULTIPLATFORM_STRICT.
Arnd
next prev parent reply other threads:[~2014-10-28 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 13:31 [PATCH v2 0/5] ARM: get a strict multiplatform kernel that can run on any hardware Xia Kaixu
2014-10-28 13:31 ` [PATCH v2 1/5] ARM: introduce a CONFIG_ARCH_MULTIPLATFORM_STRICT Kconfig option Xia Kaixu
2014-10-28 14:18 ` Arnd Bergmann
2014-10-28 14:21 ` Russell King - ARM Linux
2014-10-28 13:31 ` [PATCH v2 2/5] ARM: change the corresponding arm/mach defconfigs Xia Kaixu
2014-10-28 13:31 ` [PATCH v2 3/5] ARM: restrict CPU_BIG_ENDIAN configuration option Xia Kaixu
2014-10-28 14:00 ` Russell King - ARM Linux
2014-10-28 14:37 ` Arnd Bergmann
2014-10-28 14:53 ` Russell King - ARM Linux
2014-10-28 16:03 ` Arnd Bergmann
2014-10-28 13:31 ` [PATCH v2 4/5] ARM: allow errata and XIP options to be enabled without ARCH_MULTIPLATFORM_STRICT Xia Kaixu
2014-10-28 14:02 ` Russell King - ARM Linux
2014-10-28 14:24 ` Arnd Bergmann
2014-10-28 14:31 ` Russell King - ARM Linux
2014-10-28 14:50 ` Arnd Bergmann
2014-10-28 15:05 ` Russell King - ARM Linux
2014-10-28 15:32 ` Arnd Bergmann
2014-10-28 13:31 ` [PATCH v2 5/5] ARM: use early console instead of early debug in allmodconfig kernels Xia Kaixu
2014-10-28 14:05 ` Russell King - ARM Linux
2014-10-28 14:29 ` Arnd Bergmann [this message]
2014-10-28 14:35 ` Russell King - ARM Linux
2014-10-28 15:01 ` 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=3063784.TXO37ZkrnY@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