Project

General

Profile

Bug #4916

USB unplug / replug renders e1d unusable

Added by laforge about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
12/18/2020
Due date:
% Done:

0%

Spec Reference:

Description

right now the behavior on USB unplug (or - god forbid - a firmware crash) is not very user friendly:
  • e1d keeps running
  • e1d does not re-open the device when it comes back
IMHO, we have the following options
  1. fail fast - simply exit when the device is lost, assume systemd or some other management instance will keep respawning us until the device is back
    • but what about client programs like osmo-bsc / osmo-mgw ?
  2. implement re-opening of a single icE1usb device, knowing our blocking control transfers would corrupt any other ongoing communication
    • is it worth the effort, assuming this is only an interim solution
  3. go for a full-blown hot-plug capable architecture lined out in #4915
    • will probably take significant effort

I think right now we mostly have to worry about situations with a single icE1usb, so I'm tempted to go for the fail-fast approach, assuming osmo-bsc/osmo-mgw recover in some way.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)