/device/gamepad use the joydev interface. We should move on and use evdev gamepad.
Why:
1. Better compatibility. Gamepad mapping will be better.
2. Android is using evdev. Evdev gamepad support ARC++ better.
3. Event driven implementation (instead of polling) will have a better latency.
To move on, we need to:
1. Add chrome flag to turn on exo ozone gamepad
2. Fix bugs of ozone gamepad.
currently, the gamepad event functions are not marked as const
3. Cook a gaming_seat using ozone gamepad.
I am checking in the ozone gaming seat. It is currently protected by USE_OZONE_GAMEPAD. We should remove this make the gaming seat default when ozone is for every chrome os and ozone gamepad is stable.
Comment 1 by kochi@chromium.org
, May 2 2017Labels: -Type-Bug Type-Feature