From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Kosina Subject: Re: [PATCH] HID: add multi-input quirk for eGalax Touchcontroller Date: Tue, 2 Feb 2010 22:44:35 +0100 (CET) Message-ID: References: <20100202034040.GA16880@barra.bne.redhat.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from cantor.suse.de ([195.135.220.2]:38303 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754747Ab0BBVog (ORCPT ); Tue, 2 Feb 2010 16:44:36 -0500 In-Reply-To: <20100202034040.GA16880@barra.bne.redhat.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Peter Hutterer Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org On Tue, 2 Feb 2010, Peter Hutterer wrote: > Nonetheless, I'm not sure about whether that's the right thing to do. With > this patch applied, it gives me two devices, one mute, the other one > announces BTN_PEN and BTN_TOUCH + abs axes, though only BTN_TOUCH is ever > triggered. Loading usbtouchscreen instead of usbhid for this device makes > the device look more sane BTN_TOUCH + abs axes but the actual data is > random. So I'm not quite sure what the fix is supposed to be, any hints are > appreciated if it's not the patch below. The data could also be mis-interpreted because of some bug in the HID descriptor. Does looking at the HID report descriptor and looking at the actual raw HID reports coming out from the device give any clue? (in recent kernels, you can just use 'hid' directory in debugfs to gather all this information). Thanks, -- Jiri Kosina SUSE Labs, Novell Inc.