2019-05-19 19:07:45 +07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
isdn: move capi drivers to staging
I tried to find any indication of whether the capi drivers are still in
use, and have not found anything from a long time ago.
With public ISDN networks almost completely shut down over the past 12
months, there is very little you can actually do with this hardware. The
main remaining use case would be to connect ISDN voice phones to an
in-house installation with Asterisk or LCR, but anyone trying this in
turn seems to be using either the mISDN driver stack, or out-of-tree
drivers from the hardware vendors.
I may of course have missed something, so I would suggest moving these
three drivers (avm, hysdn, gigaset) into drivers/staging/ just in case
someone still uses them.
If nobody complains, we can remove them entirely in six months, or
otherwise move the core code and any drivers that are still needed back
into drivers/isdn.
As Paul Bolle notes, he is still testing the gigaset driver as long as
he can, but the Dutch ISDN network will be shut down in September 2019,
which puts an end to that.
Marcel Holtmann still maintains the Bluetooth CMTP profile and wants to
keep that alive, so the actual CAPI subsystem code remains in place for
now, after all other drivers are gone, CMTP and CAPI can be merged into
a single driver directory.
Cc: Marcel Holtmann <marcel@holtmann.org>
Cc: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2019-04-21 03:28:45 +07:00
|
|
|
menuconfig ISDN_CAPI
|
|
|
|
|
tristate "CAPI 2.0 subsystem"
|
|
|
|
|
help
|
|
|
|
|
This provides CAPI (the Common ISDN Application Programming
|
|
|
|
|
Interface) Version 2.0, a standard making it easy for programs to
|
|
|
|
|
access ISDN hardware in a device independent way. (For details see
|
|
|
|
|
<http://www.capi.org/>.) CAPI supports making and accepting voice
|
|
|
|
|
and data connections, controlling call options and protocols,
|
|
|
|
|
as well as ISDN supplementary services like call forwarding or
|
|
|
|
|
three-party conferences (if supported by the specific hardware
|
|
|
|
|
driver).
|
|
|
|
|
|
|
|
|
|
This subsystem requires a hardware specific driver.
|
|
|
|
|
See CONFIG_BT_CMTP for the last remaining regular driver
|
|
|
|
|
in the kernel that uses the CAPI subsystem.
|
|
|
|
|
|
|
|
|
|
if ISDN_CAPI
|
|
|
|
|
|
2007-03-01 11:13:50 +07: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 12:35:06 +07:00
|
|
|
every controller (default disabled).
|
2007-03-01 11:13:50 +07:00
|
|
|
This will increase the size of the kernelcapi module by 20 KB.
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
|
2014-03-17 00:44:21 +07:00
|
|
|
config ISDN_CAPI_CAPI20
|
2014-06-02 04:47:24 +07:00
|
|
|
tristate "CAPI2.0 /dev/capi20 support"
|
2014-03-17 00:44:21 +07:00
|
|
|
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.
|
|
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
config ISDN_CAPI_MIDDLEWARE
|
2010-02-08 17:12:45 +07:00
|
|
|
bool "CAPI2.0 Middleware support"
|
2014-03-17 00:44:21 +07:00
|
|
|
depends on ISDN_CAPI_CAPI20 && TTY
|
2005-04-17 05: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.
|
|
|
|
|
|
2014-06-02 04:47:24 +07:00
|
|
|
config ISDN_CAPI_CAPIDRV_VERBOSE
|
|
|
|
|
bool "Verbose reason code reporting"
|
|
|
|
|
depends on ISDN_CAPI_CAPIDRV
|
|
|
|
|
help
|
|
|
|
|
If you say Y here, the capidrv interface will give verbose reasons
|
|
|
|
|
for disconnecting. This will increase the size of the kernel by 7 KB.
|
|
|
|
|
If unsure, say N.
|
isdn: move capi drivers to staging
I tried to find any indication of whether the capi drivers are still in
use, and have not found anything from a long time ago.
With public ISDN networks almost completely shut down over the past 12
months, there is very little you can actually do with this hardware. The
main remaining use case would be to connect ISDN voice phones to an
in-house installation with Asterisk or LCR, but anyone trying this in
turn seems to be using either the mISDN driver stack, or out-of-tree
drivers from the hardware vendors.
I may of course have missed something, so I would suggest moving these
three drivers (avm, hysdn, gigaset) into drivers/staging/ just in case
someone still uses them.
If nobody complains, we can remove them entirely in six months, or
otherwise move the core code and any drivers that are still needed back
into drivers/isdn.
As Paul Bolle notes, he is still testing the gigaset driver as long as
he can, but the Dutch ISDN network will be shut down in September 2019,
which puts an end to that.
Marcel Holtmann still maintains the Bluetooth CMTP profile and wants to
keep that alive, so the actual CAPI subsystem code remains in place for
now, after all other drivers are gone, CMTP and CAPI can be merged into
a single driver directory.
Cc: Marcel Holtmann <marcel@holtmann.org>
Cc: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2019-04-21 03:28:45 +07:00
|
|
|
|
|
|
|
|
endif
|