Lines Matching full:lapb
4 The Linux LAPB Module Interface
13 The LAPB module will be a separately compiled module for use by any parts of
14 the Linux operating system that require a LAPB service. This document
16 term module in this context does not imply that the LAPB module is a
20 The interface to the LAPB module consists of functions to the module,
31 The two LAPB specific structures are the LAPB initialisation structure and
32 the LAPB parameter structure. These will be defined in a standard header
33 file, <linux/lapb.h>. The header file <net/lapb.h> is internal to the LAPB
36 LAPB Initialisation Structure
41 of the LAPB module::
53 that is called when a particular event in the LAPB module occurs. These will
58 LAPB Parameter Structure
63 operational parameters of the LAPB implementation for a given connection::
81 and 7 for a standard LAPB link, and between 1 and 127 for an extended LAPB
90 0 LAPB operation (0=LAPB_STANDARD 1=LAPB_EXTENDED).
91 1 [SM]LP operation (0=LAPB_SLP 1=LAPB=MLP).
96 Extended LAPB operation indicates the use of extended sequence numbers and
97 consequently larger window sizes, the default is standard LAPB operation.
99 LAPB are different to indicate the mode of operation, the default is Single
103 names will be defined in the public LAPB header file.
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.
120 For multiple LAPB links in a single device driver, multiple calls to
125 LAPB_OK LAPB registered successfully.
134 This releases all the resources associated with a LAPB link. Any current
135 LAPB link will be abandoned without further messages being passed. After
136 this call, the value of token is no longer valid for any calls to the LAPB
140 LAPB_OK LAPB unregistered successfully.
141 LAPB_BADTOKEN Invalid/unknown LAPB token.
148 This allows the device driver to get the values of the current LAPB
153 LAPB_OK LAPB getparms was successful.
154 LAPB_BADTOKEN Invalid/unknown LAPB token.
161 This allows the device driver to set the values of the current LAPB
168 LAPB_OK LAPB getparms was successful.
169 LAPB_BADTOKEN Invalid/unknown LAPB token.
181 LAPB_OK LAPB is starting to connect.
182 LAPB_BADTOKEN Invalid/unknown LAPB token.
183 LAPB_CONNECTED LAPB module is already connected.
193 LAPB_OK LAPB is starting to disconnect.
194 LAPB_BADTOKEN Invalid/unknown LAPB token.
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
207 LAPB_OK LAPB has accepted the data.
208 LAPB_BADTOKEN Invalid/unknown LAPB token.
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
218 to the beginning of the LAPB data. If the call is successful then the skbuff
219 is owned by the LAPB module and may not be used by the device driver again.
223 LAPB_OK LAPB has accepted the data.
224 LAPB_BADTOKEN Invalid/unknown LAPB token.
230 These callbacks are functions provided by the device driver for the LAPB
231 module to call when an event occurs. They are registered with the LAPB
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
256 what has happened. In all cases the LAPB link can be regarded as being
260 LAPB_OK The LAPB link was terminated normally.
270 This is called by the LAPB module when the link is terminated by the remote
276 LAPB_OK The LAPB link was terminated normally by the remote
288 This is called by the LAPB module when data has been received from the
290 stack. The skbuff becomes the property of the device driver and the LAPB
292 be pointing to the first byte of data after the LAPB header.
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.
305 The skb->data pointer will be pointing to the first byte of the LAPB header.