From 00b0b70f5dd7e6896cc533e7ac3e9584467858e6 Mon Sep 17 00:00:00 2001
From: Dan Williams <dcbw@redhat.com>
Date: Sun, 19 Dec 2010 15:18:12 -0600
Subject: [PATCH] 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.
---
 src/80-mm-candidate.rules | 3 +--
 1 file changed, 1 insertion(+), 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"