-
-
Notifications
You must be signed in to change notification settings - Fork 42
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
Do you think this might be made to work with other machines using the ite8295? #170
Comments
True per key RGB or 4 zone? Because I can only try to do something for the latter while hoping the protocol used is independent of the manufacturer. |
True RGB per key, but it also has zones. I'm in a weird place with it because my machine uses open source firmware except for that controller - the EC and bios are open and I probably need to reverse some of the LED stuff and share it back with System76 to see if it can help at all. |
You could try and add your specific identifier to L5P-Keyboard-RGB/driver/src/lib.rs Line 14 in 7b19a1f
|
Thank you for the suggestion; I'll take a look and see if I can. Right now I'm using modified kernel drivers for another clevo ODM's machines and their control center to change them - it's universal and not per key, but at least lets me manage things at the worst case. |
I have a Sager/Clevo X370SNW-G also known by many other names. It has a ite8295 that controls the per key RGB. Under Linux I can currently manipulate these in /sys/class/leds but in Windows I have no way to manipulate them, the official software from clevo does not work because the laptop is a System76 branded variant, meaning it has coreboot and an open source EC firmware.
The text was updated successfully, but these errors were encountered: