public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Chazarain <guichaz@yahoo.fr>
To: linux-kernel@vger.kernel.org, linux-joystick@atrey.karlin.mff.cuni.cz
Subject: snd-ens1371 (alsa) & joystick woes
Date: Tue, 12 Apr 2005 13:10:58 +0200	[thread overview]
Message-ID: <425BACC2.9020709@yahoo.fr> (raw)

Hi,

 From 2.6.11 to 2.6.12-rc2, there are some changes in the joystick behaviour
that I don't think are expected. It's a simple joystick using analog.ko 
plugged
on a sound board using snd-ens1371. So here we go:

With 2.6.11:
$ jstest /dev/input/js0
Joystick (Analog 3-axis 4-button joystick) has 3 axes and 4 buttons. 
Driver version is 2.1.0.
Testing ... (interrupt to exit)
Axes:  0: 32767  1:-32767  2:-32767 Buttons:  0:off  1:off  2:off  3:off

Works ok, button0 is the one that serves as a gun trigger. All buttons
work as expected when I use them.

$ jstest --event /dev/input/js0
Joystick (Analog 3-axis 4-button joystick) has 3 axes and 4 buttons. 
Driver version is 2.1.0.
Testing ... (interrupt to exit)
# ...
Event: type 1, time 201830, number 0, value 0
Event: type 1, time 202082, number 0, value 1
Event: type 1, time 202229, number 0, value 0
Event: type 1, time 202355, number 0, value 1
# ...

I repeatedly press the button0, works OK.

Now with 2.6.12-rc2:

$ jstest /dev/input/js0
Joystick (Analog 3-axis 4-button joystick) has 3 axes and 5 buttons. 
Driver version is 2.1.0.
Testing ... (interrupt to exit)
Axes:  0:     0  1:     0  2:-31874 Buttons:  0:off  1:off  2:off  
3:off  4:off

Huh, now it says it has 5 buttons. The button0 is disabled, and hitting
the gun trigger (button0 in 2.6.11) changes the button4. Others buttons
work as expected.


$ jstest --event /dev/input/js0
Joystick (Analog 3-axis 4-button joystick) has 3 axes and 5 buttons. 
Driver version is 2.1.0.
Testing ... (interrupt to exit)
# ...
Event: type 1, time -147737, number 4, value 0
Event: type 1, time -147170, number 4, value 1
Event: type 1, time -146991, number 4, value 0
Event: type 1, time -146834, number 4, value 1
Event: type 1, time -146676, number 4, value 0
Event: type 1, time -146529, number 4, value 1
Event: type 1, time -146361, number 4, value 0
Event: type 1, time -146193, number 4, value 1
Event: type 1, time -146004, number 4, value 0
Event: type 1, time -145836, number 4, value 1
Event: type 1, time -145710, number 4, value 0
Event: type 1, time -145385, number 4, value 1
Event: type 1, time -145269, number 4, value 0
# ...

Still playing with the gun trigger, the negative time must be the jiffies
initialisation to -300*HZ, but the number 4 seems wrong.

Thanks.

-- 
Guillaume


             reply	other threads:[~2005-04-12 12:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 11:10 Guillaume Chazarain [this message]
2005-04-12 13:23 ` snd-ens1371 (alsa) & joystick woes Patrick McFarland
2005-04-12 13:28   ` Guillaume Chazarain
2005-04-15  9:36 ` Guillaume Chazarain
2005-04-29  3:12   ` Dmitry Torokhov
2005-04-29  9:07     ` Guillaume Chazarain
     [not found] <3Ssnv-QY-7@gated-at.bofh.it>
     [not found] ` <3StMH-1XF-49@gated-at.bofh.it>
2005-04-12 21:12   ` Bodo Eggert <harvested.in.lkml@posting.7eggert.dyndns.org>

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=425BACC2.9020709@yahoo.fr \
    --to=guichaz@yahoo.fr \
    --cc=linux-joystick@atrey.karlin.mff.cuni.cz \
    --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