BSP Developer's Guide

H
Implementing a MUX-Based Network Interface Driver
mib2Tbl
An M2_INTERFACETBL structure for tracking the MIB-II variables used in
your driver. Your driver must initialize the structure referenced here, although
both your driver and the MUX will later adjust the values stored in the table.
NOTE: The mib2Tbl field is retained for backwards compatibility with RFC 1213.
It is not recommended for new drivers. For new drivers, use the RFC 2233
interface. For more information, see H.7 Converting an END Driver from RFC 1213
to RFC 2233, p.311.
pAddrList
A pointer to the head of a list of multicast addresses. The MUX sets and
manages this list, but it uses your driver’s endMCastAddrAdd( ),
endMCastAddrDel( ), and endMCastAddrGet( ) entry points to do so.
nMulti
A value indicating the number of addresses on the list referenced in the
multiList member. The MUX sets this value using the information returned by
your driver’s endMCastAddrGet( ).
protocols
The head of the list of protocols that have bound themselves to this network
driver. The MUX manages this list.
snarfProto
A BOOL indicating whether a packet-snarfing protocol has bound itself to this
driver. Such a protocol can prevent the packet from passing on to lower
priority protocols (see Snarfing Protocols Block Packets to Lower Priority Protocols,
p.302). The MUX sets and manages this value.
pMemPool
A pointer to a netBufLib-managed memory pool. The MUX sets the value of
this member. Treat it as opaque.
pMib2Tbl
The interface table for RFC 2233 compliance.
H
Tracking Your Device’s Control Structure: DEV_OBJ
Your driver uses the DEV_OBJ structure to tell the MUX the name of your device
and to hand the MUX a pointer to your device’s control structure. This control
structure is a device-specific structure that you define according to your needs.
Your driver uses this control structure to track things such as flags, memory pool
285