From: Vojtech P. <vo...@su...> - 2002-04-12 08:55:22
|
On Thu, Apr 11, 2002 at 11:48:07AM -0300, Rodrigo Damazio wrote: > Fabien Brachere wrote: > > >Rodrigo Damazio wrote : > > > >>Fabien Brachere wrote: > >> > >>>Ok, I didn't have an heart attack, and I put all this stuff on a very > >>>minimal web site: http://madfab.free.fr/ff/index.html > >>> > >>>Fabien Brachere > >>> > >> Nicely done...perhaps you'd like to help with the PID code? > >>Instead of registering itself for specific USB device IDs, it's a > >>subclass of the HID class, so whenever a HID device is detected, it > >>checks if it's also PID-compliant, and if it is then you can use force > >>feedback calls on it(this also allows us to not worry at all about > >>reading the axes input, since HID does that already)...the structs for > >>these calls are the very same that are used for I-Force, the only > >>difference is how we generate and send packets to the device... > >> > > > >I know that the Sidewinder is registered by the HID module, but I'm not > >satisfy with this: the joydev module report 24 buttons and 10 axes (it's > >a big joystick but not so big ...), the only quick solution I found is > >to short-cut hid by specifying USB device IDs, it's just for > >development, I think we can see this later. > > > That's indeed true...I wonder why that happens - is it the > joystick that reports itself as having all that, or is it a bug in the > HID code? I think it's too small of a thing to re-create the driver > though, it can probably be fixed... Most likely some of the PID stuff gets assigned as buttons/axes, because no better match can be found - there are fallbacks in the input<->hid mapping code. > >The first important thing is to implement correct upload effect to the > >device memory, once uploaded it's trivial to play it. > > > I know...that's what I'm working on...these last days I merged > parts of the code from Bjorn and added missing parts to it, so it > already detects all FF capabilities of the joystick... -- Vojtech Pavlik SuSE Labs |