mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-27 22:53:55 +08:00
d1cadce15a
Since v2.4 the capi driver used the following device nodes if
"middleware" support was enabled:
/dev/capi20
/dev/capi/0
/dev/capi/1
[...]
/dev/capi20 is a character device node. /dev/capi/0 (and up) are tty
device nodes (with a different major).
This device node (naming) scheme is not documented anywhere, as far as I
know. It was originally provided by the capifs pseudo filesystem (before
udev became available). It is required for example by the pppd
capiplugin. It was supported until a few years ago. But a number of
developments broke it:
- v2.6.6 (May 2004) renamed /dev/capi20 to /dev/capi and removed the
"/" from the name of capi's tty driver. The explanation of the patch
that did this included two examples of udev rules "to restore the old
namespace";
- either udev 154 (May 2010) or udev 179 (January 2012) stopped
allowing to rename device nodes, and thus the ability to have
/dev/capi20 appear instead of /dev/capi and /dev/capi/0 (and up)
instead of /dev/capi0 (and up);
- v3.0 (July 2011) also removed capifs. That disabled another method to
create the /dev/capi/0 (and up) device nodes.
So now users need to manually tweak their setup (eg, create /dev/capi/
and fill that with symlinks) to get things working. This is all rather
hacky and only discoverable by searching the web. Fix all this by
renaming /dev/capi back to /dev/capi20, and by setting the name of the
"capi_nc" tty driver to "capi!" so the tty device nodes appear as
/dev/capi/0 (and up).
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Tilman Schmidt <tilman@imap.cc>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
45 lines
1.6 KiB
Plaintext
45 lines
1.6 KiB
Plaintext
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
|
|
every controller (default disabled).
|
|
This will increase the size of the kernelcapi module by 20 KB.
|
|
If unsure, say Y.
|
|
|
|
config ISDN_CAPI_CAPI20
|
|
tristate "CAPI2.0 /dev/capi20 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_MIDDLEWARE
|
|
bool "CAPI2.0 Middleware support"
|
|
depends on ISDN_CAPI_CAPI20 && TTY
|
|
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_CAPIDRV
|
|
tristate "CAPI2.0 capidrv interface support"
|
|
depends on ISDN_I4L
|
|
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.
|
|
|
|
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.
|