Lines Matching refs:by

4 The "concap" interface is intended to be used by network device
6 It is assumed that the protocol interacts with a linux network device by
28 encapsulation protocols. The encapsulation protocol is configured by a
35 encapsulation is usually done by just sticking a header on the data. Thus,
37 encapsulation protocol directly (usually by just providing a hard_header()
62 isdn_net.c harder to maintain. Thus, by identifying an abstract
68 Likewise, a similar encapsulation protocol will frequently be needed by
70 synchronous ppp implementation used by the isdn driver and the
71 asynchronous ppp implementation used by the ppp driver have a lot of
98 - process (xmit) data handed down by upper protocol layer
105 provided by the encapsulation protocol instance within a
128 	/* process a frame handed down to us by upper layer */
148 - request data being submitted by lower layer (device hardware) 
149 - request a connection being set up by lower layer 
150 - request a connection being released by lower layer
153 provided by the network interface within a struct concap_device_ops.
157 	/* to request data be submitted by device */ 
160 	/* Control methods must be set to NULL by devices which do not
178 	struct concap_device_ops *dops; /* callbacks provided by device */
179  	struct concap_proto_ops  *pops; /* callbacks provided by us */
193 data that are only accessed by the pops callback functions. Likewise,
195 only by means of the callbacks referred to by the dops pointer.
208 	struct concap_proto *cprot;        /* callbacks provided by protocol */
220 performance. However, typically the concap interface will be used by
228 protocols (e.g. by a member struct concap_proto* in struct net_device)
230 by passing a pointer of type (struct net_device*) instead of