-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
[Feature request]: Wildcard support in backlight path. #52
Comments
This sounds like a good idea, in fact we have this implemented for iio light sensor (exactly because of this reason), but you are right not for anything else. In the iio the way it is implemented is not using wildcard, but configuring parent folder (which is always static), and it is then a hardcoded logic of the app to enumerate child folders. We can try the same, or we can switch to wildcards in both places, whatever works best, as long as it's consistent 👍 |
Same issue here. How's the status? |
Nobody is working on it at the moment, if you'd like to try your hand at it, you are most welcome - reach out if you have any questions, here or in a PR 😉 |
Please describe your feature request
I have an amd cpu in my laptop and the path to the backlight device changes from boot to boot. The device changes names from "amdgpu_bl0" to "amdgpu_bl1" and so on. This makes it impossible to configure wluma as it cannot find the device after a reboot.
Therefore I think it would be nice to be able to use a wildcard in the path such as "amdgpu_bl*" and have wluma use the first directory that matches this but it does not seem to work/be implemented.
The text was updated successfully, but these errors were encountered: