From: Jiri Slaby <jirislaby@kernel.org>
To: Myrrh Periwinkle <myrrhperiwinkle@qtmlabs.xyz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arthur Taylor <art@ified.ca>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] vt: defkeymap: Map keycodes above 127 to K_HOLE
Date: Tue, 22 Jul 2025 11:07:41 +0200 [thread overview]
Message-ID: <1755f4ab-f0c4-4442-8446-ae7b104b4e89@kernel.org> (raw)
In-Reply-To: <20250702-vt-misc-unicode-fixes-v1-2-c27e143cc2eb@qtmlabs.xyz>
On 02. 07. 25, 16:17, Myrrh Periwinkle wrote:
> The maximum number of keycodes got bumped to 256 a very long time ago,
> but the default keymaps were never adjusted to match. This is causing
> the kernel to interpret keycodes above 127 as U+0000 if the shipped
> generated keymap is used.
>
> Fix this by mapping all keycodes above 127 to K_HOLE so the kernel
> ignores them.
>
> The contents of this patche were generated by rerunning `loadkeys
> --mktable --unicode` and only including the changes to map keycodes
> above 127 to K_HOLE.
OK., makes sense.
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Myrrh Periwinkle <myrrhperiwinkle@qtmlabs.xyz>
> Cc: stable@vger.kernel.org
--
js
suse labs
prev parent reply other threads:[~2025-07-22 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 14:17 [PATCH 0/2] vt: Miscellaneous fixes for keyboard input handling Myrrh Periwinkle
2025-07-02 14:17 ` [PATCH 1/2] vt: keyboard: Don't process Unicode characters in K_OFF mode Myrrh Periwinkle
2025-07-22 9:06 ` Jiri Slaby
2025-07-02 14:17 ` [PATCH 2/2] vt: defkeymap: Map keycodes above 127 to K_HOLE Myrrh Periwinkle
2025-07-22 9:07 ` Jiri Slaby [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=1755f4ab-f0c4-4442-8446-ae7b104b4e89@kernel.org \
--to=jirislaby@kernel.org \
--cc=art@ified.ca \
--cc=gregkh@linuxfoundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=myrrhperiwinkle@qtmlabs.xyz \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®