All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: zitev <zitev@freemail.hu>
Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org, jkosina@suse.cz
Subject: Re: not supported hardware: Gigabyte K8100 Aivia USB Gaming Keyboard
Date: Sat, 28 Jan 2012 01:12:23 -0600	[thread overview]
Message-ID: <20120128071223.GA27331@burratino> (raw)
In-Reply-To: <4F230A1A.7080508@freemail.hu>

zitev wrote:

> I attached the lsusb output!

Perfect, thanks.

> Bus 001 Device 004: ID 1044:7a02 Chu Yuen Enterprise Co., Ltd 
[...]
>     bNumInterfaces          3
[...]
>     Interface Descriptor:
>       bInterfaceClass         3 Human Interface Device
>       iInterface              2 KB
[...]
>     Interface Descriptor:
>       bInterfaceClass         3 Human Interface Device
>       iInterface              3 Mouse
[...]
>     Interface Descriptor:
>       bInterfaceClass         3 Human Interface Device
>       iInterface              4 K8100 Interface

Can you set up usbmon and get a trace of e.g., pressing, holding,
then releasing the "a" key?  See Documentation/usb/usbmon.txt
in the Linux source or the doc directory of the linux-doc-3.2
package for details.

It works roughly like this:

1. Mount debugfs and load the usbmon module:

  mount -t debugfs debugfs /sys/kernel/debug
  modprobe usbmon

2. Start tracing:

  {
    sleep 1; # one second of quiet
    cat /sys/kernel/debug/usb/usbmon/1u >/tmp/mon.out &
    sleep 20; # twenty seconds or so to run the test
    kill $!; # and then stop collecting data
  }

3. Somehow summarize the output.  If it is fairly small, an
attachment is fine; otherwise, excerpts and maybe a link to a
copy that can be downloaded online might work.

Hope that helps,
Jonathan

  reply	other threads:[~2012-01-28  7:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D55AE81.3030805@freemail.hu>
     [not found] ` <20120126002100.GA4495@burratino>
     [not found]   ` <4F21C49D.2010906@freemail.hu>
     [not found]     ` <4F21C49D.2010906-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2012-01-26 21:39       ` not supported hardware: Gigabyte K8100 Aivia USB Gaming Keyboard Jonathan Nieder
2012-01-27 20:33         ` zitev
2012-01-28  7:12           ` Jonathan Nieder [this message]
2012-02-01 19:18             ` zitev
2012-02-01 19:35               ` Jonathan Nieder
2012-02-01 19:53                 ` zitev
2012-02-01 20:06               ` Jiri Kosina
2012-02-02 20:16                 ` zitev
2012-02-09 21:33                   ` Jiri Kosina
     [not found]                     ` <alpine.LNX.2.00.1202092231420.24127-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2012-02-11 10:05                       ` zitev
     [not found]                         ` <4F5A83ED.4000406@freemail.hu>
     [not found]                           ` <4F5A83ED.4000406-Y8qEzhMunLyT9ig0jae3mg@public.gmane.org>
2012-03-09 23:37                             ` Jonathan Nieder
2012-03-10  7:48                               ` zitev
2012-02-01 19:33             ` zitev

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=20120128071223.GA27331@burratino \
    --to=jrnieder@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=zitev@freemail.hu \
    /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.