From: Jarod Wilson <jarod@redhat.com>
To: "David Härdeman" <david@hardeman.nu>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
Jarod Wilson <jarod@wilsonet.com>,
linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] Apple remote support
Date: Thu, 18 Nov 2010 15:49:52 -0500 [thread overview]
Message-ID: <20101118204952.GC16899@redhat.com> (raw)
In-Reply-To: <20101118204319.GA8213@hardeman.nu>
On Thu, Nov 18, 2010 at 09:43:19PM +0100, David Härdeman wrote:
> On Thu, Nov 18, 2010 at 11:33:04AM -0500, Jarod Wilson wrote:
> >Mauro's suggestion, iirc, was that max scancode size should be a
> >property of the keytable uploaded, and something set at load time (and
> >probably exposed as a sysfs node, similar to protocols).
>
> I think that would be a step in the wrong direction. It would make the
> keytables less flexible while providing no real advantages.
I think it was supposed to be something you could update on the fly when
uploading new keys, so its not entirely inflexible. Default keymap might
be 24-bit NEC, then you upload 32-bit NEC codes, and the max scancode size
would get updated at the same time. Of course, it probably wouldn't work
terribly well to have a mix of 24-bit and 32-bit NEC codes in the same
table.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2010-11-18 20:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 3:11 [RFC PATCH 0/2] Apple remote support Jarod Wilson
2010-10-29 3:13 ` [RFC PATCH 1/2] ir-nec-decoder: decode Apple's NEC remote variant Jarod Wilson
2010-10-29 22:15 ` Andy Walls
2010-10-29 3:13 ` [RFC PATCH 2/2] IR: add Apple remote keymap Jarod Wilson
2010-10-29 3:15 ` [RFC PATCH 0/2] Apple remote support Jarod Wilson
2010-10-29 13:46 ` Mauro Carvalho Chehab
2010-10-29 15:11 ` Jarod Wilson
2010-10-29 19:17 ` David Härdeman
2010-10-29 19:27 ` Jarod Wilson
2010-10-29 19:59 ` David Härdeman
2010-10-29 20:09 ` Jarod Wilson
2010-10-30 23:36 ` David Härdeman
2010-10-31 2:32 ` Jarod Wilson
2010-11-01 21:56 ` David Härdeman
2010-11-02 20:42 ` Jarod Wilson
2010-11-04 12:16 ` David Härdeman
2010-11-04 15:54 ` Jarod Wilson
2010-11-04 19:38 ` David Härdeman
2010-11-04 19:43 ` Mauro Carvalho Chehab
2010-11-05 13:27 ` David Härdeman
2010-11-05 14:04 ` Christopher Harrington
2010-11-07 19:01 ` Jarod Wilson
2010-11-15 4:11 ` Jarod Wilson
2010-11-15 18:39 ` David Härdeman
2010-11-16 12:08 ` Mauro Carvalho Chehab
2010-11-16 23:26 ` David Härdeman
2010-11-18 16:33 ` Jarod Wilson
2010-11-18 20:43 ` David Härdeman
2010-11-18 20:49 ` Jarod Wilson [this message]
2010-11-18 20:59 ` Mauro Carvalho Chehab
2010-11-19 23:55 ` David Härdeman
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=20101118204952.GC16899@redhat.com \
--to=jarod@redhat.com \
--cc=david@hardeman.nu \
--cc=jarod@wilsonet.com \
--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).