From: "David Härdeman" <david@hardeman.nu>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org, sean@mess.org
Subject: Re: [PATCH 0/2] NEC scancodes and protocols in keymaps
Date: Fri, 3 Apr 2015 09:28:33 +0200 [thread overview]
Message-ID: <20150403072833.GA26445@hardeman.nu> (raw)
In-Reply-To: <20150402135637.28ec4dbf@recife.lan>
On Thu, Apr 02, 2015 at 01:56:37PM -0300, Mauro Carvalho Chehab wrote:
>Em Thu, 02 Apr 2015 14:02:57 +0200
>David Härdeman <david@hardeman.nu> escreveu:
>
>> The following two patches should show more clearly what I mean by
>> adding protocols to the keytables (and letting userspace add
>> keytable entries with explicit protocol information). Consider
>> it a basis for discussion.
>>
>> Each patch has a separate description, please refer to those for
>> more information.
>
>Interesting approach. It would be good to also have a patch for
>v4l-utils rc-keycode userspace, for it to use the new way when
>available. An option to fallback to the old way would also be
>useful, in order to allow testing the backward compatibility.
Ok, yes, that'd be good to have, I'll look into it.
--
David Härdeman
prev parent reply other threads:[~2015-04-03 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 12:02 [PATCH 0/2] NEC scancodes and protocols in keymaps David Härdeman
2015-04-02 12:03 ` [PATCH 1/2] rc-core: use the full 32 bits for NEC scancodes David Härdeman
2015-04-02 12:03 ` [PATCH 2/2] rc-core: don't throw away protocol information David Härdeman
2015-04-02 16:56 ` [PATCH 0/2] NEC scancodes and protocols in keymaps Mauro Carvalho Chehab
2015-04-03 7:28 ` David Härdeman [this message]
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=20150403072833.GA26445@hardeman.nu \
--to=david@hardeman.nu \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=sean@mess.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.