Re: ir-keytable question [Ubuntu 17.04]

[Sean Young]

On Sat, Jul 29, 2017 at 01:46:07PM +0200, Matthias Reichl wrote:
> On Sat, Jul 29, 2017 at 11:23:22AM +0100, Sean Young wrote:
> > Hi,
> > 
> > On Sun, Jul 16, 2017 at 10:26:14PM -0700, Szabolcs Andrasi wrote:
> > > Hi,
> > > 
> > > I'm using Ubuntu 17.04 and I installed the ir-keytable tool. The
> > > output of the ir-keytable command is as follows:
> > > 
> > > 
> > > 
> > > Found /sys/class/rc/rc0/ (/dev/input/event5) with:
> > > Driver ite-cir, table rc-rc6-mce
> > > Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec
> > > sanyo mce_kbd rc-6 sharp xmp
> > > Enabled protocols: lirc rc-6
> > > Name: ITE8708 CIR transceiver
> > > bus: 25, vendor/product: 1283:, version: 0x
> > > Repeat delay = 500 ms, repeat period = 125 ms
> > > 
> > > 
> > > 
> > > I'm trying to enable the supported mce_kbd protocol in addition to the
> > > lirc and rc-6 protocols with the
> > > 
> > > $ sudo ir-keytable -p lirc -p rc-6 -p mce_kbd
> > > 
> > > command which works as expected. If, however, I reboot my computer,
> > > ir-keytable forgets this change and only the lirc and rc-6 protocols
> > > are enabled. Is there a configuration file I can edit so that after
> > > the boot my IR remote still works? Or is that so that the only way to
> > > make it work is to write a start-up script that runs the above command
> > > to enable the needed protocol?
> > 
> > So what we have today is /etc/rc_maps.cfg, where you can select the default
> > keymap for a particular driver; unfortunately, you can only select one
> > keymap and one keymap can only have one protocol.
> >
> > Ideally we could either have more than one protocol per keymap, which
> > would be helpful for the MCE Keyboard, or we could allow multiple keymaps
> > which would be great for supporting different remotes at the same time.
> 
> Having more than one protocol in the keymap file works fine here,
> we have been using that feature in LibreELEC for a long time now.
> Maybe it was just forgotten to document it?
> 
> $ git show 42511eb505
> commit 42511eb505b46b125652d37e764e5c8d1eb99e6b
> Author: Mauro Carvalho Chehab 
> Date:   Sat Apr 10 21:55:28 2010 -0300
> 
> ir-keytable: add support for more than one protocol in a table
> 
> Signed-off-by: Mauro Carvalho Chehab 
> 
> Quick test with ir-keytable 1.12.3 from Debian Stretch:

-snip-

Yes, you're right. I was wrong.

So, first of all, in recent kernels the "lirc" protocol is always enabled
and cannot be disabled. So there is no reason to explicitly enable it.

Now if you want to enable both rc-6 and mce_kbd, is that because you want
to use the Microsoft MCE IR keyboard? It uses both rc-6 and mce_kbd
protocol.

We should really have a keymap for this device; the only difference
with the rc6_mce keyboard is that mce_kbd protocol is also used.

Would that work?


Sean

Re: ir-keytable question [Ubuntu 17.04]

[Matthias Reichl]

On Sat, Jul 29, 2017 at 11:23:22AM +0100, Sean Young wrote:
> Hi,
> 
> On Sun, Jul 16, 2017 at 10:26:14PM -0700, Szabolcs Andrasi wrote:
> > Hi,
> > 
> > I'm using Ubuntu 17.04 and I installed the ir-keytable tool. The
> > output of the ir-keytable command is as follows:
> > 
> > 
> > 
> > Found /sys/class/rc/rc0/ (/dev/input/event5) with:
> > Driver ite-cir, table rc-rc6-mce
> > Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec
> > sanyo mce_kbd rc-6 sharp xmp
> > Enabled protocols: lirc rc-6
> > Name: ITE8708 CIR transceiver
> > bus: 25, vendor/product: 1283:, version: 0x
> > Repeat delay = 500 ms, repeat period = 125 ms
> > 
> > 
> > 
> > I'm trying to enable the supported mce_kbd protocol in addition to the
> > lirc and rc-6 protocols with the
> > 
> > $ sudo ir-keytable -p lirc -p rc-6 -p mce_kbd
> > 
> > command which works as expected. If, however, I reboot my computer,
> > ir-keytable forgets this change and only the lirc and rc-6 protocols
> > are enabled. Is there a configuration file I can edit so that after
> > the boot my IR remote still works? Or is that so that the only way to
> > make it work is to write a start-up script that runs the above command
> > to enable the needed protocol?
> 
> So what we have today is /etc/rc_maps.cfg, where you can select the default
> keymap for a particular driver; unfortunately, you can only select one
> keymap and one keymap can only have one protocol.
>
> Ideally we could either have more than one protocol per keymap, which
> would be helpful for the MCE Keyboard, or we could allow multiple keymaps
> which would be great for supporting different remotes at the same time.

Having more than one protocol in the keymap file works fine here,
we have been using that feature in LibreELEC for a long time now.
Maybe it was just forgotten to document it?

$ git show 42511eb505
commit 42511eb505b46b125652d37e764e5c8d1eb99e6b
Author: Mauro Carvalho Chehab 
Date:   Sat Apr 10 21:55:28 2010 -0300

ir-keytable: add support for more than one protocol in a table

Signed-off-by: Mauro Carvalho Chehab 

Quick test with ir-keytable 1.12.3 from Debian Stretch:

$ sudo ir-keytable -c -p lirc,rc-6 -s rc1
Old keytable cleared
Protocols changed to lirc rc-6

$ sudo ir-keytable -r -s rc1
Enabled protocols: lirc rc-6

$ cat /etc/rc_keymaps/rc6_mce_kbd_test
# table test, type:rc-6,mce_kbd
0x01KEY_1

$ cat test-map.cfg
* * rc6_mce_kbd_test

$ sudo ir-keytable -a test-map.cfg -s rc1
Old keytable cleared
Wrote 1 keycode(s) to driver
Protocols changed to mce_kbd rc-6

$ sudo ir-keytable -r -s rc1
scancode 0x0001 = KEY_1 (0x02)
Enabled protocols: lirc mce_kbd rc-6

so long,

Hias

> 
> For now, you could add a udev rule to also enable the mce_kbd protocol.
> 
> 
> Sean

Re: ir-keytable question [Ubuntu 17.04]

[Sean Young]

Hi,

On Sun, Jul 16, 2017 at 10:26:14PM -0700, Szabolcs Andrasi wrote:
> Hi,
> 
> I'm using Ubuntu 17.04 and I installed the ir-keytable tool. The
> output of the ir-keytable command is as follows:
> 
> 
> 
> Found /sys/class/rc/rc0/ (/dev/input/event5) with:
> Driver ite-cir, table rc-rc6-mce
> Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec
> sanyo mce_kbd rc-6 sharp xmp
> Enabled protocols: lirc rc-6
> Name: ITE8708 CIR transceiver
> bus: 25, vendor/product: 1283:, version: 0x
> Repeat delay = 500 ms, repeat period = 125 ms
> 
> 
> 
> I'm trying to enable the supported mce_kbd protocol in addition to the
> lirc and rc-6 protocols with the
> 
> $ sudo ir-keytable -p lirc -p rc-6 -p mce_kbd
> 
> command which works as expected. If, however, I reboot my computer,
> ir-keytable forgets this change and only the lirc and rc-6 protocols
> are enabled. Is there a configuration file I can edit so that after
> the boot my IR remote still works? Or is that so that the only way to
> make it work is to write a start-up script that runs the above command
> to enable the needed protocol?

So what we have today is /etc/rc_maps.cfg, where you can select the default
keymap for a particular driver; unfortunately, you can only select one
keymap and one keymap can only have one protocol.

Ideally we could either have more than one protocol per keymap, which
would be helpful for the MCE Keyboard, or we could allow multiple keymaps
which would be great for supporting different remotes at the same time.

For now, you could add a udev rule to also enable the mce_kbd protocol.


Sean

ir-keytable question [Ubuntu 17.04]

[Szabolcs Andrasi]

Hi,

I'm using Ubuntu 17.04 and I installed the ir-keytable tool. The
output of the ir-keytable command is as follows:



Found /sys/class/rc/rc0/ (/dev/input/event5) with:
Driver ite-cir, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec
sanyo mce_kbd rc-6 sharp xmp
Enabled protocols: lirc rc-6
Name: ITE8708 CIR transceiver
bus: 25, vendor/product: 1283:, version: 0x
Repeat delay = 500 ms, repeat period = 125 ms



I'm trying to enable the supported mce_kbd protocol in addition to the
lirc and rc-6 protocols with the

$ sudo ir-keytable -p lirc -p rc-6 -p mce_kbd

command which works as expected. If, however, I reboot my computer,
ir-keytable forgets this change and only the lirc and rc-6 protocols
are enabled. Is there a configuration file I can edit so that after
the boot my IR remote still works? Or is that so that the only way to
make it work is to write a start-up script that runs the above command
to enable the needed protocol?

Thank you in advance!

-- Szabolcs