From: Hans de Goede <hdegoede@redhat.com>
To: Werner Sembach <wse@tuxedocomputers.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] Input: atkbd - Correctly map F13 - F24
Date: Mon, 17 Mar 2025 13:06:41 +0100 [thread overview]
Message-ID: <45fff318-7925-4328-9dca-999c00e271d2@redhat.com> (raw)
In-Reply-To: <83ea44f6-c0ad-4cb0-a16e-dd4fa17b63c7@tuxedocomputers.com>
Hi,
On 11-Mar-25 19:10, Werner Sembach wrote:
> Hi Hans, Hi Dimitry,
>
> resending this too on the v2 to not cause confusion:
>
> Regarding remapping KEY_ZENKAKUHANKAKU to KEY_TOUCHPAD_TOGGLE:
>
> Am 11.03.25 um 19:06 schrieb Werner Sembach:
>> Currently only F23 is correctly mapped for PS/2 keyboards.
>>
>> Following to this table:
>> https://download.microsoft.com/download/1/6/1/161ba512-40e2-4cc9-843a-923143f3456c/translate.pdf
>>
>> - F24 and Zenkaku/Hankaku share the same scancode, but since in real world
>> Zenkaku/Hankaku keys seem to just use the tilde scancode, this patch binds the
>> scancode to F24. Note that on userspace side the KEY_ZENKAKUHANKAKU keycode is
>> currently not bound in xkeyboard-config, so it is (mostly*) unused anyway.
>
> I think what the firmware vendor actually wanted to do was to send ctrl+super+f24 upon touchpad toggle. This would somewhat fall in line with, for example, the copilot key being implemented as shift+super+f23.
I agree that that seems to be the intent.
> Following this, my suggestion is to do this remapping and handle the rest in xkeyboard-config
xkeyboard config already contains mappings for F13 - F18 and F20-F23 in
/usr/share/X11/xkb/symbols/inet
So all that needs to happen there is map FK19 -> F19 and FK24 -> F24.
And then teach KDE + GNOME that ctrl+super+f24 means touchpad-toggle.
We could maybe get away with also dropping the weird mappings for FK13 - FK18
and map those straight to F13 - F18, but we need the special mappings
for F20 - F23 to stay in place to not break stuff.
Regards,
Hans
next prev parent reply other threads:[~2025-03-17 12:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 18:06 [PATCH v2 1/2] Input: atkbd - Map FN-key for TongFang barebones Werner Sembach
2025-03-11 18:06 ` [PATCH v2 2/2] Input: atkbd - Correctly map F13 - F24 Werner Sembach
2025-03-11 18:10 ` Werner Sembach
2025-03-17 12:06 ` Hans de Goede [this message]
2025-03-17 16:47 ` Werner Sembach
2025-03-17 22:22 ` Hans de Goede
2025-03-18 10:20 ` Werner Sembach
2025-03-25 13:18 ` Werner Sembach
2025-03-17 11:58 ` Hans de Goede
2025-03-17 17:00 ` Werner Sembach
2025-03-17 22:23 ` Hans de Goede
2025-03-18 10:21 ` Werner Sembach
2025-05-15 12:26 ` Werner Sembach
2025-07-21 20:36 ` Werner Sembach
2025-07-22 7:04 ` Hans de Goede
2025-07-22 11:53 ` Werner Sembach
2025-03-11 18:07 ` [PATCH v2 1/2] Input: atkbd - Map FN-key for TongFang barebones Werner Sembach
2025-03-17 11:04 ` Hans de Goede
2025-03-17 15:50 ` Werner Sembach
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=45fff318-7925-4328-9dca-999c00e271d2@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wse@tuxedocomputers.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.