From: Johann D. <jo...@Do...> - 2002-01-20 20:05:48
|
On Sun, 20 Jan 2002, Rodrigo Damazio wrote: > Johann Deneux wrote: > > > > >I checked it. It's not the iforce, protocol, what would have been > >surprising anyway. The bit used for the deadman sensor just happend to be > >the same bit as I-Force uses, but that was just luck. > > > I supposed it is the standard PID protocol then?? I realized it Probably. > should be something other than I-Force, because I tried adding the > joystick to iforce-main.c and iforce-usb.c and it just didn't work. Then > I suppose we must implement a non-I-force PID driver, am I correct?? If > so I suggest we use the same base API and ioctls that are being used for > I-Force, just sending different data to the device...perhaps (to be > better organized), take the common part of the current I-force code and > put it as generic force feedback code, then add I-force and standard PID > as sub-options... 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). -- Johann Deneux |