Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754445Ab0BCKxX (ORCPT ); Wed, 3 Feb 2010 05:53:23 -0500 Received: from cantor2.suse.de ([195.135.220.15]:51895 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752897Ab0BCKxV (ORCPT ); Wed, 3 Feb 2010 05:53:21 -0500 Date: Wed, 3 Feb 2010 11:53:20 +0100 (CET) From: Jiri Kosina To: Peter Hutterer Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] HID: add multi-input quirk for eGalax Touchcontroller In-Reply-To: <20100203033914.GA23850@barra.bne.redhat.com> Message-ID: References: <20100202034040.GA16880@barra.bne.redhat.com> <20100203033914.GA23850@barra.bne.redhat.com> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1075 Lines: 24 On Wed, 3 Feb 2010, Peter Hutterer wrote: > > 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. The hid descriptor table is attached, but tbh I'm not well-versed > enough in the HID protocol to even tell what format I can give you. I've > attached a simple hexdump of two presses, one with a finger, one with the > stylus. Let me know what format you need or what how I can start to decypher > this myself (are there any parsing tools around?). It shouldn't be necesarry to run hexdump on the 'events' node, the data coming from it are supposed to already be parsed and human-readable. -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/