mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Piotr Sawuk <a9702387@unet.univie.ac.at>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: joystick.c
Date: Tue, 9 Jul 2002 18:38:41 +0200	[thread overview]
Message-ID: <20020709183841.A10953@ucw.cz> (raw)
In-Reply-To: <3D2AB938.52461BDE@unet.univie.ac.at>; from a9702387@unet.univie.ac.at on Tue, Jul 09, 2002 at 10:21:44AM +0000

On Tue, Jul 09, 2002 at 10:21:44AM +0000, Piotr Sawuk wrote:

> Sorry if I'm off-topic here, since I don't read this list.
> also when replying please send me a copy...
> 
> in function js_correct(value,corr) I've found the instructions:
> 
> if (value < -32767) return -32767;
> if (value > 32767) return 32767;
> 
> what's the use of these? I'm asking because my new usb-joystick
> is returning those values somewhere in the middle of it's threshold
> and I was wondering if disabling the above would do any good?

The data coming from the joystick is defined to be bound by this range.
It's signed 16 bit anyway.

> however, the actual reason why I've looked into that file was
> because wine reported strange joystick-events 6,7,8,9 and I
> just can't figure out what those are supposed to do. I've found
> JS_EVENT 1 and 2 in the linux/joystick.h include, but no mention
> of anything related to the number '6'. does anyone know anything
> about those joystick events?

What joystick is it? This looks like a problem with the HID driver.

-- 
Vojtech Pavlik
SuSE Labs

  parent reply	other threads:[~2002-07-09 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09 10:21 joystick.c Piotr Sawuk
2002-07-09 16:17 ` joystick.c Thunder from the hill
2002-07-09 16:38 ` Vojtech Pavlik [this message]
2002-07-12  5:00   ` joystick.c Piotr Sawuk

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=20020709183841.A10953@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=a9702387@unet.univie.ac.at \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®