diff options
| author | Johannes Stoelp <johannes.stoelp@gmail.com> | 2023-08-18 14:23:23 +0200 |
|---|---|---|
| committer | Johannes Stoelp <johannes.stoelp@gmail.com> | 2023-08-22 23:37:33 +0200 |
| commit | e7b2cecc90ef105091de249698d8c61e50a8764b (patch) | |
| tree | 3b599600944f4afccf4ce146dafa701f0c0b48b0 | |
| parent | fabb7a355488efaa0eeee6a134e9fad57c1d0b74 (diff) | |
| download | notes-e7b2cecc90ef105091de249698d8c61e50a8764b.tar.gz notes-e7b2cecc90ef105091de249698d8c61e50a8764b.zip | |
input: fix links and typos
| -rw-r--r-- | src/linux/input.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/src/linux/input.md b/src/linux/input.md index 8a9771e..a01d367 100644 --- a/src/linux/input.md +++ b/src/linux/input.md @@ -23,7 +23,7 @@ sudo cat /dev/input/mice | od -tx1 -w3 -v These device files are created by the [evdev] driver. -- `/dev/input/eventX` represents the generic input event interface a *SINGLE* input deivece. +- `/dev/input/eventX` represents the generic input event interface a *SINGLE* input device. Input events are encoded as given by the `input_event` struct below. Reading from the `eventX` device file will always yield whole number of input events. @@ -41,7 +41,7 @@ On most 64bit machines the raw data stream can be inspected as follows. sudo cat /dev/input/event4 | od -tx1 -w24 -v ``` -## Identifyin device files. +## Identifying device files. To find out which device file is assigned to which input device the following file `/proc/bus/input/devices` in the proc filesystem can be consulted. @@ -64,5 +64,5 @@ Once compiled, the example should be run as `sudo ./event /dev/input/eventX`. ``` [linux-input]: https://www.kernel.org/doc/Documentation/input/input.txt -[mousedev]: TODO /home/johannst/dev/linux/drivers/input/mousedev.c -[evdev]: TODO /home/johannst/dev/linux/drivers/input/evdev.c +[mousedev]: https://elixir.bootlin.com/linux/latest/source/drivers/input/mousedev.c#L842 +[evdev]: https://elixir.bootlin.com/linux/latest/source/drivers/input/evdev.c#L1337 |