keyboard fix#345
Merged
Merged
Conversation
added 2 commits
June 18, 2026 14:53
awesomebrick
marked this pull request as draft
June 20, 2026 07:04
Contributor
Author
|
ok there's a not-necessary but related and probably important change in libavr32 that didn't get added into my previous commit and PR. marking this as draft until that one gets merged |
Contributor
Author
|
all fixed. keyboards work now! ready for pr |
awesomebrick
marked this pull request as ready for review
June 24, 2026 16:47
This file contains hidden or 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
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.
updated the submodule reference to incorporate kbdfix.
there's also a potential race condition in the hid callback timer that was fixed, found in the process of finding the other stuff.
tested with my previously non-working keyboards (ASUS ROG Falchion and MelGeek MOJO68)