Re: hello...and MS-FF2...

[Bj|rn A. <d3a...@dt...>]

Quoting Rodrigo Damazio <cu...@uo...>:
> Johann Deneux wrote:
> >On Sun, 20 Jan 2002, Rodrigo Damazio wrote:
> >>>
> >>        I supposed it is the standard PID protocol then?? I realized it 
> >
> >Probably.
> >
>         What else do we need to check to see if it is?? (I have a lot of 
> free time these days, I can do it)

Implement the PID spec and see if it works... :)
 
No, really, I have no reason to doubt that it is really a PID device. It
says it is, it has very plausible reports in it, and the dumps you sent
looks good. (at least the parts I've read.)

> >Vojtech and I designed the ff API so that it's not I-Force specific. We
> >may need to add/change some parts of the API, but what the ff_effect
> >struct is supposed to be generic enough to be used with other kinds of
> >devices. Have a look at input.h. Nothing in it should be I-Force specific.
> >Now, it's true there are parts that could be re-used or adapted from
> >iforce.c (the parameter blocks allocation and handling, for example).
> >
>         Yes, I had realized that - everything is quite generic...

I agree. It's a good interface.

>         I'll try to create a ff_pid.c file based on iforce*.c, and make 
> it send the data according to the PID specs and the dumps I have...or 
> have any of you already started that?

Yes, I have. As of now I can upload (some) effects, but I haven't been 
able to play on yet. Hopefully tonight... I'll try to get some patches
sent as well - there's a few more generic fixes in there as well. 

>         Btw, how do custom effects work??

Just like any other effect, all you have to do is send that data along
in another report. Look at the diagram on page 44 of the PID spec, it's
fairly clear.

/August.
-- 
Wrong on most accounts.  const Foo *foo; and Foo const *foo; mean the same: foo
being a pointer to const Foo.  const Foo const *foo; would mean the same but is
illegal (double const).  You are confusing this with Foo * const foo; and const
Foo * const foo; respectively. -David Kastrup, comp.os.linux.development.system