// Greetings and Salivatations, All!
{
Is anyone familiar with the above?
What I'm looking for, are the specs for the parameters used when registering
a receiving ISR for particular packet types with NE2000.COM.
I can set it to direct all incoming packets to my ISR, however this seems
like a bit much considering that I'm only interested in two particular types
at the moment.
From what I've been able to gather, parameters are set up in registers as
below, followed by a call to the vector NE2000 is using:
dl = Number
ds = Segment addr. of template
si = Offset addr. of template
cx = Template length
es = Segment addr. of receiver ISR
di = Offset addr. of receiver ISR
bx = Packet Type (word)
ah = ACCESS_TYPE (constant; function # of NE2000)
al = CL_ETHERNET (constant; class of network)
With dl = 0, ds/si = NULL, cx = 0, and bx = 0xffff, the call completes
normally, and my ISR is called upon receiving any packet.
Specifing a type other than 0xffff (leaving other values as indicated),
returns an error code claiming a "bad packet type specified."
I've had no luck finding any further documentation. :-( Can anyone point out
the proper usage of the Number, Packet Template, and Template length
parameters? It strikes me as overkill to receive everything and filter types
via software if the hardware has the same capability in the first place...
...and for those of you wondering about on/off topic, I need this to help
smooth out a class I'm writing to perform as an Ethernet packet engine. :-)
};
// Don
... DEC: Do Expect Cuts
---
---------------
* Origin: Extreme Impossibility/2 שש 547-1469 שש 14.4kbps (1:249/176)
|