2 # Config.in for the CAPI subsystem
4 config ISDN_DRV_AVMB1_VERBOSE_REASON
5 bool "Verbose reason code reporting"
8 If you say Y here, the CAPI drivers will give verbose reasons for
9 disconnecting. This will increase the size of the kernel by 7 KB. If
13 bool "CAPI trace support"
16 If you say Y here, the kernelcapi driver can make verbose traces
17 of CAPI messages. This feature can be enabled/disabled via IOCTL for
18 every controller (default disabled).
19 This will increase the size of the kernelcapi module by 20 KB.
22 config ISDN_CAPI_MIDDLEWARE
23 bool "CAPI2.0 Middleware support (EXPERIMENTAL)"
24 depends on EXPERIMENTAL
26 This option will enhance the capabilities of the /dev/capi20
27 interface. It will provide a means of moving a data connection,
28 established via the usual /dev/capi20 interface to a special tty
29 device. If you want to use pppd with pppdcapiplugin to dial up to
32 config ISDN_CAPI_CAPI20
33 tristate "CAPI2.0 /dev/capi support"
35 This option will provide the CAPI 2.0 interface to userspace
36 applications via /dev/capi20. Applications should use the
37 standardized libcapi20 to access this functionality. You should say
40 config ISDN_CAPI_CAPIFS_BOOL
41 bool "CAPI2.0 filesystem support"
42 depends on ISDN_CAPI_MIDDLEWARE && ISDN_CAPI_CAPI20
44 config ISDN_CAPI_CAPIFS
46 depends on ISDN_CAPI_CAPIFS_BOOL
47 default ISDN_CAPI_CAPI20
49 This option provides a special file system, similar to /dev/pts with
50 device nodes for the special ttys established by using the
51 middleware extension above. If you want to use pppd with
52 pppdcapiplugin to dial up to your ISP, say Y here.
54 config ISDN_CAPI_CAPIDRV
55 tristate "CAPI2.0 capidrv interface support"
58 This option provides the glue code to hook up CAPI driven cards to
59 the legacy isdn4linux link layer. If you have a card which is
60 supported by a CAPI driver, but still want to use old features like
61 ippp interfaces or ttyI emulation, say Y/M here.