I've been trying to get my Microsoft joystick working and I've been using the VGBA emulator to test it. I put the N800 in host mode and I also put this into the kernal

insmod joydev.ko

But this doesn't seem to do anything as far as VGBA is concerned. The following is a dmesg dump. Does anyone have any ideas about what is wrong or a better way to test it? I'm I understanding it correctly as comming up as /class/input/input4?

Thanks for the help

[ 4210.046875] musb_stage0_irq 645: CONNECT (a_host) devctl 3d
[ 4210.046875] hub 1-0:1.0: state 8 ports 1 chg 0000 evt 0000
[ 4210.046875] usb usb1: usb auto-resume
[ 4210.046875] usb usb1: finish resume
[ 4210.046875] hub 1-0:1.0: hub_resume
[ 4210.070312] hub 1-0:1.0: port 1, status 0301, change 0001, 1.5 Mb/s
[ 4210.226562] hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x301
[ 4210.351562] usb 1-1: new low speed USB device using musb_hdrc and address 2
[ 4210.484375] usb 1-1: skipped 1 descriptor after interface
[ 4210.484375] usb 1-1: default language 0x0409
[ 4210.492187] usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
[ 4210.492187] usb 1-1: Product: Microsoft SideWinder Plug & Play Game Pad
[ 4210.492187] usb 1-1: Manufacturer: Microsoft
[ 4210.492187] usb 1-1: device v045e p0027 is not supported
[ 4210.492187] usb 1-1: uevent
[ 4210.492187] usb 1-1: usb_probe_device
[ 4210.492187] usb 1-1: configuration #1 chosen from 1 choice
[ 4210.492187] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[ 4210.492187] usb 1-1:1.0: uevent
[ 4210.492187] usbhid 1-1:1.0: usb_probe_interface
[ 4210.492187] usbhid 1-1:1.0: usb_probe_interface - got id
[ 4210.492187] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/input/hid-core.c: HID probe called for ifnum 0
[ 4210.500000] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/input/hid-core.c: submitting ctrl urb: Get_Report wValue=0x0100 wIndex=0x0000 wLength=3
[ 4210.500000] input: Microsoft Microsoft SideWinder Plug & Play Game Pad as /class/input/input4
[ 4210.500000] input: USB HID v1.00 Gamepad [Microsoft Microsoft SideWinder Plug & Play Game Pad] on usb-musb_hdrc-1
[ 4210.500000] /home/bifh4/diablo-uarm-prereleased.gcc34qemu/work/kernel-diablo-2.6.21/kernel-source-diablo/drivers/usb/core/inode.c: creating file '002'

While I have only used joysticks under KDE.

However, you output may tell you what the problem is, do you have another type of joystick to test with??



[ 4210.492187] usb 1-1: device v045e p0027 is not supported

No I only have this one joystick. I could also be a problem with VGBA. I will give Diablo a try, it has a few more input configuration options.

Ok, I've tried lots of other apps with no luck. This joystick works on a windows xp box. Does anyone know what other tests or ideas I could try?

How do you know the joystick is even working? Is there even an app like jscalibrator for Maemo? And you will probably have to use something like Joy2Key to make it work with VGBA.

Wii Remotes do work however...

The joystick works on XP machines. I can try the joy2key and see what happens. I'm looking for any ideas because it seems the kernel is working properly, but I'm not completely convinced of that either.

Apparently joy2key and qjoypad aren't available for armel and I don't see any maemo versions. I'm not sure how people are running this on their NIT. Does anyone have info on how I can do this?

ok, so i installed joy2key under easy debian (i can't find any options for maemo). Will a normal maemo program accept input from the easy debian image? How this thing works is a mystery to me.

I don't see how joy2key is going to help you with a joystick the kernel does not support. You either need a driver module for that joystick or support in the kernel..

[ 4210.492187] usb 1-1: Product: Microsoft SideWinder Plug & Play Game Pad
[ 4210.492187] usb 1-1: Manufacturer: Microsoft
[ 4210.492187] usb 1-1: device v045e p0027 is not supported

I saw that that line generated by the kernel, but my usb keyboard generates similar warnings, but it works fine. I think this joystick is pretty standard, so I have been assuming that message is not too important because the kernel continues to configure it as an input device. Maybe I`m wrong, but i dont know the linux system at all. I have figured out that I need to translate it to a keyboard input for it to work in any of these applications.

Some how I doubt the joy2key running in the easy debian environment will translate to a native maemo app, but i don`t know anything about that either. At this point things look hopeless.

Can someone post what a successful dmesg dump looks like for the joystick? All of my usb devices are 'not supported' but work fine except the joystick.

What kernel modules are you using?

When I try to map the /dev/js0 to the input mounted by the usb driver with joy2key -dev it fail with an 'input error'.