Lines Matching refs:with

13 lingo) with Kernel CAPI to indicate their readiness to provide their service
14 to CAPI applications. CAPI applications also register with Kernel CAPI,
15 requesting association with a CAPI device. Kernel CAPI then dispatches the
26 CAPI drivers optionally register themselves with Kernel CAPI by calling the
27 Kernel CAPI function register_capi_driver() with a pointer to a struct
28 capi_driver. This structure must be filled with the name and revision of the
31 with a pointer to the same struct capi_driver.
33 CAPI drivers must register each of the ISDN devices they control with Kernel
34 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
35 struct capi_ctr before they can be used. This structure must be filled with
37 pointers which are subsequently used by Kernel CAPI for communicating with the
39 detach_capi_ctr() with a pointer to the same struct capi_ctr.
57 allocated by Kernel CAPI and passed to register_appl() along with the
69 ApplID as with register_appl(). After return from release_appl(), no CAPI
132 	applications with the device
144 	The return value should only be used to signal problems with respect
146 	actual processing of the message should be signaled with an
201 parameters, with the following exceptions:
252 	register/unregister a driver with Kernel CAPI
256 	register/unregister a device (controller) with Kernel CAPI
305 Library functions for working with _cmsg structures
319 	with the given values, zeroing the remainder of the structure so only
320 	parameters with non-default values need to be changed before sending
346 logged. The traceflag parameter is initialized with the value of the