From: Rabin Vincent <rabin@rab.in>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Peter Hurley <peter@hurleysoftware.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Rob Herring <robh+dt@kernel.org>,
linux-serial@vger.kernel.org
Subject: Re: debug tip after earlycon is closed?
Date: Mon, 8 Aug 2016 11:08:57 +0200 [thread overview]
Message-ID: <20160808090857.GA20832@lnxartpec.se.axis.com> (raw)
In-Reply-To: <20160728122022.GZ1041@n2100.armlinux.org.uk>
On Thu, Jul 28, 2016 at 01:20:22PM +0100, Russell King - ARM Linux wrote:
> To me, what this means is that the DT parsing of linux,stdout is
> broken - while it may look nice from a design point of view, the
> design is wrong and fails to take account of non-UART consoles in
> the system.
Note that the brokeness you describe also leads to stdout-path being
unable to put the console on any serial port but the first, as reported
here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/323811.html
It always puts the console on the first serial port if CONFIG_VT_CONSOLE
is not enabled, even if the stdout-path property requests a different
serial port.
WARNING: multiple messages have this Message-ID (diff)
From: rabin@rab.in (Rabin Vincent)
To: linux-arm-kernel@lists.infradead.org
Subject: debug tip after earlycon is closed?
Date: Mon, 8 Aug 2016 11:08:57 +0200 [thread overview]
Message-ID: <20160808090857.GA20832@lnxartpec.se.axis.com> (raw)
In-Reply-To: <20160728122022.GZ1041@n2100.armlinux.org.uk>
On Thu, Jul 28, 2016 at 01:20:22PM +0100, Russell King - ARM Linux wrote:
> To me, what this means is that the DT parsing of linux,stdout is
> broken - while it may look nice from a design point of view, the
> design is wrong and fails to take account of non-UART consoles in
> the system.
Note that the brokeness you describe also leads to stdout-path being
unable to put the console on any serial port but the first, as reported
here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-February/323811.html
It always puts the console on the first serial port if CONFIG_VT_CONSOLE
is not enabled, even if the stdout-path property requests a different
serial port.
next prev parent reply other threads:[~2016-08-08 9:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 1:23 debug tip after earlycon is closed? Masahiro Yamada
2016-07-27 1:23 ` Masahiro Yamada
2016-07-27 2:17 ` Sebastian Reichel
2016-07-27 2:17 ` Sebastian Reichel
2016-07-27 3:26 ` Masahiro Yamada
2016-07-27 3:26 ` Masahiro Yamada
2016-07-27 7:32 ` Arnd Bergmann
2016-07-27 7:32 ` Arnd Bergmann
2016-07-27 7:32 ` Arnd Bergmann
2016-07-28 2:08 ` Masahiro Yamada
2016-07-28 2:08 ` Masahiro Yamada
2016-07-28 7:44 ` Arnd Bergmann
2016-07-28 7:44 ` Arnd Bergmann
2016-07-28 12:20 ` Russell King - ARM Linux
2016-07-28 12:20 ` Russell King - ARM Linux
2016-08-08 9:08 ` Rabin Vincent [this message]
2016-08-08 9:08 ` Rabin Vincent
2016-08-12 3:44 ` Masahiro Yamada
2016-08-12 3:44 ` Masahiro Yamada
2016-08-12 3:44 ` Masahiro Yamada
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=20160808090857.GA20832@lnxartpec.se.axis.com \
--to=rabin@rab.in \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=peter@hurleysoftware.com \
--cc=robh+dt@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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.