Xref: utzoo comp.unix.xenix:3720 comp.unix.wizards:11887
Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!ames!husc6!bloom-beacon!arktouros!dyer
From: dyer@arktouros.MIT.EDU (Steve Dyer)
Newsgroups: comp.unix.xenix,comp.unix.wizards
Subject: Re: Need help with serial line device driver
Keywords: How to get data to another Driver ?
Message-ID: <7596@bloom-beacon.MIT.EDU>
Date: 21 Oct 88 15:44:26 GMT
References: <385@ftp.COM> <7581@bloom-beacon.MIT.EDU> <4886@b-tech.ann-arbor.mi.us>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: dyer@arktouros.MIT.EDU (Steve Dyer)
Organization: MIT Project Athena, Cambridge MA 02139
Lines: 22

In article <4886@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
>>You want to define a new TTY line discipline which will make the
>>bytes available to your IP input routine.  This is what's done
>
>I think he is trying to avoid having or writing the tty driver source.
>Can a kernel routine call ttyopen() and ttyread()?  Ar there any PD
>tty drivers for Xenix (or Microport)?

You don't need tty driver source to write a new line discipline.
That's the whole purpose of line disciplines, after all.  You
write your line discipline, add the correct entries to the master
file, and then build a new kernel.

The ttyread and ttywrite routines are assuming transfers to/from
user space, so won't work as you'd like.  A line discipline (or
a STREAMS module if/when we have STREAMS serial devices) is really
the only way to go.  Trying to do what you suggest is as hard, if
not harder, than doing it right.

---
Steve Dyer
dyer@arktouros.MIT.EDU
dyer@spdcc.COM aka {harvard,husc6,ima,bbn,m2c,mipseast}!spdcc!dyer