On Fri, Apr 2, 2010 at 12:05 PM, Jiri Kosina <jkosina@xxxxxxx> wrote: > On Wed, 31 Mar 2010, Octoploid wrote: > >> >> (The »unifying USB reciever« has three sub-devices. The first one is >> >> for keyboards, the second for mouses and the third is not used: >> >> usb 3-1: new full speed USB device using ohci_hcd and address 2 >> >> input: Logitech USB Receiver as >> >> /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.0/input/input2 >> >> generic-usb 0003:046D:C52B.0001: input,hidraw0: USB HID v1.11 Keyboard >> >> [Logitech USB Receiver] on usb-0000:00:12.0-1/input0 >> >> input: Logitech USB Receiver as >> >> /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.1/input/input3 >> >> generic-usb 0003:046D:C52B.0002: input,hiddev96,hidraw1: USB HID v1.11 >> >> Mouse [Logitech USB Receiver] on usb-0000:00:12.0-1/input1 >> >> generic-usb 0003:046D:C52B.0003: hiddev97,hidraw2: USB HID v1.11 >> >> Device [Logitech USB Receiver] on usb-0000:00:12.0-1/input2) >> >> >> >> The rdesc output for the mouse and the third device follows: >> > >> > Thanks for providing the output. >> > >> > The device defines 16 buttons in its report descriptor. How much does it >> > actually physically have? >> >> 8 if I count correctly (left,middle,right,scrollwheel left,scrollwheel right, >> forward, backward and the hidden (the non working) thumb button). >> Here is a photo of the mouse (the hidden button is located under the >> white underscore below the back and forward buttons): >> http://www.techfresh.net/wp-content/uploads/2010/03/logitech_m705.jpg >> >> > Is the other (non-used) interface also silent when you press the >> > non-working button? (I can see that it is claimed by HID as well). >> >> Yes. >> >> > Could you please apply the patch below and check whether there is still no >> > event present when you press the button? >> > >> >> Yes, unfortunately there are still no events even with the patch applied. >> (I've tested both interfaces) > > Could you please verify that there is indeed no USB event being triggered > by the button press at all, with usbmon [1]? I already verified this, but forgot to mention it in my last mail. There are indeed no USB events being triggered when I run "cat /sys/kernel/debug/usb/usbmon/ou". > If it is the case, I am afraid the only option would be inspecting what > initialization sequence does the driver for Another OS perform, so that it > makes the button work. Any pointers on how I could accomplish this? Thanks in advance. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
