All of lore.kernel.org
 help / color / mirror / Atom feed
From: isdn@linux-pingi.de (isdn at linux-pingi.de)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging
Date: Thu, 10 Mar 2016 17:41:03 +0100	[thread overview]
Message-ID: <56E1A39F.1010005@linux-pingi.de> (raw)
In-Reply-To: <1457614704.2478.11.camel@tiscali.nl>

Am 10.03.2016 um 13:58 schrieb Paul Bolle:
> Hi Karsten,
> 
> On do, 2016-03-10 at 11:53 +0100, isdn at linux-pingi.de 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.
> Do you perhaps refer to a mISDN + Asterisk + chan-capi setup? (That's
> the closest to mISDN with CAPI support that I could find. Did I miss
> something?)

http://listserv.isdn4linux.de/pipermail/isdn4linux/2012-January/005580.html

Since 2012 mISDN has a cAPI20 interface, pure in userspace.
Everything is in the capi20 subdirectory of mISDNuser.
The capi20 support need to be enabled with ./configure.

Has nothing to do with Asterisk, but for FAX it is useing the same DSP
library, spandsp.

Best
Karsten Keil

WARNING: multiple messages have this Message-ID (diff)
From: isdn@linux-pingi.de
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Tilman Schmidt <tilman@imap.cc>, Arnd Bergmann <arnd@arndb.de>,
	Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	linux-arm-kernel@lists.infradead.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-doc@vger.kernel.org,
	netdev@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging
Date: Thu, 10 Mar 2016 17:41:03 +0100	[thread overview]
Message-ID: <56E1A39F.1010005@linux-pingi.de> (raw)
In-Reply-To: <1457614704.2478.11.camel@tiscali.nl>

Am 10.03.2016 um 13:58 schrieb Paul Bolle:
> Hi Karsten,
> 
> On do, 2016-03-10 at 11:53 +0100, isdn@linux-pingi.de 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.
> Do you perhaps refer to a mISDN + Asterisk + chan-capi setup? (That's
> the closest to mISDN with CAPI support that I could find. Did I miss
> something?)

http://listserv.isdn4linux.de/pipermail/isdn4linux/2012-January/005580.html

Since 2012 mISDN has a cAPI20 interface, pure in userspace.
Everything is in the capi20 subdirectory of mISDNuser.
The capi20 support need to be enabled with ./configure.

Has nothing to do with Asterisk, but for FAX it is useing the same DSP
library, spandsp.

Best
Karsten Keil

WARNING: multiple messages have this Message-ID (diff)
From: isdn@linux-pingi.de
To: Paul Bolle <pebolle@tiscali.nl>
Cc: devel@driverdev.osuosl.org, Arnd Bergmann <arnd@arndb.de>,
	linux-doc@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-kernel@vger.kernel.org, Tilman Schmidt <tilman@imap.cc>,
	netdev@vger.kernel.org,
	Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	"David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging
Date: Thu, 10 Mar 2016 17:41:03 +0100	[thread overview]
Message-ID: <56E1A39F.1010005@linux-pingi.de> (raw)
In-Reply-To: <1457614704.2478.11.camel@tiscali.nl>

Am 10.03.2016 um 13:58 schrieb Paul Bolle:
> Hi Karsten,
> 
> On do, 2016-03-10 at 11:53 +0100, isdn@linux-pingi.de 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.
> Do you perhaps refer to a mISDN + Asterisk + chan-capi setup? (That's
> the closest to mISDN with CAPI support that I could find. Did I miss
> something?)

http://listserv.isdn4linux.de/pipermail/isdn4linux/2012-January/005580.html

Since 2012 mISDN has a cAPI20 interface, pure in userspace.
Everything is in the capi20 subdirectory of mISDNuser.
The capi20 support need to be enabled with ./configure.

Has nothing to do with Asterisk, but for FAX it is useing the same DSP
library, spandsp.

Best
Karsten Keil

  reply	other threads:[~2016-03-10 16:41 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 19:06 [PATCH 1/2] isdn: icn: remove a #warning Arnd Bergmann
2016-03-02 19:06 ` Arnd Bergmann
2016-03-02 19:06 ` [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging Arnd Bergmann
2016-03-02 19:06   ` Arnd Bergmann
2016-03-03  8:30   ` isdn at linux-pingi.de
2016-03-03  8:30     ` isdn
2016-03-04 15:24     ` Arnd Bergmann
2016-03-04 15:24       ` Arnd Bergmann
2016-03-04 16:18       ` Paul Bolle
2016-03-04 16:18         ` Paul Bolle
2016-03-04 16:32         ` Arnd Bergmann
2016-03-04 16:32           ` Arnd Bergmann
2016-03-07  8:33           ` Paul Bolle
2016-03-07  8:33             ` Paul Bolle
2016-03-05 13:08         ` Tilman Schmidt
2016-03-05 13:08           ` Tilman Schmidt
2016-03-07  8:48           ` Paul Bolle
2016-03-07  8:48             ` Paul Bolle
2016-03-09 22:10             ` Tilman Schmidt
2016-03-09 22:10               ` Tilman Schmidt
2016-03-10 10:53               ` isdn at linux-pingi.de
2016-03-10 10:53                 ` isdn
2016-03-10 10:53                 ` isdn
2016-03-10 12:58                 ` Paul Bolle
2016-03-10 12:58                   ` Paul Bolle
2016-03-10 16:41                   ` isdn at linux-pingi.de [this message]
2016-03-10 16:41                     ` isdn
2016-03-10 16:41                     ` isdn
2016-03-11 20:04                     ` Tilman Schmidt
2016-03-11 20:04                       ` Tilman Schmidt
2016-03-11 20:04                       ` Tilman Schmidt
2016-03-04 18:18       ` isdn at linux-pingi.de
2016-03-04 18:18         ` isdn
2016-03-04 21:00         ` Arnd Bergmann
2016-03-04 21:00           ` Arnd Bergmann
2016-03-07  6:57       ` Holger Schurig
2016-03-07  6:57         ` Holger Schurig
2016-03-19 10:27         ` Tilman Schmidt
2016-03-19 10:27           ` Tilman Schmidt
2016-03-19 10:27           ` Tilman Schmidt
2016-03-03 22:22   ` David Miller
2016-03-03 22:22     ` David Miller
2016-03-03 22:33     ` Greg KH
2016-03-03 22:33       ` Greg KH
2016-03-03 22:33       ` Greg KH
2016-03-05  3:19   ` kbuild test robot
2016-03-05  3:19     ` kbuild test robot
2017-01-03 15:24   ` Greg Kroah-Hartman
2017-01-03 15:24     ` Greg Kroah-Hartman
2017-01-03 15:24     ` Greg Kroah-Hartman
2017-01-03 21:19     ` Arnd Bergmann
2017-01-03 21:19       ` Arnd Bergmann
2017-01-03 21:54       ` Paul Bolle
2017-01-03 21:54         ` Paul Bolle
2017-01-03 22:25         ` Arnd Bergmann
2017-01-03 22:25           ` Arnd Bergmann
2017-01-03 22:57           ` Paul Bolle
2017-01-03 22:57             ` Paul Bolle
2017-01-03 23:03             ` Arnd Bergmann
2017-01-03 23:03               ` Arnd Bergmann
2017-01-03 23:03               ` Arnd Bergmann
2017-01-05 21:19       ` Greg Kroah-Hartman
2017-01-05 21:19         ` Greg Kroah-Hartman
2017-01-05 21:19         ` Greg Kroah-Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E1A39F.1010005@linux-pingi.de \
    --to=isdn@linux-pingi.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.