kbd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Hannes Winkler <hannes.winkler@st.ovgu.de>
To: kbd@lists.altlinux.org
Subject: [kbd] add keymap loading for event devices
Date: Wed, 15 Jan 2020 10:14:29 +0100	[thread overview]
Message-ID: <a43a5a6e-1c0e-d738-ed5b-0b72be9d7a99@st.ovgu.de> (raw)

Good morning,

there's currently no way to easily apply a keymap (given as a keymap 
file) to an event device.

What do you think about adding such a feature to loadkeys? That'd also 
enable udev to easily apply the system keymap to hotplugged event devices.

Keymaps are practically the only thing evdevs keep as global state 
(everything else on a per-fd basis), so you don't need to apply the 
keymap every time you open an evdev. It's sufficient to apply the keymap 
to the evdev once, when it's plugged in - loadkeys would be perfect for 
this.

I'd be willing to contribute if you agree to add this feature to loadkeys.

Best regards,
Hannes Winkler




             reply	other threads:[~2020-01-15  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15  9:14 Hannes Winkler [this message]
2020-02-07 10:11 ` [kbd] add keymap loading for event devices Alexey Gladkov

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=a43a5a6e-1c0e-d738-ed5b-0b72be9d7a99@st.ovgu.de \
    --to=hannes.winkler@st.ovgu.de \
    --cc=kbd@lists.altlinux.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 read-only IMAP folder(s) and NNTP newsgroup(s).