From: "Frédéric Deghetto" <frederic.deghetto@gmail.com>
To: linux-media@vger.kernel.org
Subject: rc rc0: two consecutive events of type space & strange ir-keytable behaviour
Date: Fri, 24 May 2019 06:12:50 +0200 [thread overview]
Message-ID: <ff3cbf92-3f43-2a85-68d3-35f9086aa393@gmail.com> (raw)
Good day,
Information on the system:
- Raspberry 3b+
- Updated yesterday to 4.19.42-v7+
Before the update the remote control was working well with:
- gpio-rc-recv rc-rc6-mce kodi (into the file rc_maps.cfg)
- And the following data into /etc/rc_keymaps/kodi:
# table kodi, type: NEC
0x140 KEY_POWER
0x1ff KEY_TAB
0x143 KEY_RED
0x10f KEY_GREEN
0x110 KEY_MINUS
0x118 KEY_VOLUMEUP
0x111 KEY_ESC
0x119 KEY_BACKSPACE
0x116 KEY_UP
0x151 KEY_LEFT
0x113 KEY_ENTER
0x150 KEY_RIGHT
0x11a KEY_DOWN
0x14c KEY_EPG
0x100 KEY_C
0x14e KEY_1
0x10d KEY_2
0x10c KEY_3
0x14a KEY_4
0x109 KEY_5
0x108 KEY_6
0x146 KEY_7
0x105 KEY_8
0x104 KEY_9
0x141 KEY_F8
0x101 KEY_0
0x142 KEY_DELETE
Since the kernel update I get this message from dmesg: "rc rc0: two
consecutive events of type space", and the remote control doesn't work.
I tried to force the protocol NEC with ir-keytable -t -p NEC and I can
this some events. Something strange, when I push a button I can get the
event of the previous pushed button. By insisting I get the right one.
I went to google and didn't see any workaround.
Many thanks for your support,
Frederic
next reply other threads:[~2019-05-24 4:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 4:12 Frédéric Deghetto [this message]
2019-05-24 5:31 ` rc rc0: two consecutive events of type space & strange ir-keytable behaviour Frédéric Deghetto
2019-05-24 7:40 ` Sean Young
[not found] ` <CACRW-tjVokBnZNNVPKH64Cu19Xe3Xd+abZfVODegpOxiORwhMw@mail.gmail.com>
2019-05-24 9:54 ` Sean Young
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=ff3cbf92-3f43-2a85-68d3-35f9086aa393@gmail.com \
--to=frederic.deghetto@gmail.com \
--cc=linux-media@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