On Sun, 28 May 2023, Dave Tyson wrote:
I have a couple of devices which report a touch screen present, but
don't attach it correctly, failing with "touchscreen has no range
report"
Yeah, my laptop had the same issue and I worked around it by using
this gross hack (for 9.x, but, should apply to 10.x):
```
--- uts.c.orig 2019-05-05 03:17:54.000000000 +0000
+++ uts.c 2022-03-31 22:13:33.000000000 +0000
@@ -213,6 +213,10 @@
*/
aprint_debug_dev(sc->sc_hdev.sc_dev,
"ELAN touchscreen found, working around bug.\n");
+ } else if (uha->uiaa->uiaa_vendor == USB_VENDOR_ATMEL &&
+ uha->uiaa->uiaa_product == 0x8417) {
+ aprint_debug_dev(sc->sc_hdev.sc_dev,
+ "Atmel maXTouch Digitizer found, working around
bug.\n");
} else {
aprint_error_dev(sc->sc_hdev.sc_dev,
"touchscreen has no range report\n");
```
That got my touchscreen working with the `ws' Xorg driver. Pretty sure
this isn't the *right* way to do it, but, I didn't have the time to
wade through the USB specs. & NetBSD kernel docs. for the correct
solution. :)
HTH,
-RVP
PS. Happy to run commands/test patches/etc. if someone more
knowledgeable is willing to do a proper job of this.
