feat: port the Embassy USB HID keyboard example #25
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
This ports the Embassy USB HID keyboard example [1] to RIOT-rs. It highlights some remaining challenges, in particular: - How should we expose peripherals to tasks, after some of them have been moved out of the Peripherals struct during the initialization phase? - How can we allow configuring these drivers from within tasks? - Can we make sure at compile time that drivers that can be used only once are actually taken by no more than one task? [1] https://github.com/embassy-rs/embassy/blob/14f41a71b6ea9dedb4ee5b9c741fe10575772c7d/examples/nrf52840/src/bin/usb_hid_keyboard.rs
|
This got merged with #87. |
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 is experimental, for documentation only; should not be merged.
This ports the Embassy USB HID keyboard example to RIOT-rs.
It highlights some remaining challenges, in particular:
Peripheralsstruct during the initialization phase?