From: "Taneli Vähäkangas" <taneli.vahakangas@welho.com>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Timo Aaltonen <tjaalton@cc.hut.fi>,
linux-input@vger.kernel.org
Subject: Re: support for Logitech Wave
Date: Thu, 17 Jan 2008 01:15:36 +0200 [thread overview]
Message-ID: <20080116231536.GA3844@localhost> (raw)
In-Reply-To: <Pine.LNX.4.64.0801162259350.15647@twin.jikos.cz>
On Wed, Jan 16, 2008 at 11:00:48PM +0100, Jiri Kosina wrote:
> On Wed, 16 Jan 2008, Taneli Vähäkangas wrote:
>
> > I tried the same on a Creative Prodikeys keyboard, but can't see any
> > events for some keys (most notably none of the "piano" keys work). Is
> > there anything that can be done to make it work?
>
> Hi Taneli,
>
> yes. Could you please grab reasonably recent kernel (2.6.24-rc<anything>
> would be ok), compile it with CONFIG_HID_DEBUG, modprobe the 'hid' module
> with 'debug=1' parameter, and send me the output from the time you connect
> the keyboard and from pressing the non-working keys? It should be trivial
> to fix then.
Thanks for prompt reply Jiri. Now I get some information for extra
function keys at the top row, but still nothing for the "piano" keys.
Here's the output for two previously non-functioning keys:
Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report (size 4)
(numbered)
Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report 4 (size 3) = 02 00 00
Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0
Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 1
Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0
Jan 17 00:27:13 newer last message repeated 13 times
Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report (size 4) (numbered)
Jan 17 00:27:13 newer kernel: drivers/hid/hid-core.c: report 4 (size 3) = 00 00 00
Jan 17 00:27:13 newer kernel: hid-debug: input ff00.0001 = 0
Jan 17 00:27:13 newer last message repeated 15 times
Is this the information you asked? I can make you the full mapping of
non-working keys to log messages. However, I don't think that's very
useful if the "piano" keys don't work, as they're the main reason for
having such a keyboard in the first place.
There was a great deal of log messages at the time of plugging in the
keyboard. I didn't feel comfortable spamming the list with it, so it is
available at:
http://www.cs.helsinki.fi/u/vahakang/hid-dbg.txt
(I think all the log entries after 00:23:59 are key presses, but
couldn't tell for sure.)
BTW, here's a picture of the keyboard in question ... just in case my
descriptions don't seem to make sense:
http://images.tw.creative.com/images/corporate/artwork/hires_prodikeyspcmidiusb.jpg
Cheers,
Taneli
-
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-01-16 23:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 13:49 support for Logitech Wave Timo Aaltonen
2008-01-16 16:07 ` Dmitry Torokhov
2008-01-16 21:58 ` Taneli Vähäkangas
2008-01-16 22:00 ` Jiri Kosina
2008-01-16 22:34 ` Timo Aaltonen
2008-01-16 22:40 ` Timo Aaltonen
2008-02-12 6:17 ` Timo Aaltonen
2008-02-12 11:34 ` Jiri Kosina
2008-02-12 11:42 ` Timo Aaltonen
2008-02-12 11:49 ` Jiri Kosina
2008-02-12 11:54 ` Timo Aaltonen
2008-01-16 23:15 ` Taneli Vähäkangas [this message]
2008-01-17 13:07 ` Jiri Kosina
2008-01-17 19:52 ` Taneli Vähäkangas
-- strict thread matches above, loose matches on Subject: below --
2008-04-24 23:12 Kevin Milburn
2008-04-28 6:59 ` Jiri Kosina
[not found] ` <200804281131.06389.linux-user@kmilburn.me.uk>
2008-04-30 9:21 ` Jiri Kosina
2008-04-30 10:41 ` Kevin Milburn
2008-04-30 17:30 ` Kevin Milburn
2008-05-01 12:27 ` Kevin Milburn
2008-05-07 9:36 ` Jiri Kosina
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=20080116231536.GA3844@localhost \
--to=taneli.vahakangas@welho.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@jikos.cz \
--cc=linux-input@vger.kernel.org \
--cc=tjaalton@cc.hut.fi \
/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).