From: Stefan Bader <stefan.bader@canonical.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Anssi Hannula <anssi.hannula@iki.fi>,
Tim Cole <tim.cole@canonical.com>,
Sergey Kolesnikov <rockingdemon@gmail.com>,
linux-input@vger.kernel.org
Subject: Re: linux kernel HID problem with Saitek X52 Pro Flight System
Date: Tue, 15 Dec 2009 14:17:27 +0100 [thread overview]
Message-ID: <4B278C67.5050505@canonical.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0912151357210.3755@pobox.suse.cz>
Jiri Kosina wrote:
> On Mon, 14 Dec 2009, Dmitry Torokhov wrote:
>
>>> This might be an overly naive approach (or call it thinking loudly)...
>>> It would probably break a lot of stuff when the JOYSTICK/TRIGGER block
>>> moved to the 0x210 region, but would it be a solution to have a block
>>> of additional joystick buttons there and check on assigning buttons to
>>> a joystick, whether it traverses over to GAMEPAD and in that case skip
>>> to the additional block?
>> That's what we have to do I guess... I wonder how many keycodes will we
>> need so we won't have to split the region again? Will they come up with
>> 70 buttons next time?
>
> Yup, I am not able to come up with anything more clever either.
>
> I can do that easily ... any suggestions for button names? :)
>
#define BTN_TRIGGER_HAPPY01 0x210
...
#define BTN_TRIGGER_HAPPY40 0x238
:-P Assuming 40 additional buttons should be crazy enough (but I know
this has been said before about other things).
-Stefan
next prev parent reply other threads:[~2009-12-15 13:17 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
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 [this message]
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=4B278C67.5050505@canonical.com \
--to=stefan.bader@canonical.com \
--cc=anssi.hannula@iki.fi \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=rockingdemon@gmail.com \
--cc=tim.cole@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.