![]() The suggested improvement was to simply ask the receiver about the currently connected pads. The driver could then simply wait for the connected signal to create the input devices on demand. The patch force disconnected all pads at driver load, requiring the user to manually re-connect them. However this was actually one of the features that required more work. This issue was also already tackled in the patch series of 31. If you have only one gamepad connected, pads 2-4 will also appear, but always read zero. ![]() Xbox360 Wireless: Ghost ControllersĪnother issue with the Wireless Controller is that it always reports the maximum of 4 connected gamepads – regardless of how many pads are actually connected. At the time of writing they should be merged in Linux 4.2rc1. Actually the code in the steamos kernel seems to predate the mailing list version as it is in much more “hacky” state.Īfter learning about this I split the clean LED related fixes out of the patch series and resubmitted them for review. May 2014 the still unfinished changes from that series appeared in the steamos_kernel (by a collabora employee). However it was part of a patch series which needed some more work – an updated series was promised, but that never happened. Griffais (a Valve Employee) to the Linux mailing list. ![]() The underlying issue is that the driver did not send the correct LED packet to the controller.Ī patch for this issue was submitted on 31. It is just annoying when the LEDs continue blinking even though the controller is already paired. This is the issue that originally got me digging into the driver. Head over here Xbox360 Wireless: Blinking LEDs
0 Comments
Leave a Reply. |