linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: linux-media@vger.kernel.org, linux-input@vger.kernel.org,
	wayland-devel@lists.freedesktop.org, Ralf Schmidt <rds2@gmx.de>
Subject: Re: Missing Protocols ir-keytable Ubuntu 20.04
Date: Wed, 10 Jun 2020 13:43:06 +0100	[thread overview]
Message-ID: <20200610124306.GA14497@gofer.mess.org> (raw)
In-Reply-To: <20200609061014.GA40603@jelly>

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

      reply	other threads:[~2020-06-10 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 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=20200610124306.GA14497@gofer.mess.org \
    --to=sean@mess.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=peter.hutterer@who-t.net \
    --cc=rds2@gmx.de \
    --cc=wayland-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).