[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141202015118.GA1891@saruman>
Date: Mon, 1 Dec 2014 19:51:18 -0600
From: Felipe Balbi <balbi@...com>
To: Aaro Koskinen <aaro.koskinen@....fi>
CC: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
Tony Lindgren <tony@...mide.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
<linux-serial@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
<linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
Sekhar Nori <nsekhar@...com>, Felipe Balbi <balbi@...com>,
<uwe@...ine-koenig.org>
Subject: Re: [PATCH] tty: serial: serial-omap: depend on !8250_omap
On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:
> Hi,
>
> On Mon, Dec 01, 2014 at 02:09:14PM +0000, One Thousand Gnomes wrote:
> > > Well the nightmare userspace switch from ttyS to ttyO few years ago is
> > > something we want to avoid.. I think the best solution would be to make
> > > serial-omap.c transparently provide support for ttyO using the new 8250
> > > code so both ttyS and ttyO devices would just work. Otherwise it will
> > > be years of "my serial port stopped working" questions again.
> >
> > Thata a udev problem not a kernel one surely.
>
> People also use serial console to observe the early kernel boot before
> the userspace is started.
right, we need a way to tell the kernel that ttyO%d and ttyS%d are the
exact same device so that console=ttyO0 and console=ttyS0 mean the same
thing. That maintains backwards compatibility and lets people move on
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists