From: Ben Hardill <b.hardill@gmail.com>
To: linux-input@vger.kernel.org, jkosina@suse.cz
Cc: Wayne Thomas <waynethomas69@gmail.com>
Subject: RE: [PATCH] HID: driver for BTC "Emprex 3009URF III Vista MCE Remote" quirky remote
Date: Sat, 27 Feb 2010 11:32:21 +0000 [thread overview]
Message-ID: <4B8902C5.5000508@gmail.com> (raw)
> > are using this usage page as standard. I was going to fiddle
> > around with this but instead will wait to see how this will be
> > implemented in udev. Sorry I couldn't relieve some of your
> > work-load.
>
> udev keymaps are described in README.keymap.txt in udev package. You
> can find current version on
>
http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=extras/keymap/README.keymap.txt;h=9c2d5dc16a151d57720b1dfe39e784f1b1d47367;hb=HEAD
>
>
>
Thanks,
Jiri,
I've tried to follow the instructions in the README.keymap but when I
run /lib/udev/keymap -i input/eventX against both of the event devices I
get nothing out, not even the "unknown" message mentioned in the doc.
I'm not totally up to speed with this yet, but I think i may be down to
the "e0x0ffbc0000 HID usage page" that Wayne mentioned earlier not being
read by the input layer and passed to the udev layer. If this is the
case then before udev can be used to make hardware like this work the
input layer will need to add support for this page.
Thanks,
Ben
next reply other threads:[~2010-02-27 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 11:32 Ben Hardill [this message]
2010-03-15 16:03 ` [PATCH] HID: driver for BTC "Emprex 3009URF III Vista MCE Remote" quirky remote Jiri Kosina
2010-03-17 19:18 ` Wayne Thomas
2010-03-18 10:51 ` Jiri Kosina
2010-03-18 11:00 ` Jiri Kosina
2010-03-18 20:03 ` Wayne Thomas
2010-04-20 18:29 ` Wayne Thomas
-- strict thread matches above, loose matches on Subject: below --
2009-12-31 8:13 Wayne Thomas
2010-01-02 2:53 ` Dmitry Torokhov
2010-01-02 9:52 ` Wayne Thomas
2010-01-02 21:25 ` Jiri Kosina
2010-01-18 10:33 ` Wayne Thomas
2010-02-17 15:20 ` 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=4B8902C5.5000508@gmail.com \
--to=b.hardill@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=waynethomas69@gmail.com \
/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).