From: Kevin Milburn <linux-user@kmilburn.me.uk>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: support for Logitech Wave
Date: Wed, 30 Apr 2008 11:41:08 +0100 [thread overview]
Message-ID: <200804301141.08619.linux-user@kmilburn.me.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0804301119050.7756@jikos.suse.cz>
On Wednesday 30 April 2008 10:21:16 Jiri Kosina wrote:
> The keyboard probably has two separate interfaces, with some multimedia
> keys being reported on a different one. That's why you see them in evbug
> output, but not in evtest output, because they appear under different
> event device.
I''m sure I tried that before, but from retesting today I guess I didn't....
You're right, the missing keys reported by evbug are showing up in evtest
when I connect to the second event interface, a.k.a
usb-Logitech_USB_Receiver-event-mouse.
so it is just the ones that evbug wasn't reporting that are missing...
Looks like I need to have some fun with getting xkbd and evdev in X working
properly.....
TIA
Kev.
next prev parent reply other threads:[~2008-04-30 10:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 23:12 support for Logitech Wave 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 [this message]
2008-04-30 17:30 ` Kevin Milburn
2008-05-01 12:27 ` Kevin Milburn
2008-05-07 9:36 ` Jiri Kosina
-- strict thread matches above, loose matches on Subject: below --
2008-01-15 13:49 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
2008-01-17 13:07 ` Jiri Kosina
2008-01-17 19:52 ` Taneli Vähäkangas
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=200804301141.08619.linux-user@kmilburn.me.uk \
--to=linux-user@kmilburn.me.uk \
--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.