Commit 7f9f4e3
committed
Include and maintain input event codes
The previous dynamic build-time mechanism for generating ev.py was
just a recipe for troubles. The recent change in the filepath of the
event code header file is just one example.
Dynamic update worked pretty well, but because Linux is known for its
uapi stability, we can safely rely on them to maintain event codes in
backwards-compatible manner. After all, Python-uinput is just a
wrapper for uinput.
src/ev.py should be updated whenever new event codes are introduced in
mainline kernels. Yes, it is a bit more work, but it's a lot simpler
code-wise and the update process is trivial to (semi-)automate.1 parent 1a60d6d commit 7f9f4e3
2 files changed
Lines changed: 595 additions & 28 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
2 | | - | |
3 | | - | |
4 | | - | |
5 | | - | |
6 | 2 | | |
7 | | - | |
8 | 3 | | |
9 | 4 | | |
10 | | - | |
11 | | - | |
12 | | - | |
13 | | - | |
14 | | - | |
15 | | - | |
16 | | - | |
17 | | - | |
18 | | - | |
19 | | - | |
20 | | - | |
21 | | - | |
22 | | - | |
23 | | - | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
32 | 5 | | |
33 | 6 | | |
34 | 7 | | |
| |||
62 | 35 | | |
63 | 36 | | |
64 | 37 | | |
65 | | - | |
66 | 38 | | |
67 | 39 | | |
68 | 40 | | |
0 commit comments