mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Peter Hurley <peter@hurleysoftware.com>
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@pengutronix.de
Subject: Re: earlycon: no match?
Date: Thu, 7 May 2015 23:25:23 +0100 (BST)	[thread overview]
Message-ID: <alpine.LFD.2.11.1505072241140.1538@eddie.linux-mips.org> (raw)
In-Reply-To: <554BD56D.9010800@hurleysoftware.com>

On Thu, 7 May 2015, Peter Hurley wrote:

> >  How does this overload interact with multiple `console=' options being 
> > present BTW, which one is considered the early console?  Or do we support 
> > driving multiple early consoles in parallel just as we do with regular 
> > consoles?
> 
> Please familiarize yourself with the existing 'console=' and 'earlycon='
> command line options documented in Documentation/kernel-parameters.txt

 Thank you for your suggestion, however that documentation does not answer 
my questions I am afraid (and neither does serial-console.txt).  Otherwise
I wouldn't have asked them in the first place.  If you don't know the 
answers either, then it's OK to say: "I don't know".

 E.g. (given the parameter aliasing we have) will:

`earlycon=uart8250,io,0x3f8 console=tty0'
`console=tty0 earlycon=uart8250,io,0x3f8'

do what I expect it to, that is open the UART at 0x3f8 as an early console 
and then hand it over to the ttyS0 device as respectively a secondary and 
the primary (/dev/console) regular console?  I've skipped options such as 
baud rates for brevity.

  Maciej

  reply	other threads:[~2015-05-07 22:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-03 21:10 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 [this message]
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=alpine.LFD.2.11.1505072241140.1538@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --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

all inboxes | Powered by JetHome®