On Mon, 27 Aug 2018 11:09:29 -0400
sean darcy <seandarcy2(a)gmail.com> wrote:
Yes, the driver loads and the touchpad works. This bug is about the
driver not working, not warnings spamming the log.
OK, I thought that the driver wasn't working and spamming, not working
I found this recent report on arch that seems to be the same problem,
different than the one referenced in the fedora bugzilla.
The device is returning a message that falls outside the check
parameters of the driver. I haven't looked at the code, but I think it
could be that a high order bit is being set by the device to return a
negative number for an error condition. If the comparison variables are
unsigned in the driver, that would make the message appear very large.
There is a bug for the spamming:
but nobody is paying any attention. That's why I asked on the list.
You could try the devel list, where more developers hang out, or the
kernel list. Or reassign the bug to the kernel where it might get
more attention, since this seems to be a kernel driver issue.
Was there a kernel where the touchpad worked and there was no spamming
of the log? A diff between the two drivers for the touchpad would
probably indicate the change to the driver that is causing this