Bug#901965: hid2hci.patch

2019-12-23 Thread Jean-Marc 
Hi bluez maintainers,

A person got in touch with debian-user-french people asking for help because 
she was facing the issue described in this bug report.

I wonder if there is any progress on finding a solution ?

For info, this problem is also mentionned in the bug report #889110 ([1])
(closed by Michael Biebl  on 9 Feb 2018).

And in the RedHat Bug 1563554 ([2]) suggesting a workaround by just adding 
 in front of the line containing  in the file /lib/udev/rules.d/97-hid2hci.rules.

Can you, please, advice what is the best solution to, at least, mitigate the 
risk of being hit by this bug ?  Specifying the ACTION like described in the RH 
bugreport or using the driver usbhid like in the Тут Root's proposed patch.

And about further investigations, unfortunately, I cannot reproduce the bug 
and, then, I am not able to investigate further to know if it is really a 
driver or kernel bug.

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt

[1] https://bugs.debian.org/889110
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1563554


pgpMRzCyEtr6N.pgp
Description: PGP signature

Bug#901965: hid2hci.patch

2019-04-27 Thread Тут Root 

*** lib_udev_rules.d_97-hid2hci.rules	2019-04-27 13:11:06.009105863 +0300
--- /lib/udev/rules.d/97-hid2hci.rules	2019-04-27 13:54:48.747630419 +0300
*** SUBSYSTEM!="usb*", GOTO="hid2hci_end"
*** 8,13 
--- 8,14 
  # Known supported devices: 413c:8154, 413c:8158, 413c:8162
  ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", ATTR{bInterfaceProtocol}=="02", \
ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", ATTRS{bmAttributes}=="e0", \
+   DRIVER=="usbhid", \
RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
  
  # Logitech devices