You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When use steam like driver for controller, then udev events work normal. What I mean: if controller off and I start or close steam then "udevadm monitor" doesn't catch any event, if controller on and I start/close steam "udevadm monitor" catch events. If steam started and I turn on/off controler "udevadm monitor" catch events.
But with this driver "udevadm monitor" catch events on "start/stop" driver daemon, not on power on/off controller.
Why it's important?
I see in issues, that a man wrote a special daemon for checking the connection controller, to my opinion with the right behavior enough simple udev rules.
Sorry for bad english, I hope I was able to present the idea.
The text was updated successfully, but these errors were encountered:
When use steam like driver for controller, then udev events work normal. What I mean: if controller off and I start or close steam then "udevadm monitor" doesn't catch any event, if controller on and I start/close steam "udevadm monitor" catch events. If steam started and I turn on/off controler "udevadm monitor" catch events.
But with this driver "udevadm monitor" catch events on "start/stop" driver daemon, not on power on/off controller.
Why it's important?
I see in issues, that a man wrote a special daemon for checking the connection controller, to my opinion with the right behavior enough simple udev rules.
Sorry for bad english, I hope I was able to present the idea.
The text was updated successfully, but these errors were encountered: