> From: alan@lxorguk.ukuu.org.uk (Alan Cox)
> Date: Fri, 27 Feb 1998 10:45:38 +0000 (GMT)
>
> > routing all tty IO through EvStack, ever. Only serial lines that are
> > somehow (?) dedicated as keyboard input devices feed into EvStack and
> > bypass the tty line
> > disc. layer directly. Jason even gave a pseudo patch later:
>
> I assume what you are actually doing is making your GGI-Keyboard a
> line discipline in itself like PPP, SLIP, tty - which is nice and clean
>
> A line discpline in itself is *not* clean, since it would require
> replicating the N_TTY code in their line discpline.
[clip as Alan Cox's answer is quite fine :]
> That is, a tty line discpline is for a specific line discpline.
> However, if you're sending raw keycodes to the line discpline, you
> haven't yet done the dispatch of which console tty should be receiving the
> input (and which keycodes means "switch to VC #3", etc.). Doing the
> dispatch of which tty the keycodes should go to within the tty line
> discpline is very unclean.
It's no different from arbitrating which console gets keyboard input.
Think about it a bit - there's only one keyboard and display on most
systems, yet we have all of these virtual-terminals... *grin*
(there's also PPP if you think about it... All those network connections
through one serial line... and multi-serial PPP afaik IS supported [at
least in the ISDN-PPP drivers if nowhere else])
> It's not at all clear people are thinking through all of the
> implications here --- possibly, they're not explaining it clearly or I'm
> not understanding what they're trying to do, but I see some real
> problems here.
RTFM (wherever the EvStack mailinglist is stored) *grin*... We have
thought about it... LOTS. Still implementing it though mind you *grin*
G'day, eh? :)
- Teunis
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu