how to invoke canonical processing in kernel

how to invoke canonical processing in kernel

[Puneet Jain]

I am trying to figure out the correct approach a porting issue I am
dealing
with and would appreciate any pointers.

I am working on porting one of our communication products which works on
a
variety of OSs including Solaris, AIX etc to Linux. Basically the
product
provides a raw and canonical terminal interface to the applications and
has been implemented in STREAMS framework.

I have downloaded the LiS - Linux STREAMS (implemented by Dave Grothe)
from gcom.com. The only problem is that it is does not have any support
for terminal I/O
subsystem. So the processing that was handled by the 'ldterm' module on
other OSs now has to be handled by the available line disciplines in the
Linux kernel. While browsing the source I noticed that the default line
discipline N_TTY is probably sufficient to do the job but I am not sure
of the hooks. I am wondering if I can invoke the default line discipline
somehow or would I have to implement the canonical processing all over
again.

Any suggestions would be greatly appreciated.

Thanks,
Puneet

Re: how to invoke canonical processing in kernel

[Alan Cox]

> subsystem. So the processing that was handled by the 'ldterm' module on
> other OSs now has to be handled by the available line disciplines in the
> Linux kernel. While browsing the source I noticed that the default line

Linux is based on the BSD codebase. The streams disaster was one we chose
to skip over and ignore

> discipline N_TTY is probably sufficient to do the job but I am not sure
> of the hooks. I am wondering if I can invoke the default line discipline
> somehow or would I have to implement the canonical processing all over
> again.

Canonical processing is always part of the tty driver. The POSIX 
tcsetattr/tcgetattr calls let you configure which parts of it you need
(eg line processing, echo, character by character input etc)

Alan

Re: how to invoke canonical processing in kernel

[Alan Cox]

> Linux is based on the BSD codebase. The streams disaster was one we chose
> to skip over and ignore

Codebase.. Umm perils of processing 3000 emails in a row. Philosophy is of
course what I mean here