3 ms·
I think posting about this problem is quite a reasonable approach. Several kernel maintainers seem to have already noticed this, and gregkh provided instruction
by jeroenhd 3y ago
I think posting about this problem is quite a reasonable approach. Several kernel maintainers seem to have already noticed this, and gregkh provided instructions on how to potentially resolve such an issue (send an email to the maintainer and the appropriate mailing list).
"Just recompile your kernel" is how Linux people convince other Linux users to install Windows or buy a Mac.
- Galanwe 3y ago> "Just recompile your kernel" is how Linux people convince other Linux users to install Windows or buy a Mac. Well I'm not really proposing he does it, I'm just saying he should ask for someone to help him do it. If I understand the post well, his workflow was relying on a bug in his pen driver. That bug got fixed. It's just the way things move forward, it happens on Linux, Windows, or any software really. The sane solution is just to rebuild the old driver (not kernel).
- andrybak 3y ago> email to the maintainer and the appropriate mailing list David Revoy has reached out to the linux-input mailing list: https://lore.kernel.org/linux-input/877c9bed-181a-4fc0-a876-e17de65c9e4d@leemhuis.info/T/#m1dce44d59055894865330fc78b2ac47872e5d658 https://lore.kernel.org/linux-input/877c9bed-181a-4fc0-a876-...