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

Use udev properties for evdev classification #132

Open
ShadowApex opened this issue Jun 26, 2024 · 1 comment
Open

Use udev properties for evdev classification #132

ShadowApex opened this issue Jun 26, 2024 · 1 comment

Comments

@ShadowApex
Copy link
Contributor

Currently all evdev devices captured by InputPlumber assume that the device is gamepad-like when translating events. We should instead use udevadm info to look for device class identifiers to translate inputs based on their device class.

@pastaq
Copy link
Contributor

pastaq commented Jun 27, 2024

I think we should instead look into using udev-rs to find and init the source devices in the first place, then that value can be an inherent property. This will also allow us to resolve other issues such as #76 and #82, as we'll have access to those properties as well.

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

2 participants