On Mon, 14 Dec 2009, Johannes Ebke wrote: > I own a Saitek Cyborg Evo Force which works fine with the HID driver on > Linux. However, i could not find a force feedback driver for it, and > just adding the USB id and spec to the IForce driver does not work (and > crashes the kernel) Hi Johannes, thanks for your e-mail. I hope you don't mind adding a few relevant CCs. First, kernel crashing means that we are probably lacking some error handling in the iforce driver, which we should add if possible. Could you please post the oops message preceeding the crash? > After that, I have reverse-engineered the protocol using usb snoops from > a kvm virtual machine with XP on it. Using libusb, I have verified that > I understand the protocol, and it actually looks quite similar to the > iforce protocol (no wonder, it just implements the DirectInput interface > in hardware) Good job, thanks a lot for doing this. > My question: Would it make sense to adapt the iforce modules to include > this slightly modified protocol (other initialization strings, other > magic bytes) or would it be better to copy & modify? It really depends how much different the protocols really are. iforce driver currently doesn't support any per-device flags which would allow for introducing slight differences between individual models. Maybe it would help if you could just summarize the most important differences to iforce protocol, so that we could see what aproach would be the best. Thanks, -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
