Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not clear udev behavior #30

Open
Atterratio opened this issue Apr 19, 2016 · 0 comments
Open

Not clear udev behavior #30

Atterratio opened this issue Apr 19, 2016 · 0 comments

Comments

@Atterratio
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant