From: Matthias Reichl <hias@horus.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-media@vger.kernel.org
Subject: [PATCH] v4l-utils: fix invalid protocol in streamzap keymap
Date: Fri, 17 Feb 2017 10:19:16 +0100 [thread overview]
Message-ID: <20170217091916.GA24266@camel2.lan> (raw)
ir-keytable can't load the streamzap keymap because the
protocol type RC5_SZ is invalid:
./ir-keytable -w rc_keymaps/streamzap
Protocol RC5_SZ invalid
...
Fix this by changing the protocol type to RC-5-SZ which
matches the kernel protocol rc-5-sz
Signed-off-by: Matthias Reichl <hias@horus.com>
---
utils/keytable/rc_keymaps/streamzap | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utils/keytable/rc_keymaps/streamzap b/utils/keytable/rc_keymaps/streamzap
index 3512cd8..03d2cb8 100644
--- a/utils/keytable/rc_keymaps/streamzap
+++ b/utils/keytable/rc_keymaps/streamzap
@@ -1,4 +1,4 @@
-# table streamzap, type: RC5_SZ
+# table streamzap, type: RC-5-SZ
0x28c0 KEY_NUMERIC_0
0x28c1 KEY_NUMERIC_1
0x28c2 KEY_NUMERIC_2
--
2.1.4
next reply other threads:[~2017-02-17 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 9:19 Matthias Reichl [this message]
2017-02-18 19:24 ` [PATCH] v4l-utils: fix invalid protocol in streamzap keymap Sean Young
2017-02-20 17:33 ` Matthias Reichl
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=20170217091916.GA24266@camel2.lan \
--to=hias@horus.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.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