From: Andy Shevchenko <andy.shevchenko@gmail.com> To: Alper Nebi Yasak <alpernebiyasak@gmail.com> Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Jiri Slaby <jslaby@suse.com>, Petr Mladek <pmladek@suse.com>, "open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>, Steven Rostedt <rostedt@goodmis.org>, linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@linux-foundation.org>, Andy Shevchenko <andriy.shevchenko@linux.intel.com>, Arvind Sankar <nivedita@alum.mit.edu>, Benjamin Herrenschmidt <benh@kernel.crashing.org>, Daniel Vetter <daniel.vetter@ffwll.ch>, "David S. Miller" <davem@davemloft.net>, Eric Biggers <ebiggers@google.com>, Feng Tang <feng.tang@intel.com>, Grzegorz Halat <ghalat@redhat.com>, Lukas Wunner <lukas@wunner.de>, Nicolas Pitre <nico@fluxnic.net>, Sam Ravnborg <sam@ravnborg.org> Subject: Re: [RFC PATCH v2 0/3] Prefer working VT console over SPCR and device-tree chosen stdout-path Date: Fri, 1 May 2020 16:16:33 +0300 [thread overview] Message-ID: <CAHp75VeZRwUp+CpOct4dCAQAfyJZBAY7=qSKwRQh935KEMWw+g@mail.gmail.com> (raw) In-Reply-To: <818ba356-ba35-68de-b7bf-f145a89280f1@gmail.com> On Fri, May 1, 2020 at 2:11 PM Alper Nebi Yasak <alpernebiyasak@gmail.com> wrote: > On 01/05/2020 04:30, Sergey Senozhatsky wrote: > I'm assuming "by default" here means "without console arguments" > regardless of firmware requests. This paragraph (with small changes) is > repeated on many other Kconfig descriptions (drivers/tty/serial/Kconfig, > drivers/tty/serial/8250/Kconfig, arch/sparc/Kconfig from grepping for > '/dev/tty0' on **/Kconfig). > > From Documentation/admin-guide/serial-console.rst: > > > You can specify multiple console= options on the kernel command line. > > [...] > > Note that you can only define one console per device type (serial, video). > > > > If no console device is specified, the first device found capable of > > acting as a system console will be used. At this time, the system > > first looks for a VGA card and then for a serial port. So if you don't > > have a VGA card in your system the first serial port will automatically > > become the console. > > and later on: > > > Note that if you boot without a ``console=`` option (or with > > ``console=/dev/tty0``), ``/dev/console`` is the same as ``/dev/tty0``. > > In that case everything will still work. I'm wondering if behaviour is changed if you put console=tty1 instead of console=tty0. -- With Best Regards, Andy Shevchenko
next prev parent reply other threads:[~2020-05-01 13:16 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-30 16:14 Alper Nebi Yasak 2020-04-30 16:14 ` [RFC PATCH v2 1/3] printk: Add function to set console to preferred console's driver Alper Nebi Yasak 2020-04-30 16:46 ` Andy Shevchenko 2020-05-01 1:44 ` Sergey Senozhatsky 2020-05-01 11:48 ` Alper Nebi Yasak 2020-05-13 5:35 ` Sergey Senozhatsky 2020-05-24 10:01 ` Daniel Vetter 2020-04-30 16:14 ` [RFC PATCH v2 2/3] vt: Set as preferred console when a non-dummy backend is bound Alper Nebi Yasak 2020-04-30 16:14 ` [RFC PATCH v2 3/3] printk: Preset tty0 as a pseudo-preferred console Alper Nebi Yasak 2020-04-30 16:44 ` [RFC PATCH v2 0/3] Prefer working VT console over SPCR and device-tree chosen stdout-path Andy Shevchenko 2020-04-30 19:32 ` Alper Nebi Yasak 2020-05-01 1:30 ` Sergey Senozhatsky 2020-05-01 11:08 ` Alper Nebi Yasak 2020-05-01 13:16 ` Andy Shevchenko [this message] 2020-05-01 15:07 ` Alper Nebi Yasak 2020-05-13 14:37 ` Petr Mladek 2020-05-13 22:22 ` Benjamin Herrenschmidt 2020-05-15 19:27 ` Alper Nebi Yasak 2020-05-25 13:04 ` Petr Mladek
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='CAHp75VeZRwUp+CpOct4dCAQAfyJZBAY7=qSKwRQh935KEMWw+g@mail.gmail.com' \ --to=andy.shevchenko@gmail.com \ --cc=akpm@linux-foundation.org \ --cc=alpernebiyasak@gmail.com \ --cc=andriy.shevchenko@linux.intel.com \ --cc=benh@kernel.crashing.org \ --cc=daniel.vetter@ffwll.ch \ --cc=davem@davemloft.net \ --cc=ebiggers@google.com \ --cc=feng.tang@intel.com \ --cc=ghalat@redhat.com \ --cc=gregkh@linuxfoundation.org \ --cc=jslaby@suse.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-serial@vger.kernel.org \ --cc=lukas@wunner.de \ --cc=nico@fluxnic.net \ --cc=nivedita@alum.mit.edu \ --cc=pmladek@suse.com \ --cc=rostedt@goodmis.org \ --cc=sam@ravnborg.org \ --cc=sergey.senozhatsky@gmail.com \ --subject='Re: [RFC PATCH v2 0/3] Prefer working VT console over SPCR and device-tree chosen stdout-path' \ /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
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).