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 1/2] Input: atkbd - Map FN-key for TongFang barebones
Date: Mon, 17 Mar 2025 12:04:59 +0100 [thread overview]
Message-ID: <4e37c7b2-85bc-459e-b2ea-2e362c16e9aa@redhat.com> (raw)
In-Reply-To: <20250311180643.1107430-1-wse@tuxedocomputers.com>
Hi Werner,
Thank you for your patches / your work on this.
On 11-Mar-25 19:06, Werner Sembach wrote:
> TongFangs firmware sends scancode 0xe0 0x78 upon pressing the FN key.
>
> This patch maps this scancode to avoid a dmesg warning printed every FN-keypress
> and to enable userspace to use they key in other shortcuts than the firmware
> builtin ones.
>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
This laptop specific mapping really belongs in hwdb, 0xe0 0x78
translates to KEYBOARD_KEY_f8 in hwdb and if you look for that in:
/lib/udev/hwdb.d/60-keyboard.hwdb
You already find several entries, e.g. :
evdev:atkbd:dmi:bvn*:bvr*:bd*:svnAcer*:pn*:*
...
KEYBOARD_KEY_f8=fn
And e.g. also for some Clevo models:
KEYBOARD_KEY_f8=f21 # Touchpad Toggle
and:
# HP Elite x2 1013 G3
evdev:atkbd:dmi:bvn*:bvr*:svnHP*:pnHPElitex21013G3:*
KEYBOARD_KEY_f8=unknown # rfkill is also reported by HP Wireless hotkeys
these first couple of hits show that 0xf8 is not
universally mapped to Fn, so putting this mapping in the kernel's
default key table is wrong IMHO.
Regards,
Hans
> ---
> drivers/input/keyboard/atkbd.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> index adf0f311996c9..3598a21d9d014 100644
> --- a/drivers/input/keyboard/atkbd.c
> +++ b/drivers/input/keyboard/atkbd.c
> @@ -98,7 +98,7 @@ static const unsigned short atkbd_set2_keycode[ATKBD_KEYMAP_SIZE] = {
> 173,114, 0,113, 0, 0, 0,126,128, 0, 0,140, 0, 0, 0,127,
> 159, 0,115, 0,164, 0, 0,116,158, 0,172,166, 0, 0, 0,142,
> 157, 0, 0, 0, 0, 0, 0, 0,155, 0, 98, 0, 0,163, 0, 0,
> - 226, 0, 0, 0, 0, 0, 0, 0, 0,255, 96, 0, 0, 0,143, 0,
> + 226, 0, 0,464, 0, 0, 0, 0, 0,255, 96, 0, 0, 0,143, 0,
> 0, 0, 0, 0, 0, 0, 0, 0, 0,107, 0,105,102, 0, 0,112,
> 110,111,108,112,106,103, 0,119, 0,118,109, 0, 99,104,119, 0,
>
next prev parent reply other threads:[~2025-03-17 11:05 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
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 [this message]
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=4e37c7b2-85bc-459e-b2ea-2e362c16e9aa@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 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).