Lines Matching refs:Kernel

2 Kernel CAPI Interface to Hardware Drivers
13 Kernel CAPI operates as a dispatching layer between CAPI applications and CAPI
15 lingo) with Kernel CAPI to indicate their readiness to provide their service
16 to CAPI applications. CAPI applications also register with Kernel CAPI,
17 requesting association with a CAPI device. Kernel CAPI then dispatches the
19 corresponding hardware driver. Kernel CAPI then forwards CAPI messages in both
29 CAPI drivers must register each of the ISDN devices they control with Kernel
30 CAPI by calling the Kernel CAPI function attach_capi_ctr() with a pointer to a
33 pointers which are subsequently used by Kernel CAPI for communicating with the
40 From then on, Kernel CAPI may call the registered callback functions for the
45 callback functions by Kernel CAPI.
51 Kernel CAPI forwards registration requests from applications (calls to CAPI
54 allocated by Kernel CAPI and passed to register_appl() along with the
60 send_message() callback function. Conversely, the driver may call Kernel
62 Kernel CAPI for forwarding to an application, specifying its ApplID.
76 This structure describes a Kernel CAPI driver itself. It is used in the
89 This structure describes an ISDN device (controller) handled by a Kernel CAPI
103 	an opaque pointer to driver specific data, not touched by Kernel CAPI
136 	Calls to these functions are serialized by Kernel CAPI so that only
143 	Calls to these functions are serialized by Kernel CAPI so that only
164 	Calls to this function are not serialized by Kernel CAPI, ie. it must
194 CAPI messages are passed between Kernel CAPI and the driver via send_message()
263 register/unregister a device (controller) with Kernel CAPI
277 pass a received CAPI message to Kernel CAPI