From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Logitech m310 mouse issues
Date: Mon, 4 Mar 2013 11:47:46 +0000 [thread overview]
Message-ID: <9748a8d72cbfe3a8308d9b1348b8a215@hamnavoe.com> (raw)
In-Reply-To: <d041036f-2d8c-4586-958d-fd3874c661dc@googlegroups.com>
> But I was able to get some info, by adding 'kbargs=-k' to the cmdline.txt.
That stops the kernel usb daemon from starting the mouse driver automatically,
so you have the opportunity to start it by hand with 'usb/kb -d'. Once you've
started that, it seizes control of the usb endpoint so the subsequent 'usb/kb'
commands tell you "no unhandled devices".
The "setting first config" and "setting boot protocol" messages indicate that
the attempt to set the mouse into HID report mode fails, so the driver falls
back to boot protocol which every device with CSP 3.1.2 should support. Either
your mouse has a different notion of boot protocol from what the driver's
author expected, or the raspberry pi's somewhat problematic USB hardware is
losing some input characters and causing the protocol to get out of sync.
In my contrib area there is now a usb-kb program. If you try that in place
of usb/kb, with argument '-ddd' for lots of debugging, it should tell you
exactly which command failed in the attempt to set HID report protocol, and
will also dump the raw data read from the mouse in boot protocol.
next prev parent reply other threads:[~2013-03-04 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 9:38 atvdude01
2012-12-07 10:35 ` Richard Miller
2013-03-01 10:33 ` Boo
2013-03-01 10:51 ` Richard Miller
2013-03-04 10:11 ` Boo
2013-03-04 11:47 ` Richard Miller [this message]
2012-12-07 12:37 ` Richard Miller
2012-12-07 12:53 ` Gorka Guardiola
2012-12-07 13:32 ` Richard Miller
2012-12-14 10:21 ` Richard Miller
2012-12-07 16:07 ` [9fans] Logitech m310 mouse issues & SSH va3yh
2012-12-07 16:18 ` Bence Fábián
2012-12-10 9:37 ` [9fans] Logitech m310 mouse issues Thomas Cenova
2012-12-10 9:37 ` Chris Sexton
2012-12-10 11:34 ` Richard Miller
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=9748a8d72cbfe3a8308d9b1348b8a215@hamnavoe.com \
--to=9fans@hamnavoe.com \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).