All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schedel <r.schedel@yahoo.de>
To: Octoploid <cryptooctoploid@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: Logitech M705 thumb button
Date: Sun, 11 Apr 2010 17:56:00 +0200	[thread overview]
Message-ID: <4BC1F110.4030203@yahoo.de> (raw)
In-Reply-To: <v2x319012f1004020427t86509b85yb68e9fd7df50a5ef@mail.gmail.com>

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.

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

Regards,
Robert Schedel

  reply	other threads:[~2010-04-11 16:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 13:40 Logitech M705 thumb button Octoploid
2010-03-30  6:56 ` Dmitry Torokhov
2010-03-30  7:33   ` Octoploid
2010-03-30 12:28     ` Jiri Kosina
2010-03-30 13:02       ` Octoploid
2010-03-31 12:05         ` Jiri Kosina
2010-03-31 12:54           ` Octoploid
2010-04-02 10:05             ` Jiri Kosina
2010-04-02 10:28               ` Octoploid
2010-04-02 11:27                 ` Octoploid
2010-04-11 15:56                   ` Robert Schedel [this message]
2010-04-11 16:29                     ` Octoploid
2010-05-03 10:42                       ` Cristian Măgherușan-Stanciu
2010-05-03 17:41                         ` Octoploid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BC1F110.4030203@yahoo.de \
    --to=r.schedel@yahoo.de \
    --cc=cryptooctoploid@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.