[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20250107034554.25843-1-mpearson-lenovo@squebb.ca>
Date: Mon, 6 Jan 2025 21:45:40 -0600
From: Mark Pearson <mpearson-lenovo@...ebb.ca>
To: mpearson-lenovo@...ebb.ca
Cc: dmitry.torokhov@...il.com,
hdegoede@...hat.com,
peter.hutterer@...hat.com,
linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH v2] Input: atkbd: Fix so copilot key generates F23 keycode
The copilot key on doesn't work as scancode 0x6e, which it generates is
not mapped.
This change lets scancode 0x6e generate keycode 193 (F23 key) which is
the expected value for copilot.
MS documentation for the scan code:
https://learn.microsoft.com/en-us/windows/win32/inputdev/about-keyboard-input#scan-codes
Confirmed on Lenovo, HP and Dell machines by Canonical
Tested on Lenovo T14s G6 AMD.
Signed-off-by: Mark Pearson <mpearson-lenovo@...ebb.ca>
---
Changes in v2: Updated commit description with MS link and testing
details
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 5855d4fc6e6a..f7b08b359c9c 100644
--- a/drivers/input/keyboard/atkbd.c
+++ b/drivers/input/keyboard/atkbd.c
@@ -89,7 +89,7 @@ static const unsigned short atkbd_set2_keycode[ATKBD_KEYMAP_SIZE] = {
0, 46, 45, 32, 18, 5, 4, 95, 0, 57, 47, 33, 20, 19, 6,183,
0, 49, 48, 35, 34, 21, 7,184, 0, 0, 50, 36, 22, 8, 9,185,
0, 51, 37, 23, 24, 11, 10, 0, 0, 52, 53, 38, 39, 25, 12, 0,
- 0, 89, 40, 0, 26, 13, 0, 0, 58, 54, 28, 27, 0, 43, 0, 85,
+ 0, 89, 40, 0, 26, 13, 0,193, 58, 54, 28, 27, 0, 43, 0, 85,
0, 86, 91, 90, 92, 0, 14, 94, 0, 79,124, 75, 71,121, 0, 0,
82, 83, 80, 76, 77, 72, 1, 69, 87, 78, 81, 74, 55, 73, 70, 99,
--
2.47.1
Powered by blists - more mailing lists