Re: [PATCH v4 01/24] input: Add ff-memless-next module

From: Elias Vanderstuyft <elias.vds@gmail.com>
To: Simon Wood <simon@mungewell.org>
Cc: "Roland Bosa" <rbosa@logitech.com>,
	"Michal Malý" <madcatxster@devoid-pointer.net>,
	"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jiri Kosina" <jkosina@suse.cz>,
	"Anssi Hannula" <anssi.hannula@iki.fi>
Subject: Re: [PATCH v4 01/24] input: Add ff-memless-next module
Date: Wed, 21 May 2014 16:05:14 +0200	[thread overview]
Message-ID: <CADbOyBROC4eeUWkEG687bwOXyqDieD+wt7J855H0z6F=Mchx_w@mail.gmail.com> (raw)
In-Reply-To: <2643156.2tkLFqgYFg@sigyn>

On Wed, May 21, 2014 at 4:13 AM, Michal Malý
<madcatxster@devoid-pointer.net> wrote:
> On Tuesday 20 of May 2014 18:17:51 Roland Bosa wrote:
>>
>> The file format of an IFR is probably easily deducible. There's a lot of
>> textual clues to parameters and the values are also written out in
>> string form.
>>
>> I don't have a FEdit file at hand, but I suppose it will be similar.
>
> I believe that Elias successfully reverse engineered the effect file format
> produced by FEdit. There is no support for this kind of prefabricated effects
> in the Linux FF API.

Of course I did, Simon, what did you expect? :P
Here you are:
http://www.winehq.org/pipermail/wine-devel/2014-February/103108.html
It contains a description of the DInput effect file format (.ffe), a
working Python script to load these files and dump their contents, as
well as a bunch of example files and tests/results.
The FFE file format is binary RIFF, if you're interested.

But I prefer not to include such things in the Linux kernel, I believe
this is the task of the userspace application.
I'm planning to implement this function into Wine, but maybe SDL would
benefit from similar functionality too (using an open file-format
instead, of course)?
Anyway, this is off-topic.

Elias