On Fri, Jul 31, 2009 at 21:35, Mario Limonciello<mario_limonciello@xxxxxxxx> wrote:
> The problem is that the device is already gone (and not in the udev
> database) by the time you call the command.
I guess, we can get rid of all these hacks and the search code, by
tagging the mouse device we need to find, with:
..., ENV{HID2HCI_SWITCH}="1", RUN+="hid2hci --method=dell --devpath=%p"
and for the bluetooth device we just let it trigger the
tagged mouse device when it goes away, with:
..., ENV{REMOVE_CMD}="/sbin/udevadm trigger --action=change --subsystem-match=usb --property-match=HID2HCI_SWITCH=1"
That way the disappearing bluetooth device would just cause
a "change" event at the mouse device, which would trigger
the original rule again.
It would not need any further search logic, and the resume case
would run the same rules as the plug-in case.
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
