Lines Matching refs:by

10   An HL-driver can register itself at LL by calling the function
23   separated by slashes:
46     This field has to be set by the HL-driver to the number of channels
48     the LL puts an id there, which has to be used by the HL-driver when
55     Also to be preset by the HL-driver. With this value the HL-driver
60     To be preset by the HL-driver. Using this field, the HL-driver
72     To be preset by the HL-driver, if it supports sk_buff's. The driver
81     This field will be set by LL. The HL-driver delivers received data-
82     packets by calling this function. Upon calling, the HL-driver must
92     This field will be set by LL. This function has to be called by the
112     This field has to be preset by the HL-driver. It points to a function,
113     to be called by LL to perform functions like dialing, B-channel
132     This field has to be preset by the HL-driver. The given function will
133     be called by the LL for delivering data to be send via B-Channel.
141 		       by sending an ISDN_STAT_BSENT. If this is 0, the driver
152     This field has to be preset by the HL-driver. The given function will be
156     and never will be called by the tty-emulation- or network-code. If
176     This field has to be preset by the HL-driver. The given function will be
180     and never will be called by the tty-emulation- or network-code. If
201    This string has to be preset by the HL-driver. Its purpose is for
202    identification of the driver by the user. Eg.: it is shown in the
205    given, upon return, isdn4linux will replace it by a generic name. (line0,
212    All commands will be performed by calling the function command() described
219 ***CHANGEI1.34: The parameter "num" has been replaced by a union "parm" containing
362     protocol. This command is issued by the LL prior to ISDN_CMD_DIAL or
390     protocol. This command is issued by the LL prior to ISDN_CMD_DIAL or
478 3. Description of the events to be signaled by the HL-driver to the LL.
482   to be set by the HL-driver with the appropriate Status-Id (event-number).
594    or caused by a remote-hangup or if the remote-station has actively
607    or caused by a remote-hangup.
645     This callback is used by the network-interfaces only, tty-Emulation