From: Mark Lord <lkml@rtr.ca>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: Input driver for Twinhan USB 6253:0100 remote control
Date: Wed, 15 Apr 2009 10:10:31 -0400 [thread overview]
Message-ID: <49E5EAD7.7000309@rtr.ca> (raw)
In-Reply-To: <alpine.LNX.2.00.0904151022170.13028@wotan.suse.de>
Jiri Kosina wrote:
> On Tue, 14 Apr 2009, Mark Lord wrote:
>
>>> 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.
>
> Yes, hid-belking is a good example of trivial driver that sits on a HID
> bus for you, as it utilizes the ->input_mapping() callback, which is
> probably the only callback from HID core you'd need.
..
Actually, the input-mapping() alone won't do the job here.
This Twinhan remote control sends single-byte codes for most buttons,
but some buttons send multi-byte codes, and we have to discard the
extraneous bytes somehow.
Cheers
next prev parent reply other threads:[~2009-04-15 14:10 UTC|newest]
Thread overview: 18+ 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
2009-04-15 8:23 ` Jiri Kosina
2009-04-15 14:10 ` Mark Lord [this message]
2009-04-16 9:24 ` Jiri Kosina
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 11:21 ` Jiri Kosina
2009-07-13 12:19 ` [PATCH] HID: " 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=49E5EAD7.7000309@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox