Xbox360 gamepad support

Bug #94560 reported by Mårten Woxberg
2
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
Low
Ben Collins

Bug Description

Binary package hint: linux-source-2.6.20

I've tried to follow the guides that exists but nothing works.

Why isn't the xpad.c and xpad.h from xbox-linux included in the main tree?
The xpad module seems to be included but the functionality isn't there.

Is there some legal problems with it or?

I think Feisty+1 should have gamepad support in both MythTV and gnome-games as well as a replacement for the mouse.

Revision history for this message
Ben Collins (ben-collins) wrote :

The module is there and up-to-date. If it isn't working, please attach dmesg output to this bug report and re-open it (as Unconfirmed/Undecided).

Changed in linux-source-2.6.20:
status: Unconfirmed → Rejected
Revision history for this message
Mårten Woxberg (maxmc) wrote :

This is with the xpad module loaded:
max@lillemor ~>sudo tail -fn0 /var/log/messages
Mar 22 17:11:53 lillemor kernel: [ 848.940000] usb 1-5: new full speed USB device using ohci_hcd and address 5
Mar 22 17:11:53 lillemor kernel: [ 849.164000] usb 1-5: configuration #1 chosen from 1 choice
Mar 22 17:11:56 lillemor kernel: [ 851.980000] usb 1-5: USB disconnect, address 5

This looks interesting to me:
[ 812.136000] usbcore: registered new interface driver xpad
[ 812.136000] drivers/usb/input/xpad.c: X-Box pad driver:v0.0.6

Shouldn't the driver be 0.1.6?
That's the most recent one at:
http://xbox.cvs.sourceforge.net/xbox-linux/kernel-2.6/drivers/usb/input/xpad.c?view=log

It's labeled 1.32 in their CVS.
According to their version history 0.0.6 was released 2002-08-05 with the comment: "added analog button support"

So whats wrong?

Revision history for this message
Ben Collins (ben-collins) wrote :

Seems the problem is that these folks haven't been merging their work with upstream kernel like good developers :)

You should probably poke them about this. It's hard for us as distro kernel maintainers to track down and sync the latest version of everything. Development should happen in the kernel, not on some external CVS.

I'm going to include it this time, but consider that unless they sync with upstream kernel, it will likely get reverted in feisty+1 because it is low priority for us.

Changed in linux-source-2.6.20:
assignee: nobody → ben-collins
importance: Undecided → Low
status: Rejected → In Progress
Revision history for this message
Ben Collins (ben-collins) wrote :

Not to mention that they don't even seem to be compiling this driver for latest kernels (like our 2.6.20). I had to make some very trivial changes to get it working.

Please talk to the project about syncing this to upstream kernel.

Changed in linux-source-2.6.20:
status: In Progress → Fix Committed
Revision history for this message
Mårten Woxberg (maxmc) wrote :

I've sent a mail to their developer mailinglist that is awaitng approval by moderators.

I've read their latest thread on the list (2007-02-27) and they seem to be heading towards syncing with the main kernel tree so hopefully this is the last time you'll need to poke in it yourself.

I'd appreciate if you could post the xpad module for the current kernel so i can try it out to see if it works or if we should wait for them to sync.

Changed in linux-source-2.6.20:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.