On Thu, Aug 20, 2009 at 19:23, Mario
Limonciello<Mario_Limonciello@xxxxxxxx> wrote:
> For the retrigger of the device on remove we were trying to match bmAttributes
> of self powered which is unnecessary.
> ---
> extras/hid2hci/70-hid2hci.rules | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/extras/hid2hci/70-hid2hci.rules b/extras/hid2hci/70-hid2hci.rules
> index b332c16..2659877 100644
> --- a/extras/hid2hci/70-hid2hci.rules
> +++ b/extras/hid2hci/70-hid2hci.rules
> @@ -20,7 +20,7 @@ ENV{DEVTYPE}!="usb_device", GOTO="hid2hci_end"
> # Unfortunately the only event seen is the BT device disappearing, so the mouse
> # device needs to be chased down on the USB bus.
> ATTR{bDeviceClass}=="e0", ATTR{bDeviceSubClass}=="01", ATTR{bDeviceProtocol}=="01", \
> - ATTR{idVendor}=="413c", ATTR{bmAttributes}=="e0", \
> + ATTR{idVendor}=="413c", \
> ENV{REMOVE_CMD}="/sbin/udevadm trigger --action=change --subsystem-match=usb --property-match=HID2HCI_SWITCH=1"
We have two of these matches? The other one stays?
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
