Re: linux kernel HID problem with Saitek X52 Pro Flight System

From: Jiri Kosina <jkosina@suse.cz>
To: Stefan Bader <stefan.bader@canonical.com>
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: Thu, 17 Dec 2009 02:29:55 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.0912170229340.3755@pobox.suse.cz> (raw)
In-Reply-To: <4B278C67.5050505@canonical.com>

On Tue, 15 Dec 2009, Stefan Bader 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).

Dmitry, do you have any preference here yourself?

-- 
Jiri Kosina
SUSE Labs, Novell Inc.