Messages in this thread |  | | Date | Sat, 31 Aug 2002 00:36:18 +0200 | From | Vojtech Pavlik <> | Subject | Re: [PATCH] 2.5.31-serport |
| |
On Fri, Aug 30, 2002 at 03:03:59PM -0700, David S. Miller wrote: > From: Russell King <rmk@arm.linux.org.uk> > Date: Fri, 30 Aug 2002 22:39:11 +0100 > > 2. What happens if I open and try to read from this port while something > has the serport_ldisc attached? I suspect that you'll create nice > loop of serio devices in serio.c and an infinite loop when you try to > traverse the list to remove a different serio device. > > SERIO devices are not meant to be registered as normal TTYs. > At least I don't do this for any of the Sparc serial ports > when they are the keyboard/mouse serio device.
No, but using serport.c, you can bind a serio to a tty via a line discipline, for example if you want a PC serial mouse on /dev/ttyS0 to talk to sermouse.c via serio. I don't like the approach much, I hope(d) we could switch somewhere below the tty layer, but it sort of works, and maybe will have the bugs fixed sooner or later.
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |