Earlier quoted context omitted.
The first link does not mention blacklisting, just resolving a license compatibility issue.
"The patches check for the gxtp7380, ite_8291, ite_8291_lb, ite_8297, ite_829x, stk8321, tuxedo_compatibility_check, tuxedo_io, tuxedo_nb02_nvidia_power_ctrl, tuxedo_nb04_keyboard, tuxedo_nb04_wmi_ab, tuxedo_nb04_wmi_bs, tuxedo_nb04_sensors, tuxedo_nb04_power_profiles, tuxedo_nb04_kbd_backlight, tuxedo_nb05_keyboard, tuxedo_nb05_kbd_backlight, tuxedo_nb05_power_profiles, tuxedo_nb05_ec, tuxedo_nb05_sensors, tuxedo_nb…
> ite_829x
Huh, so Tuxedo developed their own ITE 829x kernel driver.
I have a Clevo based laptop, similar to the ones they sell. Years ago I reverse engineered the keyboard's features and wrote a user space driver.
https://github.com/matheusmoreira/ite-829x
I interacted with Tuxedo quite a few times back then while I was figuring this stuff out. They even sent me source code for a pre-release version of their Electron app. It didn't help much in the end but they proved to be much nicer and more responsive than other manufacturers and even Clevo itself.
Wish they'd emailed me about their driver. I could have helped develop it, especially if they had given me documentation.
I briefly explored the idea of turning it into a kernel module and contributing it to the kernel. While reading Linux driver source code, some comments gave me the impression they'd prefer code remained in user space if possible. Since I already had a working user space driver, I decided not to contribute it.
I wrote the above program because Clevo's app was Windows only and so aggravating to use it defies description. Looks like Tuxedo ran into the same problem with their Electron app, if the complaints in this thread are any indication... Déjà vu.