Aleksander Morgado
950abbf8ee
Back in Linux < 3.6 days, the cdc-wdm ports exposed by the QMI driver were flagged as owned by the 'usb' subsystem. That changed in 3.6 when the subsystem was renamed to 'usbmisc': https://mail.gnome.org/archives/networkmanager-list/2012-June/msg00125.html This patch removes all monitoring of the 'usb' subsystem completely, which is anyway a valid subsystem but for which we shouldn't need any special handling. Right now, with newer kernels, we were using that monitoring exclusively to get notified of full USB device remove events, which is really not required as we already process the port removals one by one. We simplify the logic everywhere that attempted to match either the 'usb' or 'usbmisc' subsystems, and we no longer require the explicit checks for the port name being named 'cdc-wdm[0-9]*' in the code, as that is already taken care of by the ID_MM_CANDIDATE udev tag rule.
21 lines
914 B
Plaintext
21 lines
914 B
Plaintext
# do not edit this file, it will be overwritten on update
|
|
|
|
# Tag any devices that MM might be interested in; if ModemManager is started
|
|
# up right after udev, when MM explicitly requests devices on startup it may
|
|
# get devices that haven't had all rules run yet. Thus, we tag devices we're
|
|
# interested in and when handling devices during MM startup we ignore any
|
|
# that don't have this tag. MM will still get the udev 'add' event for the
|
|
# device a short while later and then process it as normal.
|
|
|
|
ACTION!="add|change|move|bind", GOTO="mm_candidate_end"
|
|
|
|
# Opening bound but disconnected Bluetooth RFCOMM ttys would initiate the
|
|
# connection. Don't do that.
|
|
KERNEL=="rfcomm*", DEVPATH=="*/virtual/*", GOTO="mm_candidate_end"
|
|
|
|
SUBSYSTEM=="tty", ENV{ID_MM_CANDIDATE}="1"
|
|
SUBSYSTEM=="net", ENV{ID_MM_CANDIDATE}="1"
|
|
KERNEL=="cdc-wdm[0-9]*", SUBSYSTEM=="usbmisc", ENV{ID_MM_CANDIDATE}="1"
|
|
|
|
LABEL="mm_candidate_end"
|