From: Mark Lord <lkml@rtr.ca>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: Input driver for Twinhan USB 6253:0100 remote control
Date: Tue, 14 Apr 2009 13:37:19 -0400 [thread overview]
Message-ID: <49E4C9CF.5060504@rtr.ca> (raw)
In-Reply-To: <200904140945.14652.dmitry.torokhov@gmail.com>
Dmitry Torokhov wrote:
> On Tuesday 14 April 2009 09:14:48 Mark Lord wrote:
>> Dmitry Torokhov wrote:
>>> Hi Mark,
>>>
>>> On Wednesday 08 April 2009 10:28:09 Mark Lord wrote:
>>>> Dmitry,
>>>>
>>>> I briefly had access to a Twinhan remote control (for Mythtv et al.)
>>>> and cobbled something together quickly to make it work.
>>>>
>>>> But I really don't understand the new hid/input stuff,
>>>> so this is undoubtedly a total abomination to your eyes. :)
>>> Actually HID is Juri's baby so let's see what he says ;). From my POV
>>> we need to update keymap to make it emit proper codes instead of Myth
>>> specific ones, but that is a lesser issue.
>> ..
>>
>> That's one thing I haven't figured out: how to make this compatible
>> with the userspace intput-kbd interface for loading new key maps and stuff.
>>
>
> You will need to convert your patch into proper hid_driver and
> implement drv->input_mapping() method instead of overriding emitted
> events. Then, once HID core is aware about proper mapping, normal
> EVIOCGKEYCODE/EVIOCSKEYCODE will work and will allow adjusting
> keymap from user space.
..
I tried that earlier, but input-kbd only ever listed a single (wrong)
key in the keymap, and wouldn't allow changing anything.
Obviously there's more to it somewhere, I guess.
> I think if you take drivers/hid/hid-belkin.c as a template the
> conversion will take you no time.
..
Okay, I can have a look at that one. Thanks.
next prev parent reply other threads:[~2009-04-14 17:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 7:29 [git pull] Input updates for 2.6.30-rc1 Dmitry Torokhov
2009-04-08 17:28 ` Input driver for Twinhan USB 6253:0100 remote control Mark Lord
2009-04-14 2:31 ` Dmitry Torokhov
2009-04-14 16:14 ` Mark Lord
2009-04-14 16:45 ` Dmitry Torokhov
2009-04-14 17:37 ` Mark Lord [this message]
2009-04-15 8:23 ` Jiri Kosina
2009-04-15 14:10 ` Mark Lord
2009-04-16 9:24 ` Jiri Kosina
2009-07-12 16:20 ` Bruno Prémont
2009-07-12 16:20 ` Bruno Prémont
2009-07-13 3:41 ` Dmitry Torokhov
2009-07-13 8:53 ` Jiri Kosina
2009-07-13 9:31 ` Bruno Prémont
2009-07-13 9:31 ` Bruno Prémont
2009-07-13 11:21 ` Jiri Kosina
2009-07-13 12:19 ` [PATCH] HID: " Bruno Prémont
2009-07-13 12:19 ` Bruno Prémont
2009-07-14 15:05 ` Jiri Kosina
2009-07-18 14:50 ` Mark Lord
2009-04-13 1:03 ` [git pull] Input updates for 2.6.30-rc1 Dmitry Torokhov
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=49E4C9CF.5060504@rtr.ca \
--to=lkml@rtr.ca \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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.