Thread (1 message) 1 message, 1 author, 2015-10-21

Re: Which is better to specify console, "console= " or "stdout-path" ?

From: Sudeep Holla <hidden>
Date: 2015-10-21 12:54:21
Also in: linux-arm-kernel, linux-serial


On 21/10/15 13:46, Peter Hurley wrote:
On 10/21/2015 04:58 AM, Sudeep Holla wrote:
quoted
On 21/10/15 06:09, Masahiro Yamada wrote:
quoted
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.
Yes I am aware of that. IIUC it's in -next now and works fine for me.
But having stdout-path in the DTS won't hinder normal console in anyway.
So I prefer it even without the patch you are referring(to support early
console parsing stdout-path)

-- 
Regards,
Sudeep
--
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help