Lines Matching refs:the

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
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.
21 Probably the most important structure is the skbuff structure for holding
22 received and transmitted data, however it is beyond the scope of this
25 The two LAPB specific structures are the LAPB initialisation structure and
26 the LAPB parameter structure. These will be defined in a standard header
27 file, <linux/lapb.h>. The header file <net/lapb.h> is internal to the LAPB
33 This structure is used only once, in the call to lapb_register (see below).
34 It contains information about the device driver that requires the services
35 of the LAPB module.
46 Each member of this structure corresponds to a function in the device driver
47 that is called when a particular event in the LAPB module occurs. These will
55 This structure is used with the lapb_getparms and lapb_setparms functions
56 (see below). They are used to allow the device driver to get and set the
57 operational parameters of the LAPB implementation for a given connection.
72 is the maximum number of tries on the link before it is declared a failure.
73 The window size is the maximum number of outstanding data packets allowed to
74 be unacknowledged by the remote end, the value of the window is between 1
79 The bit fields have the following meanings:
87 Extended LAPB operation indicates the use of extended sequence numbers and
88 consequently larger window sizes, the default is standard LAPB operation.
89 MLP operation is the same as SLP operation except that the addresses used by
90 LAPB are different to indicate the mode of operation, the default is Single
91 Link Procedure. The difference between DCE and DTE operation is (i) the
92 addresses used for commands and responses, and (ii) when the DCE is not
94 names will be defined in the public LAPB header file.
105 This must be called before the LAPB module may be used. If the call is
107 generated by the device driver to allow for the unique identification of the
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.
111 lapb_register must be made. The format of the lapb_register_struct is given
121 This releases all the resources associated with a LAPB link. Any current
123 this call, the value of token is no longer valid for any calls to the LAPB
132 This allows the device driver to get the values of the current LAPB
133 variables, the lapb_parms_struct is described above. The valid return values
142 This allows the device driver to set the values of the current LAPB
143 variables, the lapb_parms_struct is described above. The values of t1timer,
144 t2timer and n2count are ignored, likewise changing the mode bits when
145 connected will be ignored. An error implies that none of the values have
150 LAPB_INVALUE		One of the values was out of its allowable range.
155 Initiate a connect using the current parameter settings. The valid return
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
176 used by the device driver again. The valid return values are:
178 LAPB_OK			LAPB has accepted the data.
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
187 to the beginning of the LAPB data. If the call is successful then the skbuff
188 is owned by the LAPB module and may not be used by the device driver again.
191 LAPB_OK			LAPB has accepted the data.
198 These callbacks are functions provided by the device driver for the LAPB
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
219 This is called by the LAPB module when an event occurs after the device
221 what has happened. In all cases the LAPB link can be regarded as being
226 LAPB_TIMEDOUT		No response was received in N2 tries from the remote
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
234 returned in response to a lapb_connect_request (see above) if the remote
235 system refused the request. The values for reason are:
237 LAPB_OK			The LAPB link was terminated normally by the remote
239 LAPB_REFUSED		The remote system refused the connect request.
241 LAPB_TIMEDOUT		No response was received in N2 tries from the remote
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
249 stack. The skbuff becomes the property of the device driver and the LAPB
251 be pointing to the first byte of data after the LAPB header.
253 This method should return NET_RX_DROP (as defined in the header
254 file include/linux/netdevice.h) if and only if the frame was dropped
255 before it could be delivered to the upper layer.
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.