feat(TTY): Add Serial TTY interface and OXP F1 Series Serial Driver #441
Conversation
pastaq
force-pushed
the
pastaq/oxp_f1_conf
branch
from
1f31949 to
084f535
Compare
pastaq
changed the title
pastaq
force-pushed
the
pastaq/oxp_f1_conf
branch
3 times, most recently
from
cdef917 to
e7202c0
Compare
- Adds new source device subsystem, tty. - Adds driver for OneXPlayer OneXFly F1 and F1 Pro Serial TTY device.
- Unify F1 and F1 Pro into single config. - Add missing F1 models. - Add serial tty HID device to config. - Adjust capability map to add right paddle support if the tty is not used.
pastaq
force-pushed
the
pastaq/oxp_f1_conf
branch
from
e7202c0 to
eb0a9e9
Compare
pastaq
changed the title
|
Some explanation of why this is needed: The F1 series has two extra shoulder buttons (M1/M2). When the MCU is in xinput mode all events flow to the evdev. M1 and M2 are programmable, but only with the limited xinput event set. M2 is set to guide by default and no other button uses guide, but there is no "free" event for M1, leaving it unusable. There is also a debug TTY mode. Switching to it moves all input to the serial interface (evdev receives no data) and M1 and M2 can be seen directly, along with the mapping of each button. As a side effect the joystick input is very slow compared to the evdev input. My testing shows this produces joystick events at somewhere between 15-20hz. Gameplay seems okay in this mode for platformers, racing, and FPS games, but I'm waiting for internal testing from OXP themselves if this is "acceptable". If not I'll drop the option in the config and reuse the serial port driver to configure M1 and M2, leaving M1 as a duplicate of some other xinput button (A probably). |
Uh oh!
There was an error while loading. Please reload this page.