From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wayne Thomas <waynethomas69@gmail.com>
Cc: jkosina@suse.cz, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: driver for BTC "Emprex 3009URF III Vista MCE Remote" quirky remote
Date: Fri, 1 Jan 2010 18:53:12 -0800 [thread overview]
Message-ID: <20100102025312.GC5788@core.coreip.homeip.net> (raw)
In-Reply-To: <3711715e0912310013u25e921cbqe6abb7c1621109e@mail.gmail.com>
Hi Wayne,
On Thu, Dec 31, 2009 at 09:13:22AM +0100, Wayne Thomas wrote:
> HID: driver for BTC "Emprex 3009URF III Vista MCE Remote" quirky remote
>
> The Behavior Tech. Computer Corp. (BTC) remote branded as "Emprex 3009URF III
> Vista Remote Controller" uses non-standard mappings for all of its 'special
> purpose' keys (0xffbc usage page). Applies cleanly to 2.6.30 and 2.6.32
> (other versions not tested).
> scripts/scriptpatch.pl reports 13 styling errors in hid-btc.c
> ("break;" should be on trailing lines)
> but have not changed them to maintain styling consistency with existing drivers.
>
I believe that this kind of mapping adjustment can be done via UDEV/HAL
key remapping facilities, without need for the kernel patch.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2010-01-02 2:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 8:13 [PATCH] HID: driver for BTC "Emprex 3009URF III Vista MCE Remote" quirky remote Wayne Thomas
2010-01-02 2:53 ` Dmitry Torokhov [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2010-02-27 11:32 Ben Hardill
2010-03-15 16:03 ` 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
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=20100102025312.GC5788@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).