From: Corentin Chary <corentin.chary@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org
Subject: MX5000 support in hid-logitech
Date: Tue, 15 Sep 2009 12:40:14 +0200 [thread overview]
Message-ID: <200909151240.14486.corentin.chary@gmail.com> (raw)
Hi,
I'm trying to add support for MX5000 keyboard in hid-lg.c, and it's the first
time I'm playing with hid drivers.
I added the keys in lg_wireless_mapping()
case 0x01b8: lg_map_key_clear(KEY_VIDEO); break;
case 0x01b7: lg_map_key_clear(KEY_AUDIO); break;
case 0x01bc: lg_map_key_clear(KEY_MESSENGER); break;
case 0x0183: lg_map_key_clear(KEY_MEDIA); break;
case 0x0230: lg_map_key_clear(KEY_ZOOMRESET); break;
case 0x022e: lg_map_key_clear(KEY_ZOOMOUT); break;
case 0x022d: lg_map_key_clear(KEY_ZOOMIN); break;
case 0x0184: lg_map_key_clear(KEY_WORDPROCESSOR); break;
case 0x0186: lg_map_key_clear(KEY_SPREADSHEET); break;
case 0x0188: lg_map_key_clear(KEY_PRESENTATION); break;
And that line in static const struct hid_device_id lg_devices[]
{ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, 0xc70a),
.driver_data = LG_RDESC | LG_WIRELESS },
I also added a printk lg_event() to find usage->hid and check
if the device was correctly probed.
I use xev to detect keystrocks.
But Adding the code in lg_wireless_mapping() didn't change anything, keys are
not reported in xev.
I added a printk between case 0x01b8: and lg_map_key_clear(KEY_VIDEO); to
check if the branch was taken, and it is.
Did I do something wrong ?
Any suggestion ?
(Please CC me, I didn't subscribed to linux-input)
Thanks,
--
Corentin Chary
http://xf.iksaif.net
next reply other threads:[~2009-09-15 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 10:40 Corentin Chary [this message]
2009-09-15 11:03 ` MX5000 support in hid-logitech Bastien Nocera
2009-09-15 12:44 ` Corentin Chary
2009-09-15 13:52 ` Corentin Chary
2009-09-15 14:34 ` Jiri Kosina
2009-09-15 16:04 ` Corentin Chary
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=200909151240.14486.corentin.chary@gmail.com \
--to=corentin.chary@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 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).