2005-04-16 15:20:36 -07:00
config ISDN_DRV_AVMB1_VERBOSE_REASON
2007-02-28 20:13:50 -08:00
bool "Verbose reason code reporting"
default y
2005-04-16 15:20:36 -07:00
help
2007-02-28 20:13:50 -08:00
If you say Y here, the CAPI drivers will give verbose reasons for
2005-04-16 15:20:36 -07:00
disconnecting. This will increase the size of the kernel by 7 KB. If
unsure, say Y.
2007-02-28 20:13:50 -08:00
config CAPI_TRACE
bool "CAPI trace support"
default y
help
If you say Y here, the kernelcapi driver can make verbose traces
of CAPI messages. This feature can be enabled/disabled via IOCTL for
2007-05-09 07:35:06 +02:00
every controller (default disabled).
2007-02-28 20:13:50 -08:00
This will increase the size of the kernelcapi module by 20 KB.
If unsure, say Y.
2005-04-16 15:20:36 -07:00
config ISDN_CAPI_MIDDLEWARE
2010-02-08 10:12:45 +00:00
bool "CAPI2.0 Middleware support"
2005-04-16 15:20:36 -07:00
help
This option will enhance the capabilities of the /dev/capi20
interface. It will provide a means of moving a data connection,
established via the usual /dev/capi20 interface to a special tty
device. If you want to use pppd with pppdcapiplugin to dial up to
your ISP, say Y here.
config ISDN_CAPI_CAPI20
tristate "CAPI2.0 /dev/capi support"
help
This option will provide the CAPI 2.0 interface to userspace
applications via /dev/capi20. Applications should use the
standardized libcapi20 to access this functionality. You should say
Y/M here.
config ISDN_CAPI_CAPIDRV
tristate "CAPI2.0 capidrv interface support"
2007-07-17 04:04:20 -07:00
depends on ISDN_I4L
2005-04-16 15:20:36 -07:00
help
This option provides the glue code to hook up CAPI driven cards to
the legacy isdn4linux link layer. If you have a card which is
supported by a CAPI driver, but still want to use old features like
ippp interfaces or ttyI emulation, say Y/M here.