From: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
To: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Cc: Masahiro Yamada
<yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Which is better to specify console, "console= " or "stdout-path" ?
Date: Wed, 21 Oct 2015 09:43:43 +0200 [thread overview]
Message-ID: <4192029.T14mE8UQNd@wuerfel> (raw)
In-Reply-To: <CAK7LNAS9uBJ1cVmGBKae3W0tk8Siu1yeXOaeN6Kz11cksMqtsg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wednesday 21 October 2015 14:09:42 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";
> };
>
>
>
> Now I have both in my DTS, but it is redundant.
>
> So, I want to select either [1] or [2].
>
>
> Which is a preferable way?
>
stdout-path is better. It took us a while to get that implemented
on arm32, but now that it works, we should all use it.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-10-21 7:43 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
[not found] ` <CAK7LNAS9uBJ1cVmGBKae3W0tk8Siu1yeXOaeN6Kz11cksMqtsg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-21 7:43 ` Arnd Bergmann [this message]
2015-10-21 8:58 ` Sudeep Holla
[not found] ` <562753A6.3070107-5wv7dgnIgG8@public.gmane.org>
2015-10-21 12:46 ` Peter Hurley
[not found] ` <56278911.9050704-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-10-21 12:54 ` Sudeep Holla
[not found] ` <56278AFD.8000505-5wv7dgnIgG8@public.gmane.org>
2015-10-21 13:02 ` Peter Hurley
[not found] ` <56278CF3.9010400-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-10-21 13:06 ` Sudeep Holla
2015-10-21 15:38 ` Masahiro Yamada
[not found] ` <CAK7LNAQ_+_9K-y7bmpdGwcH2u4uqJhJhON1Ew4OvzSSa-amyvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-21 16:26 ` Peter Hurley
[not found] ` <5627BCBC.5040701-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-10-22 4:20 ` Masahiro Yamada
[not found] ` <CAK7LNASqjd_Xf53WKa=Ogesf80HQzEoKEyVtw-BMh7JF=jq+xQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=4192029.T14mE8UQNd@wuerfel \
--to=arnd-r2ngtmty4d4@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yamada.masahiro-uWyLwvC0a2jby3iVrkZq2A@public.gmane.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).