Attention is currently required from: keith, dexter.
laforge has posted comments on this change. (
https://gerrit.osmocom.org/c/libosmo-abis/+/32374 )
Change subject: e1d: reconnect to osmo-e1d after connection loss
......................................................................
Patch Set 3:
(1 comment)
Patchset:
PS2:
> Its a problem with the e1d driver in libosmo-e1d. […]
I don't have the full picture nor the time right now (on holidays) to
investigate fully. I just wanted to share that the problem of e1d restarts is
something every application is facing, so a generic solution on the libosmo-e1d
side would make sense, IMHO. Adding a new API in libosmo-e1d for that it is
certainly an option.
The other question to me is whether it wouldn't be much simpler for keith (or
other osmo-bsc + E1 users) to use the icE1usb DAHDI driver. In that situation
the situation of an "e1d restart" never occurs. So I'm wondering whether it's
useful investment of R&D resources to implement a feature which already works
using some other software.
IMHO, there are use cases (like OCTOI) whcih are tied ot osmo-e1d. And then
there are other use cases (like osmo-{bsc,mgw}) where using the DAHDI driver
might be a better match.
The DAHDI driver also doesn't have any problems with usb device
disconnects/reconnects, at least not that I'm aware of.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-abis/+/32374
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: Iaf4d42c2f009b1d7666e319fabdeb2598aa0b338
Gerrit-Change-Number: 32374
Gerrit-PatchSet: 3
Gerrit-Owner: dexter <[email protected]>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: keith <[email protected]>
Gerrit-CC: laforge <[email protected]>
Gerrit-CC: tnt <[email protected]>
Gerrit-Attention: keith <[email protected]>
Gerrit-Attention: dexter <[email protected]>
Gerrit-Comment-Date: Fri, 21 Apr 2023 00:07:30 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <[email protected]>
Comment-In-Reply-To: keith <[email protected]>
Comment-In-Reply-To: dexter <[email protected]>
Gerrit-MessageType: comment
