Attention is currently required from: keith, dexter.
1 comment:
Patchset:
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 change 32374. To unsubscribe, or for help writing mail filters, visit settings.