feat(onexplayer): add ONEXPLAYER 3 support - #660
Conversation
|
Does this device have any strange serial devices in /dev?
Thanks |
| - name: Home | ||
| source_events: | ||
| - gamepad: | ||
| button: Keyboard |
There was a problem hiding this comment.
Is this real? I would expect it to be a keyboard key
There was a problem hiding this comment.
It's exposed through OXP HID as ID 0x24
There was a problem hiding this comment.
What is the real wold event in evtest?
There was a problem hiding this comment.
The physical device comes through HIDRAW but on the virtual controller exposed from OXP HID it shows up as BTN_MODE + BTN_NORTH
| button: Keyboard | ||
| target_event: | ||
| gamepad: | ||
| button: QuickAccess |
There was a problem hiding this comment.
I figured since it has a separate working "Guide"/Xbox button it made sense to make this QuickAccess. Should I change it to Keyboard?
There was a problem hiding this comment.
Well you already have a Quick Access mapped to Options, so it's a bit redundant.
There was a problem hiding this comment.
I see what you mean yeah I was just struggling to come up with what to do for it. Looks like if unconfigured it just shows up as "show keyboard" so that seems sane enough.
|
No Serial devices, just regular TTYs.
Sorry for the formatting here let me know if you prefer a pastebin or something. Also some extra devices will show up because I have the OneX 3 plugged in through a docking station at the moment
Actual device "/sys/class/leds/go:rgb:joystick_rings"
|
fe7f8de to
4b32dad
Compare
Add the DMI autostart match, composite device profile, and extra-button capability mappings for the ONEXPLAYER 3. The profile and mappings were generated with OpenAI Codex assistance, then reviewed and verified interactively on ONEXPLAYER 3 hardware using evtest and InputPlumber. Validation included the full test suite, clippy, YAML parsing, and the autostart configuration test. Co-developed-by: OpenAI Codex
4b32dad to
7b6aeec
Compare
Add the DMI autostart match, composite device profile, and extra-button capability mappings for the ONEXPLAYER 3.
Hardware tested
045e:028e1a86:fe00Known limitation
The left rear paddle does not emit an input event while the device is in its normal XInput mode with the current
hid-oxpbehavior. The right rear paddle works. This appears to be outside the InputPlumber profile and is not worked around in this change.AI assistance disclosure
The profile and mappings were generated with OpenAI Codex assistance, then reviewed and verified interactively on ONEXPLAYER 3 hardware using evtest and InputPlumber. Validation included the full test suite, clippy, YAML parsing, and the autostart configuration test.
Co-developed-by: OpenAI Codex