From: Jarod Wilson <jarod@wilsonet.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Jarod Wilson <jarod@redhat.com>,
mchehab@redhat.com, linux-media@vger.kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 2/3] ir-core: add imon pad and mce keymaps
Date: Sat, 24 Apr 2010 16:53:09 -0400 [thread overview]
Message-ID: <i2mbe3a4a1004241353x2f362576x903aa1393c8f55af@mail.gmail.com> (raw)
In-Reply-To: <20100424085321.GA2668@hardeman.nu>
On Sat, Apr 24, 2010 at 4:53 AM, David Härdeman <david@hardeman.nu> wrote:
> On Fri, Apr 16, 2010 at 05:28:35PM -0400, Jarod Wilson wrote:
>>
>> This adds the keymaps for the hardware decode scancodes imon
>> devices create for their native imon pad (and mini) remotes,
>> and the hardware scancodes generated by the imon devices when
>> used with an rc6 windows media center ed. remote.
...
>> +/* mce-mode imon mce remote key table */
>> +static struct ir_scancode imon_mce[] = {
>> + /* keys sorted mostly by frequency of use to optimize lookups */
>
> Won't help at all, entries are inserted in scancode order in the actual
> in-kernel keytable to allow for binary scancode searches.
Ah, yeah, that'd be some "legacy" cruft from when the driver was using
its own internal key table and lookups, making mental note to remove
those comments...
--
Jarod Wilson
jarod@wilsonet.com
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-04-24 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 21:26 [PATCH 0/3] ir-core: add imon device driver Jarod Wilson
2010-04-16 21:27 ` [PATCH 1/3] ir-core: make ir_g_keycode_from_table a public function Jarod Wilson
2010-04-16 21:28 ` [PATCH 2/3] ir-core: add imon pad and mce keymaps Jarod Wilson
2010-04-24 8:53 ` David Härdeman
2010-04-24 20:53 ` Jarod Wilson [this message]
2010-04-16 21:29 ` [PATCH 3/3] ir-core: add imon driver Jarod Wilson
2010-04-20 21:22 ` Mauro Carvalho Chehab
2010-04-22 1:55 ` Jarod Wilson
2010-04-22 13:36 ` Mauro Carvalho Chehab
2010-04-23 5:23 ` Jarod Wilson
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=i2mbe3a4a1004241353x2f362576x903aa1393c8f55af@mail.gmail.com \
--to=jarod@wilsonet.com \
--cc=david@hardeman.nu \
--cc=jarod@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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).