Nicolas Saenz Julienne
Nicolas Saenz Julienne
Hi, had a quick look at the issue, since I can reproduce it with openSUSE tumbleweed and kernel v4.20-rc1. It seems that just after probing the device _fwupd_ is unbinding...
Well the issue was fixed in fwupd. We just have to wait for distros to pick up the changes. There is no need to patch xpad.
dnmodder, what distro are you using? Could you try to run this command with the controller **unplugged**? `sudo service fwupd stop ` And then connect the device. It should work.
I see, I think you should open a new issue then. As this one isn't really related.
We're trying to fix this issue in upstream Linux. Here's the explanation on what's happening: http://archive.lwn.net:8080/linux-kernel/CAOGqxeWzjn70A_gP4Eh_ZLW0H3KkE_wA7QzeGRqU1u7xtJr-+Q@mail.gmail.com/ There will hopefully be a fix available soon.
Fair enough, should I close the issue or you're OK if I keep it open as a reminder?
Hi @lategoodbye! As far as raspberrypi-ts.c is concerned you can't do much to fix this issue. The firmware mandates the polling rate and that's the faster it'll ever be. IIRC...
> Note: currently this doesn't seem to boot Hi @lategoodbye, where you aware of this: https://github.com/raspberrypi/linux/issues/3032#issuecomment-507356208. It could be one of the reasons.
@lategoodbye Could you comment on what "58 GPIO support" implies. I can't seem to find anything related.
Here's a screenshot, left uses v1.0.2, right v1.0.3, I'm running vim in konsole (borderless) on a gnome/wayland system. The only thing that changed prior opening the second window is the...