linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org
Subject: Re: earlycon: no match?
Date: Mon, 4 May 2015 22:22:23 +0200	[thread overview]
Message-ID: <20150504202223.GT6325@pengutronix.de> (raw)
In-Reply-To: <55477BC1.6000805@hurleysoftware.com>

On Mon, May 04, 2015 at 10:01:37AM -0400, Peter Hurley wrote:
> Hi Robert,
> 
> On 05/03/2015 05:10 PM, Robert Schwebel wrote:
> > Hi Peter,
> > 
> > with 4.1-rc1, my boxes with early console enabled show something like
> > this (the example is vexpress, but it for example also happens on an
> > AM335x board):
> > 
> >   earlycon: no match for ttyAMA0,38400n8
> 
> This shouldn't impact any previous earlycon setup. Are you saying
> you're seeing a regression?
> 
> How do you have early console enabled, via the command line or via DT?

What happens here is that Robert has console=ttyAMA0,38400n8 in his
command line. In init/main.c we have:

static int __init do_early_param(char *param, char *val, const char *unused)
{
	const struct obs_kernel_param *p;

	for (p = __setup_start; p < __setup_end; p++) {
		if ((p->early && parameq(param, p->str)) ||
		    (strcmp(param, "console") == 0 &&
		     strcmp(p->str, "earlycon") == 0)
		) {
			if (p->setup_func(val) != 0)
				pr_warn("Malformed early option '%s'\n", param);
		}
	}
	/* We accept everything at this stage. */
	return 0;
}

This means that param_setup_earlycon() gets called with the arguments
passed to the console= parameter which makes no sense in this context
and leads to the "no match for" message.

Sascha

-- 
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 |

  parent reply	other threads:[~2015-05-04 20:22 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
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 [this message]
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=20150504202223.GT6325@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=peter@hurleysoftware.com \
    --cc=r.schwebel@pengutronix.de \
    /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).