Message-ID:	<3743A7DB.57503DD2@your.clothes.home.com>
From:	Steve Wallace <kerfer AT home DOT com>
Organization:	0 Entropy: Increasing
X-Mailer:	Mozilla 4.5 [en]C-AtHome0405 (Win95; U)
X-Accept-Language:	en
MIME-Version:	1.0
Newsgroups:	comp.os.msdos.djgpp
Subject:	SVAync Sanity Check.
Lines:	38
Date:	Thu, 20 May 1999 06:11:47 GMT
NNTP-Posting-Host:	24.4.71.21
X-Complaints-To:	abuse AT home DOT net
X-Trace:	news.rdc1.sdca.home.com 927180707 24.4.71.21 (Wed, 19 May 1999 23:11:47 PDT)
NNTP-Posting-Date:	Wed, 19 May 1999 23:11:47 PDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

To Sam Vincent, or anyone else that can answer this:

I downloaded the SVAsync package, and it looks like it will 
do what I need it to do, with one small problem...I am trying 
to use it as a physical layer protocol driver, so I need a
callback routine to an upper layer from the receive side.

Simple enough...I added a routine called SVAsyncCBHook
to SVAsync.c which is called by the receive ISR in isr.s,
the idea being that the higher layer will register a callback
routine, which will then be called by SVAsyncCBHook() on behalf
of the ISR: The idea being to assemble received data characters
into packets, and strip the headers/trailers, check CRCs, and
that sort of thing.

Anybody see any problem with this approach?  Other than the
possible problem of staying in an ISR an arguably long time?
Is *that* a problem on a PC, given that I'm not doing anything
else anyway?

I'm not a PC wienie, so if this is completely off the wall,
that may be why.  ;^>

Thanks in advance for your help.

Oh yeah...Sam: Thanks for all your hard work.  It looks like
you've saved me a lot of time (unless the group tells me that
what I'm doing won't work, in which case, thanks for all your
hard work when I use this in the future ;^>).

-- 
Later.
Steve.
-- 
"Buy the best and only cry once"

For my proper E-mail address, please remove 
'your.clothes.'  Spammers suck.

- Raw text -