From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id C8B7D29736 for ; Wed, 29 May 2024 16:21:11 +0200 (CEST) Received: from gaff.inri.net ([168.235.71.243]) by 9front; Wed May 29 10:19:09 -0400 2024 Received: from [127.0.0.1] ([168.235.81.125]) by gaff; Wed May 29 10:19:09 -0400 2024 Date: Wed, 29 May 2024 10:19:07 -0400 From: Stanley Lieber To: 9front@9front.org In-Reply-To: <93196A5AB533F031FD74F0BE4C4CF406@felloff.net> References: <93196A5AB533F031FD74F0BE4C4CF406@felloff.net> Message-ID: <3BB4C362-D2BC-4406-A829-5C792A8BAB97@stanleylieber.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: metadata-scale STM-aware hypervisor browser Subject: Re: [9front] Wacom WACF008 glitching on ThinkPad X60/X61 Tablets Reply-To: 9front@9front.org Precedence: bulk On May 29, 2024 5:24:04 AM EDT, cinap_lenrek@felloff=2Enet wrote: >i said before, you need to capture the bytes going thru the serial here, >to see what is going on and if we have a chance working around it=2E > >instrument the driver and log the bytes in hex into a logfile, >with a timestamp=2E > >-- >cinap > the reason i didn't do this already is because i don't know how=2E i trian= gulated the undesirable behavior and worked around it=2E badly, yes, which = is why i posted here for comments=2E but what i did do does allow me to dra= w without glitches, so as a start, at least, i wanted to share this to bene= fit others struggling with the same behavior=2E i realize i didn't address = the underlying problem=2E the bitwise stuff happening in query() and readpacket() looks like gibberi= sh to me=2E i'm sure it's all quite compact and sensible, but when i look a= t it, i'm just hearing the teacher from charlie brown=2E in order to log ra= w bytes, should i just be dumping the entirety of buf (in readpacket()) to = disk? and then how do i interpret it? i did not have any luck searching for documentation on the protocol this d= evice uses=2E i did try looking at the linux driver, but again, it's miss o= thmar all the way down=2E thanks, sl