1 config ISDN_DRV_AVMB1_VERBOSE_REASON
2 bool "Verbose reason code reporting"
5 If you say Y here, the CAPI drivers will give verbose reasons for
6 disconnecting. This will increase the size of the kernel by 7 KB. If
10 bool "CAPI trace support"
13 If you say Y here, the kernelcapi driver can make verbose traces
14 of CAPI messages. This feature can be enabled/disabled via IOCTL for
15 every controller (default disabled).
16 This will increase the size of the kernelcapi module by 20 KB.
19 config ISDN_CAPI_MIDDLEWARE
20 bool "CAPI2.0 Middleware support"
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
29 config ISDN_CAPI_CAPI20
30 tristate "CAPI2.0 /dev/capi support"
32 This option will provide the CAPI 2.0 interface to userspace
33 applications via /dev/capi20. Applications should use the
34 standardized libcapi20 to access this functionality. You should say
37 config ISDN_CAPI_CAPIDRV
38 tristate "CAPI2.0 capidrv interface support"
41 This option provides the glue code to hook up CAPI driven cards to
42 the legacy isdn4linux link layer. If you have a card which is
43 supported by a CAPI driver, but still want to use old features like
44 ippp interfaces or ttyI emulation, say Y/M here.