colin/ModemManager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bluetooth: tag 'moved' bluetooth ttys as candidates

Browse Source 
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.
This commit is contained in:
Dan Williams
2010-12-19 15:18:12 -06:00
parent a4e620aca0
commit 00b0b70f5d
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
src/80-mm-candidate.rules
View File

@@ -7,11 +7,10 @@
# that don't have this tag. MM will still get the udev 'add' event for the # 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. # device a short while later and then process it as normal.
ACTION!="add|change", GOTO="mm_candidate_end" ACTION!="add|change|move", GOTO="mm_candidate_end"
SUBSYSTEM=="tty", ENV{ID_MM_CANDIDATE}="1" SUBSYSTEM=="tty", ENV{ID_MM_CANDIDATE}="1"
SUBSYSTEM=="net", ENV{ID_MM_CANDIDATE}="1" SUBSYSTEM=="net", ENV{ID_MM_CANDIDATE}="1"
SUBSYSTEM=="bluetooth", ENV{ID_MM_CANDIDATE}="1"
LABEL="mm_candidate_end" LABEL="mm_candidate_end"