fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

11K
active users

TIL: @tuxedocomputers released drivers for their machines under the , which makes it impossible for competitors and distros to ship them pre-compiled, as that license is incompatible with the 's only license.

They did this purposely, allegedly to "keep control of the upstream pacing" – and want to re-license the code while upstreaming.

github.com/tuxedocomputers/tux

gitlab.com/tuxedocomputers/dev

gitlab.com/tuxedocomputers/dev

gitlab.com/tuxedocomputers/dev

@fabyk @kernellogger @tuxedocomputers Maybe, I’ll admit this doesn’t seem like an issue: they relicense everything when upstreaming, so there’s no incompatibility, anyone can still grab the code and build the DKMS drivers package to add it to another distro (done in a COPR repo for Fedora, IIRC), and all the code of these drivers is open source.

Standard practice for stuff they wouldn’t be accepted as-is in the kernel?

@thelinuxEXP @fabyk @kernellogger @tuxedocomputers It is incompatible even for regular redistribution by everyone. And nobody can help them upstream the drivers because the code is effectively radioactive.

It's absolutely a terrible move and it should be fixed.

@thelinuxEXP

it's just a detail, but imagine how different the Linux world would look like if you for each machine where you install Arch/Debian/Fedora/… on would first have to hunt down a proper driver package from official or unofficial sources while praying on each kernel update that things do not fail because some API considered kernel-intenal changed and broke compilation with DKMS…

CC: @Conan_Kudo @fabyk @tuxedocomputers

Thorsten Leemhuis (acct. 1/4)

@thelinuxEXP

BTW, to get an impression how to hard this stuff is with DKMS and how it easily it can fail for users, just look here: gitlab.com/tuxedocomputers/dev

That's another reason why I would avoid using words like "Standard practice", as it gives the wrong impression to people that are not aware of these things. Not to mention that this license trick is hardly standard, as @Conan_Kudo already pointed out.

CC: @fabyk @tuxedocomputers

GitLabKeeping up with Fedora branches (#209) · Issues · TUXEDO Computers / Development / Packages / tuxedo-drivers · GitLabSince Fedora 41 released it would be good to have the tuxedo repos before-hand, at the very least during the beta phase. There are automations like...