aboutsummaryrefslogtreecommitdiff
path: root/cli/mmcli-modem-signal.c
diff options
context:
space:
mode:
authorAleksander Morgado <aleksander@aleksander.es>2016-09-18 15:43:30 +0200
committerAleksander Morgado <aleksander@aleksander.es>2016-09-18 15:43:30 +0200
commitc7d8ac622a56142325af1e9b51d0cce1f06eaa3d (patch)
tree6713acc93267b3e988c74f761496196c64234b98 /cli/mmcli-modem-signal.c
parentaa0e1081070b1062c696d31ed3c68e9511733ad1 (diff)
udev: fix tagging per interface number
Commit 7ff57f9808f35d434b638a67b84481271c67c90e introduced a change to try to use ATTRS{bInterfaceNumber} as a common way to match by interface number, but this logic is broken because all the rules that we use to match by interface number (attribute in the interface device) also require matching by idVendor and idProduct (attributes in the physdev device), and udev rules forbid matches from more than one parent device at a time. We could use ATTR{bInterfaceNumber} (instead of ATTRS) to tag the actual USB interface device, but that would require a change in all the plugins to look for the tag not in the TTY device, but in its parent. So, recover the original behavior, where a hidden property is created containing the first bInterfaceNumber found in the list of parent devices, and then run the matches against idVendor and idProduct only if the hidden property is found with the expected value.
Diffstat (limited to 'cli/mmcli-modem-signal.c')
0 files changed, 0 insertions, 0 deletions