From mboxrd@z Thu Jan 1 00:00:00 1970 From: simon@mungewell.org Subject: Re: [PATCH] hid: Fix Logitech Driving Force Pro wheel Date: Sat, 28 May 2011 19:47:32 -0400 Message-ID: <8942e3cdf4941912b0855e64939e5939.squirrel@host171.canaca.com> References: <201105282037.22888.michael@m-bauer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from host171.canaca.com ([67.55.55.225]:54250 "EHLO host171.canaca.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754852Ab1E1Xre (ORCPT ); Sat, 28 May 2011 19:47:34 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Michael Bauer Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, Jiri Kosina > 2). The original does Y then 3 others, the replacement does Y + RZ then 1 > other. OK I missed that you had 'disabled' the first byte value after the hat switch (which is presumably the combined acc-brake), in preference for the seperate ACC and Brake. Is there a reason to prevent the combined acc-brake being reported to the system? Surely it would be best to report all options so that the app can decide which one to use.... I can see that you might want to relabel them for consistance with Windows. Do you know what the 4th (and last) byte value is? Simon