From: Anssi Hannula <anssi.hannula@gmail.com>
To: Dmitriy Geels <dmitriy.geels@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: hid-pidff bug: fails to find all required reports of saitek gamepad
Date: Mon, 02 Mar 2009 22:35:12 +0200 [thread overview]
Message-ID: <49AC4300.5090002@gmail.com> (raw)
In-Reply-To: <78f5d6bf0903021041o24155b7dg89a5fb975e60c320@mail.gmail.com>
Dmitriy Geels wrote:
> 2009/2/27 Anssi Hannula <anssi.hannula@gmail.com>:
>> 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?
> No i didn't, fftest plays 4 different effect types, of which only 2
> are supported,
> Here is output: http://paste.org.ru/index.pl?jc3999
> Here is source of this fftest: http://paste.org.ru/index.pl?jjkw01
Oh, right, FF_RUMBLE is mapped to FF_PERIODIC by default. I have a local
patch for your device that maps it to FF_CONSTANT, that's why I was
confused.
So that wasn't the issue.
What about running fftest two times in succession, or just ffmvforce two
times in succession, does it trigger the problem?
Also, try removing some effects from fftest one-by-one, and see if the
problem is still triggered.
--
Anssi Hannula
next prev parent reply other threads:[~2009-03-02 20:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 19:45 hid-pidff bug: fails to find all required reports of saitek gamepad Dmitriy Geels
2009-02-02 15:50 ` Anssi Hannula
2009-02-02 18:29 ` Dmitriy Geels
2009-02-02 18:48 ` Dmitriy Geels
2009-02-07 12:28 ` Anssi Hannula
[not found] ` <78f5d6bf0902092146x2abaf45an79e4546e75a80356@mail.gmail.com>
2009-02-10 7:49 ` Dmitriy Geels
2009-02-10 7:49 ` Fwd: " Dmitriy Geels
2009-02-10 16:06 ` Anssi Hannula
2009-02-11 9:12 ` Dmitriy Geels
2009-02-11 16:27 ` Anssi Hannula
2009-02-12 18:06 ` Dmitriy Geels
2009-02-12 18:42 ` Anssi Hannula
2009-02-13 8:33 ` Dmitriy Geels
2009-02-13 19:43 ` Anssi Hannula
[not found] ` <78f5d6bf0902141125m1bf9ac00xb2b414e81d81b869@mail.gmail.com>
[not found] ` <49972478.3060207@gmail.com>
2009-02-14 22:33 ` Dmitriy Geels
2009-02-17 12:16 ` Dmitriy Geels
2009-02-18 15:45 ` Anssi Hannula
2009-02-19 6:56 ` Dmitriy Geels
[not found] ` <78f5d6bf0902182254v191cc485x62eb211baaddd36@mail.gmail.com>
[not found] ` <499D7C66.6090000@gmail.com>
2009-02-26 21:21 ` Dmitriy Geels
2009-02-27 16:24 ` Anssi Hannula
2009-03-02 18:41 ` Dmitriy Geels
2009-03-02 20:35 ` Anssi Hannula [this message]
2009-03-03 6:28 ` Dmitriy Geels
2009-03-03 18:35 ` Dmitriy Geels
2009-03-07 14:38 ` Anssi Hannula
2009-03-08 5:18 ` Dmitriy Geels
2009-03-08 10:16 ` Anssi Hannula
2009-03-09 19:08 ` Dmitriy Geels
2009-05-07 23:45 ` Anssi Hannula
2009-05-07 23:57 ` Anssi Hannula
[not found] ` <78f5d6bf0906041227w3a58bde0u554a3d3336e17fa6@mail.gmail.com>
2009-06-06 12:14 ` Anssi Hannula
2009-06-09 5:02 ` Dmitriy Geels
2009-06-09 6:09 ` Alek Du
2009-06-09 7:37 ` Dmitriy Geels
2009-06-11 9:38 ` Dmitriy Geels
2009-06-11 20:11 ` Dmitriy Geels
2009-07-09 17:41 ` Dmitriy Geels
2009-07-09 17:58 ` Anssi Hannula
2009-11-06 9:06 ` Dmitriy Geels
2009-11-09 12:00 ` Dmitriy Geels
2009-11-20 14:17 ` Dmitriy Geels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49AC4300.5090002@gmail.com \
--to=anssi.hannula@gmail.com \
--cc=dmitriy.geels@gmail.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).