Fix the generation of KEY_UNKNOWN events #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Reduced verbosity * Using hex literals for events
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have been reported with the driver emitting unknown keycodes (240) and producing some undesired effects on some circumstances under X11. I've took a look at kernel sources and it seems sparse_keymap_report_event generates an unknown keycode on unmapped cases.
I've also reduced a bit verbosity. Perhaps, I should have split into several patches.... :\
Btw, I am currently maintaining slimbook qc71 fork, you clan close pr #12 because it is a bit outdated. I will create another pr later.