From: Alexey Gladkov <legion@kernel.org>
To: kbd@lists.linux.dev
Subject: [PATCH 0/4] Allow to convert xkb keymap to kernel keymap
Date: Thu, 4 Jan 2024 18:15:14 +0000 [thread overview]
Message-ID: <cover.1704392039.git.legion@kernel.org> (raw)
This patchset adds the ability to use keymaps from libxkbcommon. It gives the
loadkeys utility additional options for passing xkb-specific parameters.
The idea is to make it possible to unify the keymap configuration between linux
console and xorg/wayland and unification of the keymaps configuration method.
Unfortunately, we cannot use xkb keymap one to one. The linux kernel has a
number of limitations that allow the use of xkb keymaps.
Many thanks to Anton Zinoviev who helped me figure out how console-setup solved
the problems of converting xkb to linux keymaps.
Alexey Gladkov (4):
Add keymap generation from the xkb database
xkbsupport: Create a list of used codes
xkbsupport: Extract translation table
xkbsupport: Add xkb compose
configure.ac | 10 +
data/xkbtrans/names | 154 ++++++++++
src/Makefile.am | 6 +
src/loadkeys.c | 80 ++++-
src/loadkeys.h | 13 +
src/xkbsupport.c | 693 ++++++++++++++++++++++++++++++++++++++++++++
src/xkbsupport.h | 18 ++
7 files changed, 965 insertions(+), 9 deletions(-)
create mode 100644 data/xkbtrans/names
create mode 100644 src/loadkeys.h
create mode 100644 src/xkbsupport.c
create mode 100644 src/xkbsupport.h
--
2.43.0
next reply other threads:[~2024-01-04 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 18:15 Alexey Gladkov [this message]
2024-01-04 18:15 ` [PATCH 1/4] Add keymap generation from the xkb database Alexey Gladkov
2024-01-04 18:15 ` [PATCH 2/4] xkbsupport: Create a list of used codes Alexey Gladkov
2024-01-04 18:15 ` [PATCH 3/4] xkbsupport: Extract translation table Alexey Gladkov
2024-01-04 18:15 ` [PATCH 4/4] xkbsupport: Add xkb compose 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=cover.1704392039.git.legion@kernel.org \
--to=legion@kernel.org \
--cc=kbd@lists.linux.dev \
/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