linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: peter@hurleysoftware.com (Peter Hurley)
To: linux-arm-kernel@lists.infradead.org
Subject: Which is better to specify console, "console= " or "stdout-path" ?
Date: Wed, 21 Oct 2015 08:46:09 -0400	[thread overview]
Message-ID: <56278911.9050704@hurleysoftware.com> (raw)
In-Reply-To: <562753A6.3070107@arm.com>

On 10/21/2015 04:58 AM, Sudeep Holla wrote:
> On 21/10/15 06:09, Masahiro Yamada wrote:
>> I think there exist two ways to specify the console port and baudrate.
>>
>>
>> [1] Specify console in bootargs
>>
>>    chosen {
>>          bootargs = "console=ttyS0,115200";
>>    };
>>
>>
>> [2] Specify stdout-path
>>
>>     chosen {
>>           stdout-path = "serial0:115200n8";
> 
> This will work for even early/boot console, so this is better than
> option [1]

Be aware that options specified via /chosen/stdout-path are
currently ignored by earlycon. There were some hiccups getting the
initial support upstream; when 4.4 hits mainline, I'll resubmit
my series that implements the of_serial i/o properties and
options passthrough to earlycon setup.

Regards,
Peter Hurley

  reply	other threads:[~2015-10-21 12:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21  5:09 Which is better to specify console, "console= " or "stdout-path" ? Masahiro Yamada
2015-10-21  7:43 ` Arnd Bergmann
2015-10-21  8:58 ` Sudeep Holla
2015-10-21 12:46   ` Peter Hurley [this message]
2015-10-21 12:54     ` Sudeep Holla
2015-10-21 13:02       ` Peter Hurley
2015-10-21 13:06         ` Sudeep Holla
2015-10-21 15:38     ` Masahiro Yamada
2015-10-21 16:26       ` Peter Hurley
2015-10-22  4:20         ` Masahiro Yamada
2015-10-28 16:00           ` 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=56278911.9050704@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --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;
as well as URLs for NNTP newsgroup(s).