basic usb HID controller driver based on the usb keyboard driver#115
Draft
DacoTaco wants to merge 1 commit intodevkitPro:masterfrom
Draft
basic usb HID controller driver based on the usb keyboard driver#115DacoTaco wants to merge 1 commit intodevkitPro:masterfrom
DacoTaco wants to merge 1 commit intodevkitPro:masterfrom
Conversation
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
1 participant
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 a draft PR so everyone can review, pitch ideas & opinions about something i (to me feelings?) threw together.
I would love to hear the opinions so i can change or investigate something , so we can make this better!
the driver is based on the usb keyboard driver so it works with an event handler that reports what is pressed/unpressed and what the value is.
Personally i would like it to work like the WPAD/PAD functions but with every controller having different interfaces (amount of buttons, axis, hat's) i have no idea if that would even work without a shit ton of defines & high memory usage?
the event is something like 'button number 2 was pressed' , 'Axis Moved, new value = X' or 'button 15 is released'
the consuming homebrew would only need to init the driver, open the controller, do a scan to poll and interpret the events in their handler.
as an example : https://0bin.net/paste/Tf1F1hNO#gVoUmD0k6ojeVv2xnwvgc-347HwRP6rDOz7ifrClp1Y
this does not support dualshock controller or the Wii GC adapter , currently unknown if those could work with this or what would need to change to support them