Bug 726922

Summary: XBox 360 Controller isn't recognized by xpad kernel module
Product: [Fedora] Fedora Reporter: Tristian Celestin <tristian.celestin>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, jwboyer, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-06 16:49:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Patch to add PDP controller ids none

Description Tristian Celestin 2011-07-30 23:17:05 UTC
Created attachment 515991 [details]
Patch to add PDP controller ids

Description of problem:

I have an xbox 360 controller manufactured by PDP. It's described here:
http://www.pdp.com/p-835-afterglow-ax1-for-xbox-360.aspx

When I plug it into a USB port, the controller is never recognized; the player indicator LEDs just blink.

This is because the product and vendor ids for the controller are not recognized by the xpad kernel module.

Steps to Reproduce:
1. Plug in the controller.
2. Watch as the player LEDs blink. 

Expected results:
The player LED should stop blinking and indicate that the controller is player 1, if the controller is the only 360 controller plugged in.
  
Actual results:
They continue to blink.


Attached is a patch (relative to xpad.c as it is in kernel 2.6.38) that adds the extra product and vendor ids for the controller.

Comment 1 Josh Boyer 2011-08-01 11:09:04 UTC
This patch should really go upstream.  Have you sent it to the linux-input list?

Comment 2 Josh Boyer 2012-06-06 16:49:35 UTC
This really needs to be submitted to the upstream kernel.  We'll pick it up automatically from there.