From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] 9front vs wacom
Date: Thu, 20 Aug 2020 19:12:51 -0700 [thread overview]
Message-ID: <61A0E3C6D73EF324C74E79871E683073@eigenstate.org> (raw)
In-Reply-To: <65818FB8AA2C2C68DB4AAB9765FA5ADD@ewsd.inri.net>
> it's been quite a while since i tested the cte-640, so i tried
> it again to make sure it still works:
>
> http://plan9.stanleylieber.com/paint/img/20200820.png
>
> i've updated fqa3 to reflect the model numbers i was able to
> verify.
>
> sl
The CTL-480, on the other hand, will spew events when I turn
debugging on nusb/kb up, but doesn't actually emit any actions.
Looks like we're not doing the right thing with the HID desc.
I'm spread thin, not sure when I'll have time to look into it.
next parent reply other threads:[~2020-08-21 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65818FB8AA2C2C68DB4AAB9765FA5ADD@ewsd.inri.net>
2020-08-21 2:12 ` ori [this message]
[not found] <A1540A0A20FD3FD86417AAA7A294D708@ewsd.inri.net>
2020-08-21 1:29 ` Kurt H Maier
2020-08-21 1:35 ` sl
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=61A0E3C6D73EF324C74E79871E683073@eigenstate.org \
--to=ori@eigenstate.org \
--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).