Lines Matching full:module

4 The Linux LAPB Module Interface
13 The LAPB module will be a separately compiled module for use by any parts of
15 defines the interfaces to, and the services provided by this module. The
16 term module in this context does not imply that the LAPB module is a
17 separately loadable module, although it may be. The term module is used in
20 The interface to the LAPB module consists of functions to the module,
21 callbacks from the module to indicate important state changes, and
22 structures for getting and setting information about the module.
34 module and is not for use.
41 of the LAPB module::
53 that is called when a particular event in the LAPB module occurs. These will
109 The LAPB module provides a number of function entry points.
115 This must be called before the LAPB module may be used. If the call is
118 instance of the LAPB link. It is returned by the LAPB module in all of the
119 callbacks, and is used by the device driver in all calls to the LAPB module.
183 LAPB_CONNECTED		LAPB module is already connected.
195 LAPB_NOTCONNECTED	LAPB module is not connected.
202 Queue data with the LAPB module for transmitting over the link. If the call
203 is successful then the skbuff is owned by the LAPB module and may not be
209 LAPB_NOTCONNECTED	LAPB module is not connected.
216 Queue data with the LAPB module which has been received from the device. It
217 is expected that the data passed to the LAPB module has skb->data pointing
219 is owned by the LAPB module and may not be used by the device driver again.
231 module to call when an event occurs. They are registered with the LAPB
232 module with lapb_register (see above) in the structure lapb_register_struct
239 This is called by the LAPB module when a connection is established after
247 This is called by the LAPB module when the link is established by the remote
254 This is called by the LAPB module when an event occurs after the device
270 This is called by the LAPB module when the link is terminated by the remote
288 This is called by the LAPB module when data has been received from the
291 module will not perform any more actions on it. The skb->data pointer will
302 This is called by the LAPB module when data is to be transmitted to the
304 device driver and the LAPB module will not perform any more actions on it.