Dan Williams
00b0b70f5d
The kernel appears to add the device first without any parents, then to move it to the correct place in the hierarchy, with its immediate parent being the device's HCI controller. So we need to capture the 'move' event too since that's when the rfcomm device is finally usable.
17 lines
667 B
Plaintext
17 lines
667 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", GOTO="mm_candidate_end"
|
|
|
|
SUBSYSTEM=="tty", ENV{ID_MM_CANDIDATE}="1"
|
|
SUBSYSTEM=="net", ENV{ID_MM_CANDIDATE}="1"
|
|
|
|
LABEL="mm_candidate_end"
|
|
|