* Re: Missing Protocols ir-keytable Ubuntu 20.04
[not found] <6446b77c-e6de-9d0a-2ed3-691481917b80@gmx.de>
@ 2020-06-02 16:08 ` Sean Young
2020-06-09 6:10 ` Peter Hutterer
0 siblings, 1 reply; 3+ messages in thread
From: Sean Young @ 2020-06-02 16:08 UTC (permalink / raw)
To: linux-media, linux-input, wayland-devel; +Cc: Ralf Schmidt
Hi,
On Wed, May 06, 2020 at 02:35:32PM +0200, Ralf Schmidt wrote:
> On more thing: because off the removed -d parameter, Remotes like the
> Technisat TTS35AI are no longer supported, such Type of Remotes are not
> recognized in /sys/class/rc/.
So I'm now the proud owner of this device.
This device is a usb dongle which is an IR receiver, but self-describes
as a usb hid keyboard device. It comes with a remote.
As far as I can figure out, there is no way to reprogram it.
So users have been re-mapping scancodes to different keycodes using:
ir-keytable -d /dev/input/eventN -c -k 0x12:KEY_F1
However, ir-keytable was designed load keymaps for rc devices, not hid
devices. This functionality was intentionally removed, as it was buggy
in many ways. ir-keytable does not exist for remapping usb hid keyboards.
This has left some users like Ralf in a situation where they can no longer
change the key mappings for their remote.
ir-keytable is probably not the right way to do this; it has no rules to
do this from udev, for example. What tooling is there for doing this
and what is the recommended way to do this?
Sean
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Missing Protocols ir-keytable Ubuntu 20.04
2020-06-02 16:08 ` Missing Protocols ir-keytable Ubuntu 20.04 Sean Young
@ 2020-06-09 6:10 ` Peter Hutterer
2020-06-10 12:43 ` Sean Young
0 siblings, 1 reply; 3+ messages in thread
From: Peter Hutterer @ 2020-06-09 6:10 UTC (permalink / raw)
To: Sean Young; +Cc: linux-media, linux-input, wayland-devel, Ralf Schmidt
On Tue, Jun 02, 2020 at 05:08:10PM +0100, Sean Young wrote:
> Hi,
>
> On Wed, May 06, 2020 at 02:35:32PM +0200, Ralf Schmidt wrote:
> > On more thing: because off the removed -d parameter, Remotes like the
> > Technisat TTS35AI are no longer supported, such Type of Remotes are not
> > recognized in /sys/class/rc/.
>
> So I'm now the proud owner of this device.
>
> This device is a usb dongle which is an IR receiver, but self-describes
> as a usb hid keyboard device. It comes with a remote.
>
> As far as I can figure out, there is no way to reprogram it.
>
> So users have been re-mapping scancodes to different keycodes using:
>
> ir-keytable -d /dev/input/eventN -c -k 0x12:KEY_F1
>
> However, ir-keytable was designed load keymaps for rc devices, not hid
> devices. This functionality was intentionally removed, as it was buggy
> in many ways. ir-keytable does not exist for remapping usb hid keyboards.
>
> This has left some users like Ralf in a situation where they can no longer
> change the key mappings for their remote.
>
> ir-keytable is probably not the right way to do this; it has no rules to
> do this from udev, for example. What tooling is there for doing this
> and what is the recommended way to do this?
remapping the keys through the udev builtins maybe?
see /usr/lib/udev/hwdb.d/60-keyboard.hwdb
Cheers,
Peter
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Missing Protocols ir-keytable Ubuntu 20.04
2020-06-09 6:10 ` Peter Hutterer
@ 2020-06-10 12:43 ` Sean Young
0 siblings, 0 replies; 3+ messages in thread
From: Sean Young @ 2020-06-10 12:43 UTC (permalink / raw)
To: Peter Hutterer; +Cc: linux-media, linux-input, wayland-devel, Ralf Schmidt
On Tue, Jun 09, 2020 at 04:10:14PM +1000, Peter Hutterer wrote:
> On Tue, Jun 02, 2020 at 05:08:10PM +0100, Sean Young wrote:
> > Hi,
> >
> > On Wed, May 06, 2020 at 02:35:32PM +0200, Ralf Schmidt wrote:
> > > On more thing: because off the removed -d parameter, Remotes like the
> > > Technisat TTS35AI are no longer supported, such Type of Remotes are not
> > > recognized in /sys/class/rc/.
> >
> > So I'm now the proud owner of this device.
> >
> > This device is a usb dongle which is an IR receiver, but self-describes
> > as a usb hid keyboard device. It comes with a remote.
> >
> > As far as I can figure out, there is no way to reprogram it.
> >
> > So users have been re-mapping scancodes to different keycodes using:
> >
> > ir-keytable -d /dev/input/eventN -c -k 0x12:KEY_F1
> >
> > However, ir-keytable was designed load keymaps for rc devices, not hid
> > devices. This functionality was intentionally removed, as it was buggy
> > in many ways. ir-keytable does not exist for remapping usb hid keyboards.
> >
> > This has left some users like Ralf in a situation where they can no longer
> > change the key mappings for their remote.
> >
> > ir-keytable is probably not the right way to do this; it has no rules to
> > do this from udev, for example. What tooling is there for doing this
> > and what is the recommended way to do this?
>
> remapping the keys through the udev builtins maybe?
> see /usr/lib/udev/hwdb.d/60-keyboard.hwdb
That's a good idea.
Ralf, what keyboard mappings are you using?
Thanks,
Sean
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-06-10 12:43 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <6446b77c-e6de-9d0a-2ed3-691481917b80@gmx.de>
2020-06-02 16:08 ` Missing Protocols ir-keytable Ubuntu 20.04 Sean Young
2020-06-09 6:10 ` Peter Hutterer
2020-06-10 12:43 ` Sean Young
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).