[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wjDFKGABDe7w-=HsiUr7f=CpbmR3bPf2UL-1dPcWRYW9g@mail.gmail.com>
Date: Fri, 24 Feb 2023 14:57:57 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Tharun Kumar P <tharunkumar.pasumarthi@...rochip.com>,
Kumaravel Thiagarajan <kumaravel.thiagarajan@...rochip.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Jiri Slaby <jslaby@...e.cz>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [GIT PULL] TTY/Serial driver updates for 6.3-rc1
On Fri, Feb 24, 2023 at 2:32 PM Al Viro <viro@...iv.linux.org.uk> wrote:
>
> > It's probably most legacy by now - it's a long time since I saw a
> > serial port being used outside of management ports, and even those are
> > often ethernet these days.
>
> Serial console is hard to replace
Yeah, but I don't think that should make it "default on" just because
somebody picked 8250.
I may have 8250 in my old config for my own legacy reasons, that
doesn't mean that when I upgrade a kernel, it should default new
drivers to be enabled too. My old legacy 8250 history does *not*
suddenly grow new hardware.
Side note: we have *truly* legacy things like that
SERIAL_8250_DEPRECATED_OPTIONS thing, which also - for historical
reasons - is "default y".
I guess that's just another sign of the whole "this is legacy" thing.
Linus
Powered by blists - more mailing lists