Add support for Elecrow ThinkNode M9#2942
Merged
Merged
Conversation
Member
|
You don't need that 'libqst.a' static lib. Apparently, that just has some accelerometer driver in it. |
173614c to
87bf371
Compare
Member
Author
Removed, and force pushed with commits squashed. |
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.
This PR adds initial support for the Elecrow ThinkNode M9.
Currently, the default companion UI isn't too interesting for this device, and the keyboard has not been wired up, so navigation is not possible.
For now, it's being added in a disabled state, where firmware won't be auto built by our release flow on GitHub Actions. However, users can build the firmware themselves if they want it.
The intention is to provide the base structure that's successfully compiling and running, to allow users to tinker and pave the way for a new companion UI.
I have tested the following firmwares:
Note that this device uses a keyboard that sends key events over I2C. You would need to poll I2C each loop, and handle the key events that have been provided. For now, we don't have any input source framework in place for injecting key events from custom keyboards into the existing UITasks.
It would be best to avoid having to setup drivers for all keyboards inside the UITask, and instead have a way to register input sources on the Board object, and allow UITasks to register key event callbacks via the provided Board instance.
This will be left for the future :)