Generic USB controler - ID 0079:0006

[markdr]

I was really hoping my no-name USB joystick controller board would just work but apart from some general kernel messages, button/joystick events are not being triggered.

Via serial port console on plugging in we get:

Code: Select all

The file js0 was created.
[   14.381989] dragonrise 0003:0079:0006.0001: no output reports found
Close all devices.
Open up to 30 input devices.
[   14.389384] dragonrise 0003:0079:0006.0001: force feedback init failed
The file event1 was created.
The file js0 was deleted.
The file event1 was deleted.
Close all devices.
Open up to 30 input devices.

Via dmesg we get:

Code: Select all

[   14.166407] usb 1-1: new low-speed USB device number 2 using dwc2
[   14.366584] usb 1-1: New USB device found, idVendor=0079, idProduct=0006, bcdDevice= 1.01
[   14.366596] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   14.366603] usb 1-1: Product: Generic USB Joystick
[   14.366610] usb 1-1: Manufacturer: NoName
[   14.380112] HID usage: 0x00010005, original interval: 10
[   14.380121] JS: endpoint->bInterval=10, interval=10
[   14.380126] HID usage: 0x00010005, applied interval: 10
[   14.380350] input: NoName Generic USB Joystick as /devices/platform/soc/ffb40000.usb/usb1/1-1/1-1:1.0/0003:0079:0006.0001/input/input1
[   14.381977] dragonrise 0003:0079:0006.0001: input,hidraw0: USB HID v1.01 Gamepad [NoName Generic USB Joystick] on usb-ffb40000.usb-1/input0
[   14.381989] dragonrise 0003:0079:0006.0001: no output reports found
[   14.389384] dragonrise 0003:0079:0006.0001: force feedback init failed

It looks to be known to the kernel as a USB_VENDOR_ID_DRAGONRISE, on another linux box it comes up as:

Code: Select all

lsusb -d 0079:0006
Bus 005 Device 004: ID 0079:0006 DragonRise Inc. PC TWIN SHOCK Gamepad

Is it just missing some additional driver support in the MiSTer kernel?
Anything else I can change/try to get this board working?

[Newsdee]

That "no output reports found" suggest it's using non-standard USB messages, so it may need a driver.
You can try connecting a different USB controller to compare the messages you get with a recognized one.

[paulbnl]

It requires a minor kernel patch: https://github.com/torvalds/linux/commi ... b8ff640de5

[markdr]

It requires a minor kernel patch: https://github.com/torvalds/linux/commi ... b8ff640de5

Thanks for the pointer, I did see that and tried it using the docker image to rebuild the kernel after applying the change but it didn't seem to make any difference (could have been user error). I did also find a reference to a linux boot string for a USB quirk to apply for this device but couldn't find how that could be applied in the MiSTer boot sequence.

Given variations of these devices are reasonably easy to find, might try picking up a different one to see if I can get past this issue.