Lines Matching +full:system +full:- +full:on +full:- +full:module

1 		The Linux LAPB Module Interface 1.3
5 Changed (Henner Eisen, 2000-10-29): int return value for data_indication() 
7 The LAPB module will be a separately compiled module for use by any parts of
8 the Linux operating system that require a LAPB service. This document
9 defines the interfaces to, and the services provided by this module. The
10 term module in this context does not imply that the LAPB module is a
11 separately loadable module, although it may be. The term module is used in
14 The interface to the LAPB module consists of functions to the module,
15 callbacks from the module to indicate important state changes, and
16 structures for getting and setting information about the module.
19 ----------
28 module and is not for use.
31 -----------------------------
35 of the LAPB module.
47 that is called when a particular event in the LAPB module occurs. These will
53 ------------------------
72 is the maximum number of tries on the link before it is declared a failure.
85 3-31	Reserved, must be 0.
98 ---------
100 The LAPB module provides a number of function entry points.
105 This must be called before the LAPB module may be used. If the call is
108 instance of the LAPB link. It is returned by the LAPB module in all of the
109 callbacks, and is used by the device driver in all calls to the LAPB module.
160 LAPB_CONNECTED		LAPB module is already connected.
169 LAPB_NOTCONNECTED	LAPB module is not connected.
174 Queue data with the LAPB module for transmitting over the link. If the call
175 is successful then the skbuff is owned by the LAPB module and may not be
180 LAPB_NOTCONNECTED	LAPB module is not connected.
185 Queue data with the LAPB module which has been received from the device. It
186 is expected that the data passed to the LAPB module has skb->data pointing
188 is owned by the LAPB module and may not be used by the device driver again.
196 ---------
199 module to call when an event occurs. They are registered with the LAPB
200 module with lapb_register (see above) in the structure lapb_register_struct
206 This is called by the LAPB module when a connection is established after
213 This is called by the LAPB module when the link is established by the remote
214 system. The value of reason is always LAPB_OK.
219 This is called by the LAPB module when an event occurs after the device
225 LAPB_NOTCONNECTED	The remote system was not connected.
227 			system.
232 This is called by the LAPB module when the link is terminated by the remote
233 system or another event has occurred to terminate the link. This may be
235 system refused the request. The values for reason are:
238 			system.
239 LAPB_REFUSED		The remote system refused the connect request.
240 LAPB_NOTCONNECTED	The remote system was not connected.
242 			system.
247 This is called by the LAPB module when data has been received from the
248 remote system that should be passed onto the next layer in the protocol
250 module will not perform any more actions on it. The skb->data pointer will
260 This is called by the LAPB module when data is to be transmitted to the
261 remote system by the device driver. The skbuff becomes the property of the
262 device driver and the LAPB module will not perform any more actions on it.
263 The skb->data pointer will be pointing to the first byte of the LAPB header.