2009/2/18 Anssi Hannula <anssi.hannula@xxxxxxxxx>: >> Problem in fftest is simple: using uninitialized structures. That also >> was causing slow path warning. >> But running ffmvforce after fftest brings device to unconsistent >> state, causing messages "usb 1-1: ctrl urb status -62 received". > > Does this happen also with fixed fftest? Yes. That's the problem. Exactly this sequence: run fftest, play all effects, then run ffmvforce. ffmvforce itself is working well. > Of course hid-pidff should also check the values provided, I'll fix this as > well. I think it'd be also good to look what could cause slow path warning. -- 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
