From: tilman@imap.cc (Tilman Schmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging
Date: Wed, 9 Mar 2016 23:10:18 +0100 [thread overview]
Message-ID: <56E09F4A.8010202@imap.cc> (raw)
In-Reply-To: <1457340486.2737.19.camel@tiscali.nl>
Am 07.03.2016 um 09:48 schrieb Paul Bolle:
> On za, 2016-03-05 at 14:08 +0100, Tilman Schmidt wrote:
>> As a consequence, owners of HiSAX type adapters are in fact stuck with
>> the old hisax driver if they want to continue using i4l userspace
>> tools.
>
> Do you know whether or not mISDN tools offer functionality comparable to
> i4l tools?
AFAICS they don't. mISDN seems very much geared towards voice use, for
example with Asterisk. The entire topic of ISDN data connections appears
to be missing. I don't see how someone currently using i4l for Internet
dial-in (either client or server side) could migrate to mISDN.
--
Tilman Schmidt E-Mail: tilman at imap.cc
Bonn, Germany
Nous, on a des fleurs et des bougies pour nous prot?ger.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160309/cb4342b1/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Tilman Schmidt <tilman@imap.cc>
To: Paul Bolle <pebolle@tiscali.nl>, Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
linux-arm-kernel@lists.infradead.org, isdn@linux-pingi.de,
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: Wed, 9 Mar 2016 23:10:18 +0100 [thread overview]
Message-ID: <56E09F4A.8010202@imap.cc> (raw)
In-Reply-To: <1457340486.2737.19.camel@tiscali.nl>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
Am 07.03.2016 um 09:48 schrieb Paul Bolle:
> On za, 2016-03-05 at 14:08 +0100, Tilman Schmidt wrote:
>> As a consequence, owners of HiSAX type adapters are in fact stuck with
>> the old hisax driver if they want to continue using i4l userspace
>> tools.
>
> Do you know whether or not mISDN tools offer functionality comparable to
> i4l tools?
AFAICS they don't. mISDN seems very much geared towards voice use, for
example with Asterisk. The entire topic of ISDN data connections appears
to be missing. I don't see how someone currently using i4l for Internet
dial-in (either client or server side) could migrate to mISDN.
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Nous, on a des fleurs et des bougies pour nous protéger.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-09 22:10 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 [this message]
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
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=56E09F4A.8010202@imap.cc \
--to=tilman@imap.cc \
--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.