lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 16 May 2022 12:45:48 +0200 From: Stefan Berzl <stefanberzl@...il.com> To: José Expósito <jose.exposito89@...il.com> Cc: jikos@...nel.org, benjamin.tissoires@...hat.com, spbnick@...il.com, linux-input@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Status on hid xppen patch Yo José, >>> I had to introduce new functionalities to the templating system of the >>> driver, that's the reason for the KUnit tests. >>> The last patch is work in progress (hopefully I'll have time to finish >>> it this weekend), only the HID descriptors are missing. >> >> I hope you make it, but otherwise you can always use mine, as it's quite >> the same as yours. Only the logical minimum and maximum are -60 and 60. > > You are right, 60 and not 127 is the right value. Actually, I think > that -61 - 60 is the correct range, because of the 0. > Running "libinput-debug-tablet" makes it easier to debug. > > I also had to fix the descriptor to avoid an issue with the pressure > causing issues with the Deco L, but other than that, it should be > correct now. I don't think the two's complement thing has any bearing here, because there are still several numbers left in both directions. Also I couldn't get the mini 7 to produce tilt values either >60 or <-60, but I'm sure you'll get behind it. > Also, I don't know if you have seen this error after connecting the > tablet: > > xhci_hcd 0000:2a:00.3: WARN urb submitted to disabled ep > usb 3-2: reset full-speed USB device number 6 using xhci_hcd > usb 3-2: reset full-speed USB device number 6 using xhci_hcd > [...] > > It happens with the Deco Mini 4, even when using the hid-generic > driver. I need to rebase my patches on 5.19 and test again, just to > make sure the problem is not somewhere else. Can't say I have seen it. The only thing I can think of is that I was using the async urb functions and that delay did something about it. Kind regards Stefan Berzl
Powered by blists - more mailing lists