I know I'm gonna get made fun of for this post, but I'm desperate.
I got a xbox ddr mat rigged up to a usb cord, and was wanting to use the step mania software for linux with my mat, but I can't find any driver. Anyone know where to find it.

I'm using:
FC3 (Test 3)
KDE 3.3.0-2 Red Hat
Kernel 2.6.8-1.541

Thanks in advance

Well.....
I guess I got my answer...
I haven't tried it yet, but here's a link if anyone else wants it...
livejournal.com
Cheers

O.K...
I can't get it to work...
I don't have a xpad.c in /usr/src/linux-2.6.x/drivers/usb/input/ to replace with the one I downloaded....
Does anyone know if this is a module I have to install?
thanks in advance...

Nevermind...
It has the xpad.c is in the kernel source...
I have to replace the source xpad.c with the new one....

well after I do:
'make modules && make modules_install'
it installs the new xpad.c module,
but when I 'modprob xpad ddr_mode=1'
the module isn't recognizing this option.
the arrows are still acting as axis's when they should act as buttons.
When I use jstest either combination of (up and down) or (left and right) pressed at the same time gives a 0 value....

Has anyone successfully got this module working...
If so how?

THANKS....

O.K ....I finally found out what I believe is the problem...

When I type: dmesg|grep usb
I get this message:
input: X-Box pad on usb-0000:00:10.2-1.1<6>usbcore: registered new driver xpad
drivers/usb/input/xpad.c: X-Box pad driver:v0.0.5

I noticed that this says that the version of the module is 0.0.5
when I look at the source code (xpad.c) it has this towards the begining of the code:

#define DRIVER_VERSION "v0.0.6"

and this towards the end of the code,
so this part of the code should print out the preprocessor directive for DRIVER_VERSION (v0.0.6)

if (result == 0)
info(DRIVER_DESC ":" DRIVER_VERSION);

SO:
this obviously means that an old xpad module is being used instead of the new one.....
Does anyone know how to overwrite this old module with the new one.....

THANKS IN ADVANCE.....

Alright....
I think I know what I'm doing wrong....
It's a very dumb mistake...
I installed the modules for a different kernel version than I usually boot....so that's why the old xpad module is loaded and not the new one....
I haven't tested this yet...but I'm almost a hundred percent sure that's what my problem is....