New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for HyperX Clutch gamepad #250
base: master
Are you sure you want to change the base?
Conversation
Added support for HyperX Clutch |
Would HyperX Clutch Gladiate: |
Would we be able to add both: Vendor should be Do we also need to add support for the controller on the device list? |
Isn't it a good practice to add it exact with usb device? What if it'll include other non-gamepad devices? |
I had couple question about the device identifiers.
|
I would agree that it's good to add exact device information. However, would that be the purpose of Also curious whether any other vendors has ran into issues by adding only their vendor IDs to
^ This was for |
For the
That's correct if the vendor makes both Xbox 360 and Xbox One compatible devices. I suspect HyperX Clutch is actually only Xbox 360 compatible since it doesn't advertise Xbox One compatibility. We should confirm it's Xbox One compatible before adding
Xbox 360 and Xbox One controllers have different capabilities and use different protocols. If Note that if
Zero is
Yes, we should add an entry to
Yes, the "Hewlett-Packard" string is old and should be "HP, Inc" on newer installs. The string was captured on a ChromeOS device with an outdated version of usb.ids. It looks like the database was updated in 2018. |
When does a new commit of the xpad.c file get pushed out to the public? |
Sorry, yes you're right. This overlooked what the for-loop starting in
I think I can see were the confusion lies. The pull request is currently only for HyperX Clutch but we like to also add support for HyperX Clutch Gladiate which does support Xbox One. To summarize, we should have the following then?
I think @HP-HX-maxster is referring to the zero for the button mapping in |
Oops, yes, it seems HyperX Clutch Gladiate is Xbox One compatible. I would expect this (assuming HyperX Clutch is also Xbox One compatible): xpad_table:
xpad_device:
Or this (if HyperX Clutch is Xbox 360 compatible): xpad_table:
xpad_device:
I think
The 0 for
I'm not sure, it seems this repo and the kernel's xpad have gotten out of sync. Maybe @paroj can clarify. I think it is quicker to make the changes to the Linux kernel's xpad since that's the version most distros will use. When I added Amazon Luna controller, I added it to the kernel's xpad and @paroj merged it into this repo, but that might not be the preferred way. |
After internal discussion, we will remove HyperX Clutch so that it just detects as a generic gamepad. So we would like the following to be added. xpad_table: { XPAD_XBOX360_VENDOR(0x03f0) }, /* HP/HyperX Xbox 360 controllers / xpad_device: { 0x03f0, 0x0495, "HyperX Clutch Gladiate", 0, XTYPE_XBOXONE }, Does Android and ChromeOS use the Linux kernel's xpad file? If it is quicker, then we can open our own pull request for the Linux kernel. It will be beneficial for us to learn to do so for future controllers as well. Let us know your thoughts @paroj. |
please create an according PR here
yes. SteamOS also.
You can skip this repo altogether and contribute to the kernel directly. However, you will need to use this process: which neither includes github nor a pull request. |
No description provided.