On Mar 19, 2010, at 11:21 PM, Masao Uebayashi wrote: > On Sat, Mar 20, 2010 at 2:42 PM, Masao Uebayashi <uebay...@gmail.com> wrote: >> audio(4) and tty(4) are very different from my view; audio(4) has the >> single entry and drivers implement backend. tty(4) is a common >> interface through which kernel accesses serial devices (correct me if >> wrong). >> >> I'm very curious which architecture looks better to you, because I >> have a vague idea to make tty(4) to something like audio(4). > > I've found that FreeBSD's tty(4) is already done so; serial drivers > implement backend interfaces. System calls always go through tty(4)'s > cdevsw. In NetBSD serial drivers have their own cdevsw...
Which is fine if you have one type of serial port, but if you have a mix of devices all providing serial ports how do you know what tty is going to what serial port (especially with multiport serial devices)?
