Aleksander Morgado
cb2dea5dc4
We can remove the port type hint udev tags for the wwan subsystem, as that logic is now incorporated in the port type hint processing logic in the daemon itself. This makes it clearer to know what exact hints are being used, as the logic is in a single place and it has proper logging of all possible cases.
29 lines
1.3 KiB
Plaintext
29 lines
1.3 KiB
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*", SUBSYSTEM=="usbmisc", ENV{ID_MM_CANDIDATE}="1"
|
|
|
|
# WWAN subsystem port handling
|
|
# - All USB devices ignored for now, only PCI devices expected
|
|
# - Only "wwan_port" device types processed (single ports); we fully ignore
|
|
# the "wwan_dev" device type (full device, not just one port)
|
|
SUBSYSTEMS=="usb", GOTO="mm_candidate_end"
|
|
SUBSYSTEM=="wwan", ENV{DEVTYPE}=="wwan_dev", GOTO="mm_candidate_end"
|
|
SUBSYSTEM=="wwan", ENV{ID_MM_CANDIDATE}="1"
|
|
|
|
LABEL="mm_candidate_end"
|