| rjw | 1f88458 | 2022-01-06 17:20:42 +0800 | [diff] [blame^] | 1 | config CAPI_TRACE |
| 2 | bool "CAPI trace support" |
| 3 | default y |
| 4 | help |
| 5 | If you say Y here, the kernelcapi driver can make verbose traces |
| 6 | of CAPI messages. This feature can be enabled/disabled via IOCTL for |
| 7 | every controller (default disabled). |
| 8 | This will increase the size of the kernelcapi module by 20 KB. |
| 9 | If unsure, say Y. |
| 10 | |
| 11 | config ISDN_CAPI_CAPI20 |
| 12 | tristate "CAPI2.0 /dev/capi20 support" |
| 13 | help |
| 14 | This option will provide the CAPI 2.0 interface to userspace |
| 15 | applications via /dev/capi20. Applications should use the |
| 16 | standardized libcapi20 to access this functionality. You should say |
| 17 | Y/M here. |
| 18 | |
| 19 | config ISDN_CAPI_MIDDLEWARE |
| 20 | bool "CAPI2.0 Middleware support" |
| 21 | depends on ISDN_CAPI_CAPI20 && TTY |
| 22 | help |
| 23 | This option will enhance the capabilities of the /dev/capi20 |
| 24 | interface. It will provide a means of moving a data connection, |
| 25 | established via the usual /dev/capi20 interface to a special tty |
| 26 | device. If you want to use pppd with pppdcapiplugin to dial up to |
| 27 | your ISP, say Y here. |
| 28 | |
| 29 | config ISDN_CAPI_CAPIDRV |
| 30 | tristate "CAPI2.0 capidrv interface support" |
| 31 | depends on ISDN_I4L |
| 32 | help |
| 33 | This option provides the glue code to hook up CAPI driven cards to |
| 34 | the legacy isdn4linux link layer. If you have a card which is |
| 35 | supported by a CAPI driver, but still want to use old features like |
| 36 | ippp interfaces or ttyI emulation, say Y/M here. |
| 37 | |
| 38 | config ISDN_CAPI_CAPIDRV_VERBOSE |
| 39 | bool "Verbose reason code reporting" |
| 40 | depends on ISDN_CAPI_CAPIDRV |
| 41 | help |
| 42 | If you say Y here, the capidrv interface will give verbose reasons |
| 43 | for disconnecting. This will increase the size of the kernel by 7 KB. |
| 44 | If unsure, say N. |