aboutsummaryrefslogtreecommitdiff
path: root/docs/how_keyboards_work.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/how_keyboards_work.md')
-rw-r--r--docs/how_keyboards_work.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/how_keyboards_work.md b/docs/how_keyboards_work.md
index 5697a2187..bbd22a278 100644
--- a/docs/how_keyboards_work.md
+++ b/docs/how_keyboards_work.md
@@ -33,7 +33,11 @@ The firmware does not send actual letters or characters, but only scancodes.
33Thus, by modifying the firmware, you can only modify what scancode is sent over 33Thus, by modifying the firmware, you can only modify what scancode is sent over
34USB for a given key. 34USB for a given key.
35 35
36## 3. What the Operating System Does 36## 3. What the Event Input/Kernel Does
37
38The *scancode* is mapped to a *keycode* dependent on the keyboard [60-keyboard.hwdb at Master](https://github.com/systemd/systemd/blob/master/hwdb/60-keyboard.hwdb). Without this mapping, the operating system will not receive a valid keycode and will be unable to do anything useful with that key press.
39
40## 4. What the Operating System Does
37 41
38Once the keycode reaches the operating system, a piece of software has to have 42Once the keycode reaches the operating system, a piece of software has to have
39it match an actual character thanks to a keyboard layout. For example, if your 43it match an actual character thanks to a keyboard layout. For example, if your