From mboxrd@z Thu Jan 1 00:00:00 1970 From: Octoploid Subject: Re: Logitech M705 thumb button Date: Sun, 11 Apr 2010 18:29:47 +0200 Message-ID: References: <319012f1003300033k254715dao7f9a807615df36df@mail.gmail.com> <319012f1003300602q708563ebo90b30c8d8b15e938@mail.gmail.com> <4BC1F110.4030203@yahoo.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Return-path: Received: from fg-out-1718.google.com ([72.14.220.159]:63689 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752156Ab0DKQ3t (ORCPT ); Sun, 11 Apr 2010 12:29:49 -0400 Received: by fg-out-1718.google.com with SMTP id 22so445129fge.1 for ; Sun, 11 Apr 2010 09:29:47 -0700 (PDT) In-Reply-To: <4BC1F110.4030203@yahoo.de> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Robert Schedel Cc: Jiri Kosina , Dmitry Torokhov , linux-input@vger.kernel.org On Sun, Apr 11, 2010 at 5:56 PM, Robert Schedel wrote: > Hello, > > On 02.04.2010 13:27, Octoploid wrote: > [...] >>>> 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. >> >> OK, I have downloaded a trial version of a usb-monitor and >> recorded the following initialization sequence. >> Let me know it this helps. >> >> http://pastebin.org/131184 > > You did not add info at which time you pressed which button, e.g. thumb button. Basically: pull out the USB receiver, then plug it in and press the thumb button a couple of times (which is kind of hard without involuntarily moving the mouse). > But, OK, init sequence is more important: Looking for "(DOWN)", there are several device-specific control blocks which resemble those sent by "lomoco" or other mouse tools for configuring Logitech features. > > Example, request 0x9, value 0x210, sent downstream: > > # 002448: Control Transfer (DOWN), 02.04.2010 11:14:55.341 +0.0 > # Pipe Handle: 0x0 > # Recipient: Interface > # Request Type: Class > # Direction: Host->Device > # Request: 0x9 (Unknown) > # Value: 0x210 > # Index: 0x2 > # Length: 0x7 > > My guess is, some new init trigger is required from a userspace tool (only) to enable thumb button, no kernel issue. This is difficult to analyze though w/o the device available and w/o spec. You might > a) fiddle with lomoco source code yourself, e.g. making the existing features work first + adding feature bits found in your protocol > b) get in touch with the developers > c) wait for someone more experienced to get the mouse and analyze I choose option c) then ;-) (I have no experience in this area whatsoever, and hoped that some USB (HID) guru might see what is going on by just reading the log.)