From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de
Subject: Re: earlycon: no match?
Date: Tue, 5 May 2015 06:51:39 +0200 [thread overview]
Message-ID: <20150505045139.GY15254@pengutronix.de> (raw)
In-Reply-To: <5547F350.7030405@hurleysoftware.com>
Peter,
On Mon, May 04, 2015 at 06:31:44PM -0400, Peter Hurley wrote:
> > You say it is a diagnostics message that indicates a misspelling.
> > I fail to see what is misspelled, so what does it diagnose?
>
> Ok, so this is only about the diagnostic message, and not about some
> other failure.
>
> I don't typically describe harmless diagnostics that didn't appear before
> as "broken", so I was having trouble believing what I was reading.
>
> Now that I understand that this is _only_ about a diagnostic message that
> didn't appear in previous kernels, I will direct to what I have written
> previously multiple times.
>
> Further, I would ask how _you_ would programmatically distinguish
> misspellings amongst the following console strings?
>
> console=pl012,...
> console=_pl011,...
> console=pl,...
> console=ttyAMA0,...
Only the last line gives me output, but with the warning. All others are
misspellings but output nothing. The last one gives me a misspelling
warning, but it is the one that makes the output work.
Obviously this was not tested on an ARM device with a serial console,
because it doesn't work there.
There should be an intended variant where *nothing* is misspelled in my
oftree+kernel commandline.
In that case, the system should come up, console comes out of the serial
line and earlycon is available. Then I should not get a diagnostic
message, becasue I did everything right.
Case A: consoleo=ttyAMA0
Result: - system boots with output on intended serial console
- warning about having the earlycon misspelled
- earlycon not operational, although driver supports it
Case B: console=pl011
Result: - no output at all, because system doesn't output to its
intented serial console.
Case C: ...?
Are there other things I'm supposed to do in order to do it right?
So both cases A+B are not fully working as intented, right?
I'd like to fix it, but in order to do so, I want to learn how it is
actually *intended* to work.
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2015-05-05 4:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-03 21:10 earlycon: no match? Robert Schwebel
2015-05-04 14:01 ` Peter Hurley
2015-05-04 16:52 ` Peter Hurley
2015-05-04 19:42 ` Robert Schwebel
2015-05-04 20:21 ` Peter Hurley
2015-05-04 20:52 ` Robert Schwebel
2015-05-04 21:27 ` Peter Hurley
2015-05-04 21:58 ` Robert Schwebel
2015-05-04 22:31 ` Peter Hurley
2015-05-05 4:51 ` Robert Schwebel [this message]
2015-05-05 10:39 ` Peter Hurley
2015-05-05 16:32 ` Robert Schwebel
2015-05-05 18:15 ` Peter Hurley
2015-05-05 17:06 ` Fabio Estevam
2015-05-07 17:09 ` Maciej W. Rozycki
2015-05-07 17:22 ` Peter Hurley
2015-05-07 20:14 ` Maciej W. Rozycki
2015-05-07 21:13 ` Peter Hurley
2015-05-07 22:25 ` Maciej W. Rozycki
2015-05-07 22:37 ` Peter Hurley
2015-05-08 16:11 ` Maciej W. Rozycki
2015-05-08 6:34 ` Sascha Hauer
2015-05-08 10:12 ` Peter Hurley
2015-05-04 20:22 ` Sascha Hauer
2015-05-04 20:34 ` Peter Hurley
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=20150505045139.GY15254@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.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 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).