From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: Re: linux kernel HID problem with Saitek X52 Pro Flight System Date: Thu, 10 Dec 2009 18:31:59 +0100 Message-ID: <4B21308F.5070304@canonical.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from adelie.canonical.com ([91.189.90.139]:47924 "EHLO adelie.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761290AbZLJRb4 (ORCPT ); Thu, 10 Dec 2009 12:31:56 -0500 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Jiri Kosina Cc: Sergey Kolesnikov , linux-input@vger.kernel.org, Dmitry Torokhov , Tim Cole Jiri Kosina wrote: > On Wed, 9 Sep 2009, Sergey Kolesnikov wrote: > >> Yes, reverting this commit helps. I've tried jstest and succeeded to >> change the state of each available button/axis. > > Thanks for verifying. > >> May be there is another way to distinguish between such joysticks and >> digitizers? > > Well, first I'll need the report descriptor dump (i.e. the HID debugging > output, see one of the previous mails), to see how the device is > presenting itself to the system. And then possibly fix the input mapping > in HID code, so that we don't infringe on mappings of different device > classes. > I know this is quite a long time ago now, but has there be any outcome on how to handle those joysticks? -Stefan