Messages in this thread | | | Date | Tue, 12 Jun 2007 14:31:49 +0100 | From | "Renato Golin" <> | Subject | Re: joydev.c and saitek cyborg evo force |
| |
On 12/06/07, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote: > We need to find out why you see [-127, 127] range, because if joydev > would see [0, 4096] range it would perform automatic correction and > map values like this: > > c0: 2048, c1: 2048, c2: 262144, c3: 262144
Hi Dmitry,
That's the values I got *after* calibration. Before, because the correction is set to a small signed value, it corrects wrongly and report a random mix of signed and unsigned values when moving in one direction...
> Which is fine as far as I can see. What utility did you use that > reported [-127; 127] range?
At joydev_connect, the last parameter "input_dev" reports me that range (dev->absmax[i] and dev->absmin[i]). When I turned on HID_DEBUG it reported [0, 4096] for both axis 0 and 1, which is correct so it must be between HID and joydev.
My point is that the auto-calibration could automagically solve all range problems in all devices by zeroing the range and adapting the ranges afterwards. If it can affect other devices as well as joysticks, the calibration could happen in HID instead of joydev.
cheers, --renato
Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |