From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Sergey Kolesnikov <rockingdemon@gmail.com>,
linux-input@vger.kernel.org, Tim Cole <tim.cole@canonical.com>,
Tim Gardner <tim.gardner@canonical.com>,
Amit Kucheria <amit.kucheria@canonical.com>,
Stefan Bader <stefan.bader@canonical.com>
Subject: Re: linux kernel HID problem with Saitek X52 Pro Flight System
Date: Tue, 8 Sep 2009 10:58:50 -0700 [thread overview]
Message-ID: <20090908183222.9D13E526EC9@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <alpine.LNX.2.00.0909081931360.23856@wotan.suse.de>
On Tue, Sep 08, 2009 at 07:42:02PM +0200, Jiri Kosina wrote:
>
> [ added some CCs
>
> In short -- Sergey has problem with his joystick not being properly
> handled starting with 2.6.30 kernel (it used to work with 2.6.29 and
> older). The problem is that joydev is not created. ]
>
>
> On Mon, 7 Sep 2009, Sergey Kolesnikov wrote:
>
> > Here goes /proc/bus/input/devices dump (VID/PID included):
> >
> > I: Bus=0003 Vendor=06a3 Product=0762 Version=0111
> > N: Name="Saitek Saitek X52 Pro Flight Control System"
> > P: Phys=usb-0000:00:1d.7-6.3/input0
> > S: Sysfs=/devices/pci0000:00/0000:00:1d.7/usb7/7-6/7-6.3/7-6.3:1.0/input/input10
> > U: Uniq=
> > H: Handlers=event6
> > B: EV=1b
> > B: KEY=7f ffffffff00000000 0 0 0 0
I find it doubtful that the device actually has 39 buttons...
> > B: ABS=3000003007f
> > B: MSC=10
>
> If I got my math right, this means that the KEY bitmask includes digitizer
> BTN_DIGI/BTN_TOOL_PEN, right?
>
> Sergey, I believe that reverting commit d07a9cba6b (you can do so using
> git revert d07a9cba6b) will fix your joystick, is that correct?
While this will get Sergey's joystick back I think that HID should be
more careful in assigning the BTN_* events. Right now it starts at a
certain type and goes forward without checking if range (joystick,
gamepad, etc) is exhausted or not.
--
Dmitry
next prev parent reply other threads:[~2009-09-08 17:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bfb1bb1f0909061357m4006a61co1c1b4dfa483b947b@mail.gmail.com>
[not found] ` <alpine.LNX.2.00.0909071731120.23856@wotan.suse.de>
[not found] ` <bfb1bb1f0909071047h1a4cbc3dx175f89ecedc3555d@mail.gmail.com>
2009-09-08 17:42 ` linux kernel HID problem with Saitek X52 Pro Flight System Jiri Kosina
2009-09-08 17:58 ` Dmitry Torokhov [this message]
2009-09-08 18:02 ` Jiri Kosina
[not found] ` <bfb1bb1f0909081304y708b037bw1c82288d6457c254@mail.gmail.com>
2009-09-08 20:49 ` Dmitry Torokhov
2009-09-08 22:43 ` Jiri Kosina
2009-12-10 17:31 ` Stefan Bader
2009-12-11 14:18 ` Tim Cole
2009-12-11 14:24 ` Stefan Bader
2009-12-11 23:02 ` Tim Cole
2009-12-12 2:00 ` Anssi Hannula
2009-12-12 4:44 ` Dmitry Torokhov
2009-12-14 10:31 ` Stefan Bader
2009-12-14 17:36 ` Dmitry Torokhov
2009-12-15 12:58 ` Jiri Kosina
2009-12-15 13:17 ` Stefan Bader
2009-12-17 1:29 ` Jiri Kosina
2009-12-17 1:38 ` Dmitry Torokhov
2009-12-18 15:10 ` Jiri Kosina
2009-12-18 17:49 ` Dmitry Torokhov
2009-12-22 13:31 ` Jiri Kosina
2009-12-23 18:55 ` Dmitry Torokhov
2010-01-04 11:17 ` 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=20090908183222.9D13E526EC9@mailhub.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=amit.kucheria@canonical.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=rockingdemon@gmail.com \
--cc=stefan.bader@canonical.com \
--cc=tim.cole@canonical.com \
--cc=tim.gardner@canonical.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;
as well as URLs for NNTP newsgroup(s).