9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Wacom WACF008 glitching on ThinkPad X60/X61 Tablets
Date: Wed, 29 May 2024 10:19:07 -0400	[thread overview]
Message-ID: <3BB4C362-D2BC-4406-A829-5C792A8BAB97@stanleylieber.com> (raw)
In-Reply-To: <93196A5AB533F031FD74F0BE4C4CF406@felloff.net>

On May 29, 2024 5:24:04 AM EDT, cinap_lenrek@felloff.net 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.
>
>instrument the driver and log the bytes in hex into a logfile,
>with a timestamp.
>
>--
>cinap
>

the reason i didn't do this already is because i don't know how. i triangulated the undesirable behavior and worked around it. badly, yes, which is why i posted here for comments. but what i did do does allow me to draw without glitches, so as a start, at least, i wanted to share this to benefit others struggling with the same behavior. i realize i didn't address the underlying problem.

the bitwise stuff happening in query() and readpacket() looks like gibberish to me. i'm sure it's all quite compact and sensible, but when i look at it, i'm just hearing the teacher from charlie brown. in order to log raw 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 device uses. i did try looking at the linux driver, but again, it's miss othmar all the way down.

thanks,

sl

      reply	other threads:[~2024-05-29 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-26  1:50 sl
2024-05-28  2:26 ` Stanley Lieber
2024-05-29  9:24   ` cinap_lenrek
2024-05-29 14:19     ` Stanley Lieber [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3BB4C362-D2BC-4406-A829-5C792A8BAB97@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).