linux-kernel - Specifying console via "stdout-path" property

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Tue, 22 Aug 2017 18:10:52 +0000
From:   Eugeniy Paltsev <Eugeniy.Paltsev@...opsys.com>
To:     "linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>
CC:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-snps-arc@...ts.infradead.org" 
        <linux-snps-arc@...ts.infradead.org>
Subject: Specifying console via "stdout-path" property

Hi everyone,

I got strange results when I tried to specify device to use as console
via "stdout-path" property in device tree:
Even If I specify device in "stdout-path" property first probed device
(of those that can be used as console device) is used as console.

For example:
-------------->8--------
chosen {
    stdout-path = &serial1;
};

serial0: uart0@... {} /* serial0 is used as console (ttyS0) as it is
                       * probed earlier */
serial1: uart1@... {}
-------------->8--------

So I am wondering is it expected behavior?


Everything is fine if I specify uart device via "console" parameter in
bootargs:
-------------->8--------
chosen {
    bootargs = "console=ttyS1"
    stdout-path = &serial1;
};

serial0: uart0@... {}
serial1: uart1@... {} /* serial1 is used as console (ttyS1) */
-------------->8--------

Thanks.
-- 
 Eugeniy Paltsev