Re: hid-pidff bug: fails to find all required reports of saitek gamepad

[Anssi Hannula <anssi.hannula@gmail.com>]

Dmitriy Geels wrote:
> 2009/2/19 Anssi Hannula <anssi.hannula@gmail.com>
>> Dmitriy Geels wrote:
>>> Yes. That's the problem.
>>> Exactly this sequence: run fftest, play all effects, then run
>>> ffmvforce. ffmvforce itself is working well.
>> Could you provide the log with fixed fftest+ffmvforce?
> 
> Sorry for making you waiting so long, here is it:
> http://paste.org.ru/index.pl?p584s9
> 
> Nothing special -- running fftest, playing 0, 1, 2, 3, 4, 5 (2 and 3
> does nothing), then -1, then run ffmvforce, click somewhere inside
> it's window -- then first "pid_block_load requested" appears, after
> "pid_block_load failed 20 times" (I decreased retries counter)
> ffmvforce continues to work, but ioctl() call always return -1
> 
> That's all. Running fftest again repeats "pid_block_load requested"
> scenario. Device (or driver?) stuck.

These seem strange:
[ 5108.143241] usbhid:hid-pidff: create_new_effect sent, type: 4
[ 5108.161645] usbhid:hid-pidff: create_new_effect sent, type: 1
[ 5108.251905] usbhid:hid-pidff: create_new_effect sent, type: 4
[ 5108.338133] usbhid:hid-pidff: create_new_effect sent, type: 4

Type 4 means FF_SINE for your device. However, fftest does test only one
FF_SINE effect. Have you altered fftest? If not, could you post the
output of fftest?

-- 
Anssi Hannula