Skip to content
This repository has been archived by the owner on Nov 15, 2024. It is now read-only.

[Docs request]: clarify usage of different AUR packages in README #142

Closed
webketje opened this issue Nov 12, 2022 · 3 comments
Closed

[Docs request]: clarify usage of different AUR packages in README #142

webketje opened this issue Nov 12, 2022 · 3 comments

Comments

@webketje
Copy link

webketje commented Nov 12, 2022

As the developer of tuxedo-backlight-control I would really appreciate a section in the README mentioning a matrix of support per AUR package x models x configurations per model.

I originally developed the GUI for https://aur.archlinux.org/packages/tuxedo-keyboard but I see this package has been flagged as out-of-date recently (however it still works a charm on my Clevo N150-ZU)? Will it still receive updates/ be recommended for older models or Linux kernels?

Now there is also https://aur.archlinux.org/packages/tuxedo-keyboard-dkms and https://aur.archlinux.org/packages/tuxedo-keyboard-ite and https://aur.archlinux.org/packages/tuxedo-keyboard-ite-dkms

A lot of users are reporting issues that turn out to be missing SysFS installations, see a.o. webketje/tuxedo-backlight-control#23. I'm often at a loss to help out these users as I do provide an Arch Linux distro but do not have such an OS at my disposal for testing. It seems in this case the laptop model (Stellaris) uses a different interface (uniwill) than the one I created tuxedo-backlight-control for (clevo), and this interface does not work in the same way, specifically regarding SysFs

@StevenSeifried
Copy link
Contributor

Regarding the tuxedo-keyboard AUR packages, since I'm the maintainer of those:
To avoid deletion for (potential) violating the naming guidelines, I renamed both packages (see pinned comment on AUR page of tuxedo-keyboard-dkms)

@webketje
Copy link
Author

Thx for the input @StevenSeifried, so basically I should change the depends for tuxedo-backlight-control to tuxedo-keyboard-dkms instead of tuxedo-keyboard.

Still I noticed the SysFS integration in clevo_keyboard.h at line 633 is different from the one in uniwill_keyboard.h at line 626. The former outputs params to files at /sys/devices/platform/tuxedo_keyboard/<param>, while the latter seems not to do so.. Or am I misreading this and does the difference stem from AUR pkg format vs buiding from source?

@tuxedo-bot
Copy link
Contributor

This repository will no longer get any updates as the code here is now part of tuxedo-drivers https://gitlab.com/tuxedocomputers/development/packages/tuxedo-drivers.

Please open a merge request or issue in the new project on GitLab if you contribution or bug report still applies.

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

No branches or pull requests

3 participants