From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ben Gamari Subject: Re: New Alps protocol in the wild? Date: Thu, 16 Aug 2012 01:04:32 -0400 Message-ID: <87sjbnzau7.fsf@gmail.com> References: <20120814103553.GF23370@arianrhod.panaceas.james.local> <87mx1xxy1y.fsf@gmail.com> <20120814160519.GC12473@artemis.panaceas.org> <87ipckwvp4.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-qc0-f174.google.com ([209.85.216.174]:53001 "EHLO mail-qc0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752807Ab2HPFEf (ORCPT ); Thu, 16 Aug 2012 01:04:35 -0400 Received: by qcro28 with SMTP id o28so1836296qcr.19 for ; Wed, 15 Aug 2012 22:04:35 -0700 (PDT) In-Reply-To: <87ipckwvp4.fsf@gmail.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: James , Ignacio Casal Quinteiro Cc: linux-input@vger.kernel.org Ben Gamari writes: snip > > Hopefully I'll find some more time in the next few days to figure out > the last few bits (primarily how multitouch events work). I wouldn't be > sad if someone finished the task for me, however. > Success! As it turns out, the process was actually not so bad. While I wasted much of the night trying to reverse the protocol, I realized that what I had come up with was nearly identical to the version 3 documentation. Trying the version 3 protocol with the device, I found that it was nearly immediately functional. It seems that while the initialization procedure has changed, the position report format is identical to previous generations. My tree[1] currently has a hacked brute-force initialization implementation, although it would probably be nice to figure out what this sequence actually means. Otherwise, it seems support for this device is a solved problem. Feel free to give my tree a try. I'd be interested to know whether it works for you. Cheers, - Ben [1] https://github.com/bgamari/linux/tree/alps