netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Welte <laforge@gnumonks.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Thomas Jarosch <thomas.jarosch@intra2net.com>,
	Networking <netdev@vger.kernel.org>,
	Tilman Schmidt <tilman@imap.cc>,
	Karsten Keil <isdn@linux-pingi.de>,
	gigaset307x-common@lists.sourceforge.net,
	Marcel Holtmann <marcel@holtmann.org>,
	Paul Bolle <pebolle@tiscali.nl>,
	isdn4linux@listserv.isdn4linux.de,
	Al Viro <viro@zeniv.linux.org.uk>,
	Holger Schurig <holgerschurig@googlemail.com>
Subject: Re: [PATCH v2 5/5] isdn: move capi drivers to staging
Date: Mon, 8 Nov 2021 13:50:55 +0100	[thread overview]
Message-ID: <YYkdL2AsV84J950k@nataraja> (raw)
In-Reply-To: <CAK8P3a0=+w-CR_3uUr3Vi8E7v1z1O40K81pZU6y67u5ns8tCHA@mail.gmail.com>

Hi Arnd,

On Mon, Nov 08, 2021 at 11:58:23AM +0100, Arnd Bergmann wrote:
> When removal of mISDN came up last, Harald Welte mentioned that some
> of the code is still used by Osmocom/OpenBSC[1] to drive the E1 line cards.
> I'm not sure if this is still the case, of if they have since migrated
> to another driver.

In Osmocom (specifically, libosmo-abis which is used in osmo-bsc and
osmo-mgw) We currently support E1 interfaces via three drivers:

1) mISDN
2) DAHDI
3) our new open source hardware / gateware / firmware USB-E1 adapter icE1usb
   https://osmocom.org/projects/e1-t1-adapter/wiki/IcE1usb via the
   all-userspace libusb based driver osmo-e1d
   https://osmocom.org/projects/osmo-e1d/wiki/Wiki

The days of the use of TDM/E1 interface are also still far from over in
the cellular telecom operator industry - particularly so in
not-so-wealthy countries.  At my company we regularly have projects that
involve the requirement to drive E1 interfaces (typically 3GPP Abis, A and
Gb interface), even in 2021.

From my point of view, mISDN is certainly the least used driver at the
moment, given that [as far as I know] the only E1/PRI interface chipsets
it supports were for classic parallel PCI bus, which is hard to find
both in terms of E1 adapters as well as in mainboards.  Also, the cards
never supported more than 1 or 2 E1 ports, as far as I know.

I would expect the majority of the users are using DAHDI based
deployments (up to 8x E1 per PCIe slot), with some adventurous ones
requiring few portsgoing for our icE1usb.

I will inquire on the appropriate osmocom mailing list whether there are
people still using mISDN.

-- 
- Harald Welte <laforge@gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

  reply	other threads:[~2021-11-08 13:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 19:58 [PATCH v2 0/5] isdn: deprecate non-mISDN drivers Arnd Bergmann
2019-04-26 19:58 ` [PATCH v2 1/5] isdn: gigaset: remove i4l support Arnd Bergmann
2019-04-28  2:04   ` David Miller
2019-04-28  9:27     ` Arnd Bergmann
2019-04-26 19:58 ` [PATCH v2 2/5] isdn: remove hisax driver Arnd Bergmann
2019-04-26 19:58 ` [PATCH v2 3/5] isdn: remove isdn4linux Arnd Bergmann
2019-04-26 19:58 ` [PATCH v2 4/5] isdn: hdlc: move into mISDN Arnd Bergmann
2019-04-26 19:58 ` [PATCH v2 5/5] isdn: move capi drivers to staging Arnd Bergmann
2021-11-08  9:48   ` Thomas Jarosch
2021-11-08 10:58     ` Arnd Bergmann
2021-11-08 12:50       ` Harald Welte [this message]
     [not found]       ` <977673e5-57ea-1977-65fe-963e88f5da7a@eversberg.eu>
2022-01-09 11:29         ` Arnd Bergmann

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=YYkdL2AsV84J950k@nataraja \
    --to=laforge@gnumonks.org \
    --cc=arnd@arndb.de \
    --cc=gigaset307x-common@lists.sourceforge.net \
    --cc=holgerschurig@googlemail.com \
    --cc=isdn4linux@listserv.isdn4linux.de \
    --cc=isdn@linux-pingi.de \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=thomas.jarosch@intra2net.com \
    --cc=tilman@imap.cc \
    --cc=viro@zeniv.linux.org.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).