Age | Commit message (Collapse) | Author | Files | Lines |
|
So far, the e1d input driver only contained code for LAPD signaling
slots, let's extend it with support for all the other slot types, as
well as support for run-time re-configuration.
Change-Id: I53369004145681bf9178543fe407dfc75e4ae63a
|
|
Let's not print an error at program/library start time if osmo-e1d
cannot be reached. This error is confusing to everyone who may
have a libosmo-abis with e1d support compiled in, but who is not
(currently) using any lines via this driver, but others drivers.
Change-Id: If0d033f8a2ab4f0e72549a811ffccc66b91fb0a8
|
|
Change-Id: I88ba83783ae1d8368990ec30cdc7ecff88884e41
|
|
This way we can support more than one E1 line via osmo-e1d. As
neither mISDN nor DAHDI distinguish between mutliple cards of single
ports vs. multi-port cards, we havee to map both interface + line number
into a single uint8_t.
Change-Id: I3b6975624a0155a68d2c67bfdbc1fb751fb50b13
|
|
It's optional for an input driver to provide this function, and e.g.
mISDN doesn't provide it, either.
Change-Id: I56ed4244121f2019ece80d15bd07d5a8ce958273
|
|
The file decscriptor 'except' handling was only added in the DAHDI
input module as the DAHDI kernel side is actually using those. I
don't think we can even use this in any way over unix domain sockets.
Change-Id: I718629179181a1de3b82e23447549f593046d91f
|
|
Change-Id: I98f337f8f517b98f9b78dc173e5761687609abd8
|
|
osmo-e1d is part of the Osmocom 'software defined E1 interface,
which consists of a USB device for the actual E1 hardware interfacing,
and a daemon (osmo-e1d) implementing a libusb-based driver.
This commit adds initial support for talking to osmo-e1d using
the related libosmoe1d library. You need to use '--enable-e1d'
at configure time to enable it.
Change-Id: Ia0431c124e3b5b4108aee7b109d8c4bb0d8b45d4
Signed-off-by: Sylvain Munaut <tnt@246tNt.com>
|