diff options
| author | Dan Williams <dcbw@redhat.com> | 2010-12-19 15:18:12 -0600 |
|---|---|---|
| committer | Dan Williams <dcbw@redhat.com> | 2010-12-19 15:18:12 -0600 |
| commit | 00b0b70f5dd7e6896cc533e7ac3e9584467858e6 (patch) | |
| tree | 09fc72ec2e81413f1335114a8b39f86d7eb7eeff /src/80-mm-candidate.rules | |
| parent | a4e620aca0a13b6630b587bc6ed21ec2454e86ec (diff) | |
bluetooth: tag 'moved' bluetooth ttys as candidates
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.
Diffstat (limited to 'src/80-mm-candidate.rules')
| -rw-r--r-- | src/80-mm-candidate.rules | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/src/80-mm-candidate.rules b/src/80-mm-candidate.rules index e30b04ef..e99ae3ad 100644 --- a/src/80-mm-candidate.rules +++ b/src/80-mm-candidate.rules @@ -7,11 +7,10 @@ # 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", GOTO="mm_candidate_end" +ACTION!="add|change|move", GOTO="mm_candidate_end" SUBSYSTEM=="tty", ENV{ID_MM_CANDIDATE}="1" SUBSYSTEM=="net", ENV{ID_MM_CANDIDATE}="1" -SUBSYSTEM=="bluetooth", ENV{ID_MM_CANDIDATE}="1" LABEL="mm_candidate_end" |