[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150108223626.43fd93d5@lxorguk.ukuu.org.uk>
Date: Thu, 8 Jan 2015 22:36:26 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Arnd Bergmann <arnd@...db.de>
Cc: Peter Hurley <peter@...leysoftware.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.cz>, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Tony Lindgren <tony@...mide.com>,
Grant Likely <grant.likely@...aro.org>
Subject: Re: [PATCH] serial: 8250: Make ISA ports optional
> One idea that has come up in the past but never saw an implementation
> is to make the ttyS namespace and minor numbers completely generic and
> let any serial port driver use it. This would be a major rework, but
> have the added advantage of cleaning up a number of other namespace
> issues as well. There also lots of open question, in particular how
> to maintain compatibility with existing drivers. One could imagine
> that each uart always gets a ttyS device and optionally also gets
> a device node for the same port with a driver specific chardev as
> most of them do today. Or it could be an either/or decision that is
> made at compile time or as a module parameter.
I'm not sure we should use ttyS for it. ttyS means 8250, a lot of
existing code knows what ttyS is and what sort of ioctls and the like are
assumed. A generic namespace needs not to be attached to a legacy naming
(eg also put all serial ports in /dev/serial/0 /dev/serial/1 etc either
via the tty layer or via systemd/udev)
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists