diff options
| author | madivad <madivad@dav3.net> | 2019-08-22 10:44:37 +1000 |
|---|---|---|
| committer | Drashna Jaelre <drashna@live.com> | 2019-08-21 17:44:37 -0700 |
| commit | 129e4d1b2f481c09c4f67d24656e6af9cf92b1b6 (patch) | |
| tree | bf9d835f9392cf5ddd456245e102417ae8843999 | |
| parent | fcf87370a835942681592891dcab6b3a0809bb1f (diff) | |
[Docs] Update how_keyboards_work.md (#6528)
* Update how_keyboards_work.md
bridged the gap between scancodes and keycodes, the doc didn't make the distinction and was ambiguous.
* Update docs/how_keyboards_work.md
Co-Authored-By: Drashna Jaelre <drashna@live.com>
* Update docs/how_keyboards_work.md
fix typo
Co-Authored-By: noroadsleft <18669334+noroadsleft@users.noreply.github.com>
| -rw-r--r-- | docs/how_keyboards_work.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/how_keyboards_work.md b/docs/how_keyboards_work.md index 5697a21872..bbd22a2788 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. Thus, by modifying the firmware, you can only modify what scancode is sent over USB for a given key. -## 3. What the Operating System Does +## 3. What the Event Input/Kernel Does + +The *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. + +## 4. What the Operating System Does Once the keycode reaches the operating system, a piece of software has to have it match an actual character thanks to a keyboard layout. For example, if your |