Lines Matching refs:be

4 The "concap" interface is intended to be used by network device
12 also be useful to other kinds of network devices. Thus, if you want
43    The configurability of the encapsulation protocol to be used
52 negotiation before the first piece of user data can be transmitted.
55 code for typical WAN devices also tends to be more complex.
64 protocol, complexity could be reduced and maintainability could be
68 Likewise, a similar encapsulation protocol will frequently be needed by
73 from the hardware specific interface stuff such code could be shared
82 is provided) is outside our scope and might be different depending on
114 	   cprot may no longer be referenced after calling this */
117 	/* initialize the protocol's data. To be called at interface startup
119 	   encapsulation protocol may be used after this*/
131 	/* to be called for each data entity received from lower layer*/ 
134 	/* to be called when a connection was set up/down.
157 	/* to request data be submitted by device */ 
160 	/* Control methods must be set to NULL by devices which do not
162 	/* to request a connection be set up */ 
165 	/* to request a connection be released */
182 					   be accessed via *pops methods only*/
191 be reset (opend). The network interface must provide the net_dev and
192 dops pointers. Other concap_proto members should be considered private
220 performance. However, typically the concap interface will be used by
229 then the interface of the service function could be changed
248 The device's data request function could also be defined as