[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100831122340.7153388f@lxorguk.ukuu.org.uk>
Date: Tue, 31 Aug 2010 12:23:40 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Rogier Wolff <R.E.Wolff@...Wizard.nl>
Cc: Arnd Bergmann <arnd@...db.de>, Greg KH <gregkh@...e.de>,
Jiri Slaby <jslaby@...e.cz>, linux-kernel@...r.kernel.org,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Mike Frysinger <vapier.adi@...il.com>,
"Michael H. Warfield" <mhw@...tsend.com>
Subject: Re: [RFC 0/5] tty: move stuff around
> Now I've missed the first part of this discussion... Is there a change
> imminent that requires rewriting of all the drivers?
Mostly locking - it's not a trivial entry point thing. The gs layer for
example was full of races and needed rewriting so just got declared
broken.
> (If rewriting serial drivers, PLEASE make it so that the
> userspace-kernel interface just passes a baud rate integer, not the
> one-of-16-possible baudrate-flags. The old stuff can be emulated in a
Did that several years ago. I think you still need to use the ioctl
because several years is apparently a bit short for glibc to get with it
even though a glibc person thought up how to do the new interface 8)
> library. Secondly serial port drivers should NOT have to worry about
> DCD changes and what to do with sleeping processes. The driver should
> have an kernel function to call: "hey, one of the control lines
> changed level. These are the new ones". And "These characters
> arrived". And the driver has an entry point: "please send these
> characters". )
Mostly done. See tty_port_*
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