On Mon, 1 Dec 2014 19:51:18 -0600
Felipe Balbi [off-list ref] wrote:

On Tue, Dec 02, 2014 at 01:13:38AM +0200, Aaro Koskinen wrote:

quoted

Hi,

On Mon, Dec 01, 2014 at 02:09:14PM +0000, One Thousand Gnomes wrote:

quoted

quoted

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

Yes.. and that possibly also means a temporary char driver that claims
ttyO* and simply redirects the calls into the tty.