Am 10.03.2016 um 17:41 schrieb isdn@xxxxxxxxxxxxxx: > Am 10.03.2016 um 13:58 schrieb Paul Bolle: >> On do, 2016-03-10 at 11:53 +0100, isdn@xxxxxxxxxxxxxx wrote: >>> mISDN with CAPI support works just fine with pppd and pppdcapiplugin >>> and the CAPI works for all mISDN HW. >> >> In the mainline tree the mISDN and CAPI stacks are effectively separate. Correct. > Since 2012 mISDN has a cAPI20 interface, pure in userspace. To expand: The documented interface for CAPI 2.0 applications is the shared library libcapi20.so. Originally that library just interfaced to the kernel CAPI subsystem through /dev/capi20. Later it was extended to support different access paths to ISDN devices: - via /dev/capi20 and kernel CAPI as before - over the network and a remote CAPI server running rcapid - over the network to FRITZ!Box router via AVM's CAPI-over-TCP service - last but not least, via the mISDNcapid daemon and mISDN Of course this cuts off anything that doesn't pass through libcapi20.so, including applications that (against the standard) access /dev/capi20 directly but also the capidrv.ko i4l compatibility shim. -- Tilman Schmidt E-Mail: tilman@xxxxxxx Bonn, Germany Nous, on a des fleurs et des bougies pour nous protéger.
Attachment:
signature.asc
Description: OpenPGP digital signature
