[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfLk7_79akWb=t1BMii1jtBxzcEcYoBH7AmA8+Gh03icQ@mail.gmail.com>
Date: Tue, 11 Mar 2025 21:50:31 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: adamsimonelli@...il.com
Cc: linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
Jiri Slaby <jirislaby@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Steven Rostedt <rostedt@...dmis.org>, John Ogness <john.ogness@...utronix.de>,
Sergey Senozhatsky <senozhatsky@...omium.org>, Petr Mladek <pmladek@...e.com>
Subject: Re: [PATCH v8 0/4] Optionally allow ttynull to be selected as a
default console
On Tue, Mar 11, 2025 at 5:31 AM <adamsimonelli@...il.com> wrote:
>
> From: Adam Simonelli <adamsimonelli@...il.com>
>
> When switching to a CONFIG_VT=n world, at least on x86 systems,
> /dev/console becomes /dev/ttyS0. This can cause some undesired effects.
> /dev/console's behavior is now tied to the physical /dev/ttyS0, which when
> disconnected can cause isatty() to fail when /dev/ttyS0 is disconnected,
> and users who upgrade to a theoretical vt-less kernel from their
> distribution who have a device such as a science instrument connected to
> their /dev/ttyS0 port will suddenly see it receive kernel log messages.
>
> When the new CONFIG_NULL_TTY_DEFAULT_CONSOLE option is turned on, this will
> allow the ttynull device to be leveraged as the default console. Distributions
> that had CONFIG_VT turned on before will be able to leverage this option
> to where /dev/console is still backed by a psuedo device, avoiding these
pseudo
> issues, without needing to enable the entire VT subsystem.
LGTM, so FWIW,
Acked-by: Andy Shevchenko <andy@...nel.org>
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists