On Wed, Feb 03, 2010 at 11:53:20AM +0100, Jiri Kosina wrote: > 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. aah, don't we love a good brown paper bag moment... events are below, if I read this correctly the hardware might need a quirk for the permanently-set InRange bits. report (size 6) (numbered) report 2 (size 6) = 02 03 69 0e c4 03 Digitizers.TipSwitch = 1 Digitizers.InRange = 1 GenericDesktop.X = 3689 GenericDesktop.Y = 964 report (size 6) (numbered) report 2 (size 6) = 02 03 6f 0e bb 03 Digitizers.TipSwitch = 1 Digitizers.InRange = 1 GenericDesktop.X = 3695 GenericDesktop.Y = 955 [...] report (size 6) (numbered) report 2 (size 6) = 02 02 71 0e a9 03 Digitizers.TipSwitch = 0 Digitizers.InRange = 1 GenericDesktop.X = 3697 GenericDesktop.Y = 937 report (size 6) (numbered) report 2 (size 6) = 02 03 68 0e d1 03 Digitizers.TipSwitch = 1 Digitizers.InRange = 1 GenericDesktop.X = 3688 GenericDesktop.Y = 977 report (size 6) (numbered) report 2 (size 6) = 02 03 67 0e d1 03 Digitizers.TipSwitch = 1 Digitizers.InRange = 1 GenericDesktop.X = 3687 [...] report (size 6) (numbered) report 2 (size 6) = 02 02 7b 0e dd 03 Digitizers.TipSwitch = 0 Digitizers.InRange = 1 GenericDesktop.X = 3707 GenericDesktop.Y = 989 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
