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