From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Renato Golin" <rengolin@gmail.com>
Cc: "Jiri Kosina" <jkosina@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: joydev.c and saitek cyborg evo force
Date: Tue, 12 Jun 2007 09:13:06 -0400 [thread overview]
Message-ID: <d120d5000706120613o7a328e59v3cba37f0ced88e77@mail.gmail.com> (raw)
In-Reply-To: <d9b9d95f0706120608g979b89oc79dbc277d19862b@mail.gmail.com>
Hi Renato,
On 6/12/07, Renato Golin <rengolin@gmail.com> wrote:
> On 12/06/07, Jiri Kosina <jkosina@suse.cz> wrote:
> > the thing is that the aim of this quirk is to normalize the values that
> > are being reported by bogus devices, so we don't really want to trust the
> > values they provide here, do we?
>
> Hi Jiri,
>
> I don't know about the other joysticks, but Saitek did reported [0,
> 4096] which is the right answer, but between HID and Joydev it was
> converted to [-127, 127]. I thought that the quirk was about that.
>
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
0 -> -32768
204 -> -29504
408 -> -26240
612 -> -22976
816 -> -19712
1020 -> -16448
1224 -> -13184
1428 -> -9920
1632 -> -6656
1836 -> -3392
2040 -> -128
2244 -> 3136
2448 -> 6400
2652 -> 9664
2856 -> 12928
3060 -> 16192
3264 -> 19456
3468 -> 22720
3672 -> 25984
3876 -> 29248
4080 -> 32512
Which is fine as far as I can see. What utility did you use that
reported [-127; 127] range?
--
Dmitry
next prev parent reply other threads:[~2007-06-12 13:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:54 Renato Golin
2007-05-18 21:35 ` Renato Golin
2007-05-21 4:16 ` Dmitry Torokhov
2007-05-21 12:49 ` Jiri Kosina
2007-05-24 13:27 ` Renato Golin
2007-05-29 23:57 ` Renato Golin
2007-05-30 0:10 ` Jiri Kosina
2007-05-30 9:14 ` Renato Golin
2007-05-30 14:56 ` Jiri Kosina
2007-05-30 15:18 ` Renato Golin
2007-05-30 22:26 ` Renato Golin
2007-05-31 19:53 ` Dmitry Torokhov
2007-05-31 20:22 ` Jiri Kosina
2007-05-31 21:48 ` Jiri Kosina
2007-06-01 18:16 ` Renato Golin
2007-06-03 9:41 ` Jiri Kosina
2007-06-04 22:06 ` Renato Golin
2007-06-04 22:10 ` Jiri Kosina
2007-06-04 22:46 ` Renato Golin
2007-06-12 12:28 ` Renato Golin
2007-06-12 12:37 ` Jiri Kosina
2007-06-12 13:08 ` Renato Golin
2007-06-12 13:13 ` Dmitry Torokhov [this message]
2007-06-12 13:31 ` Renato Golin
2007-06-12 13:45 ` Dmitry Torokhov
2007-06-12 15:25 ` Jiri Kosina
2007-06-14 22:24 ` Renato Golin
2007-06-20 10:00 ` Jiri Kosina
2007-07-21 0:10 ` Renato Golin
2007-08-10 15:10 ` Jiri Kosina
2007-08-10 15:54 ` Jiri Kosina
2007-08-11 17:38 ` Renato Golin
2007-08-11 21:06 ` Jiri Kosina
2007-08-11 21:15 ` Renato Golin
2007-08-10 16:31 ` Renato Golin
2007-08-11 13:42 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d120d5000706120613o7a328e59v3cba37f0ced88e77@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rengolin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome