| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 1 | # |
| 2 | # Config.in for the CAPI subsystem |
| 3 | # |
| 4 | config ISDN_DRV_AVMB1_VERBOSE_REASON |
| Karsten Keil | 17f0cd2 | 2007-02-28 20:13:50 -0800 | [diff] [blame] | 5 | bool "Verbose reason code reporting" |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 6 | depends on ISDN_CAPI |
| Karsten Keil | 17f0cd2 | 2007-02-28 20:13:50 -0800 | [diff] [blame] | 7 | default y |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 8 | help |
| Karsten Keil | 17f0cd2 | 2007-02-28 20:13:50 -0800 | [diff] [blame] | 9 | If you say Y here, the CAPI drivers will give verbose reasons for |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 10 | disconnecting. This will increase the size of the kernel by 7 KB. If |
| 11 | unsure, say Y. |
| 12 | |
| Karsten Keil | 17f0cd2 | 2007-02-28 20:13:50 -0800 | [diff] [blame] | 13 | config CAPI_TRACE |
| 14 | bool "CAPI trace support" |
| 15 | depends on ISDN_CAPI |
| 16 | default y |
| 17 | help |
| 18 | If you say Y here, the kernelcapi driver can make verbose traces |
| 19 | of CAPI messages. This feature can be enabled/disabled via IOCTL for |
| Matt LaPlante | a982ac0 | 2007-05-09 07:35:06 +0200 | [diff] [blame] | 20 | every controller (default disabled). |
| Karsten Keil | 17f0cd2 | 2007-02-28 20:13:50 -0800 | [diff] [blame] | 21 | This will increase the size of the kernelcapi module by 20 KB. |
| 22 | If unsure, say Y. |
| 23 | |
| Linus Torvalds | 1da177e | 2005-04-16 15:20:36 -0700 | [diff] [blame] | 24 | config ISDN_CAPI_MIDDLEWARE |
| 25 | bool "CAPI2.0 Middleware support (EXPERIMENTAL)" |
| 26 | depends on ISDN_CAPI && EXPERIMENTAL |
| 27 | help |
| 28 | This option will enhance the capabilities of the /dev/capi20 |
| 29 | interface. It will provide a means of moving a data connection, |
| 30 | established via the usual /dev/capi20 interface to a special tty |
| 31 | device. If you want to use pppd with pppdcapiplugin to dial up to |
| 32 | your ISP, say Y here. |
| 33 | |
| 34 | config ISDN_CAPI_CAPI20 |
| 35 | tristate "CAPI2.0 /dev/capi support" |
| 36 | depends on ISDN_CAPI |
| 37 | help |
| 38 | This option will provide the CAPI 2.0 interface to userspace |
| 39 | applications via /dev/capi20. Applications should use the |
| 40 | standardized libcapi20 to access this functionality. You should say |
| 41 | Y/M here. |
| 42 | |
| 43 | config ISDN_CAPI_CAPIFS_BOOL |
| 44 | bool "CAPI2.0 filesystem support" |
| 45 | depends on ISDN_CAPI_MIDDLEWARE && ISDN_CAPI_CAPI20 |
| 46 | |
| 47 | config ISDN_CAPI_CAPIFS |
| 48 | tristate |
| 49 | depends on ISDN_CAPI_CAPIFS_BOOL |
| 50 | default ISDN_CAPI_CAPI20 |
| 51 | help |
| 52 | This option provides a special file system, similar to /dev/pts with |
| 53 | device nodes for the special ttys established by using the |
| 54 | middleware extension above. If you want to use pppd with |
| 55 | pppdcapiplugin to dial up to your ISP, say Y here. |
| 56 | |
| 57 | config ISDN_CAPI_CAPIDRV |
| 58 | tristate "CAPI2.0 capidrv interface support" |
| 59 | depends on ISDN_CAPI && ISDN_I4L |
| 60 | help |
| 61 | This option provides the glue code to hook up CAPI driven cards to |
| 62 | the legacy isdn4linux link layer. If you have a card which is |
| 63 | supported by a CAPI driver, but still want to use old features like |
| 64 | ippp interfaces or ttyI emulation, say Y/M here. |
| 65 | |