Xref: utzoo comp.unix.xenix:3719 comp.unix.wizards:11885
Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ames!mailrus!ncar!tank!oddjob!matt
From: matt@oddjob.uchicago.edu (Matt Crawford)
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: <477@tank.uchicago.edu>
Date: 21 Oct 88 17:36:56 GMT
References: <385@ftp.COM> <7581@bloom-beacon.MIT.EDU> <4886@b-tech.ann-arbor.mi.us>
Sender: news@tank.uchicago.edu
Reply-To: matt@oddjob.uchicago.edu (Matt Crawford)
Followup-To: comp.unix.xenix
Organization: Morse Science High School
Lines: 16

) >In article <385@ftp.COM> bill@ftp.COM (Bill Lampman) writes:
) >>kernel code for demultiplexing and checksumming, etc.  Does anyone know
) >>how I can access the serial line data without having a daemon running to
) >>read the data and then write it back to the kernel ? This scheme would

	[ two responses deleted ]

I think the answers I've seen are on the wrong track.  I believe Bill
just needs to know how to have his driver put the received packet on the
input queue for the IP module.  I don't know Xenix so I can't give an
exact answer, but in 4.[23] the device driver checks to see whether the
IP input queue is full and, if it isn't, places the new packet on the
queue and sets a bit or tickles a software interrupt so that the IP
module will examine its input queue in the near future.  Look for macros
or functions with names like IF_ENQUEUE or schednetisr.  (Then try to
guess how they work!)
				Matt Crawford