|
|
ISDN drivers use MDI ioctl system calls for communications between the driver and applications such as dialers and port monitors. MDI ioctl usage in ISDN drivers depends on whether the ioctls:
SCO ISDN-specific ioctls are implementations of CAPI ``operations'':
CAPI operation | MDI/ISDN ioctl |
---|---|
CAPI_REGISTER | ISDN_REGISTER |
CAPI_RELEASE | ISDN_RELEASE |
CAPI_GET_PROFILE | ISDN_GETPROFILE |
Applications can ``register'' with the SCO ISDN interface by opening the /dev/netx device and issuing the ISDN_REGISTER ioctl downstream with the relevant parameters to the opened device.
It is the DLPI (Data Link Provider Interface) module that, upon receiving the register ioctl, requests an application ID from the ISDN driver. The DLPI module then maintains the mapping of application ID to Stream. The application itself does not need to known the application ID.
When the /dev/netx device used by the ISDN adapter is closed, the driver must respond to a ISDN_RELEASE ioctl issued by the DLPI module.
The ISDN_GETPROFILE ioctl gets ``profile'' information about the ISDN device: number of controllers, controller features, and supported protocols.
The values of the defined ioctls and the parameter structures are defined in the <sys/scoisdn.h> header file.