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.
Adds a simple gamepad HID device to the devices that share a common endpoint: mouse, keyboard, consumer controls, and now gamepad.
The gamepad shows up to varying degrees in various operating systems:
/dev/input/js*
device and a/dev/input/event*
device. Events can be seen viaevtest
andjstest
. Firefox and Chrome do not see the gamepad via https://html5gamepad.com, but that appears to be due to limited gamepad support/compatibility between the browsers and LinuxFirefox and Chrome can see the gamepad via http://html5gamepad.com. You may need to send some events before it shows up.
This PR also includes latent support for a stylus-based digitizer as well, but it conflicts with other devices, so it's turned off until we have dynamic USB HID devices. I had hoped to add a little dynamic
boot.py
support to allow turning the HID devices on and off before USB comes up, but this requires dynamic construction of both the report descriptors and the HID descriptor, so deferred for now.Needs adafruit/Adafruit_CircuitPython_HID#19 to have a Python library for the gamepad support.