Jump in the discussion.

No email address required.

I think Nvidia would have years ago if they could. I think a lot of this stuff needs to be done as clean room (like nouveau) because so many people/companies have their fingers in the current driver code that makes it legally impossible to release it as GPL compatible :marseyshrug:

1337 h@X0rz doing something that isn’t just demanding ransom or doxxing no no word sayers is cool though.

Jump in the discussion.

No email address required.

I think Nvidia would have years ago if they could . I think a lot of this stuff needs to be done as clean room (like nouveau) because so many people/companies have their fingers in the current driver code that makes it legally impossible to release it as GPL compatible

yeah but like who cares lmao. You just know that someone is going to release their own drivers. They are going to run gitea over tor or something. there are already legally fishy drivers that work around nvidia's virtualization crap, and that's just on github.

1337 h@X0rz doing something that isn’t just demanding ransom or doxxing no no word sayers is cool though.

yeah they will go down in history for being so based. if they follow through, it will be bigger than everything else in the warez scene combined.

Jump in the discussion.

No email address required.

The whole point of having truly FOSS ~novideo~ nvidia drivers is so they can get into the kernel mainline. Kernel developers won't even look at code that's under the wrong license / illegally obtained to avoid poisoning the kernel's code. This source dump will also have limited usability unless very skilled people commit to fixing the drivers for every new GPU and game.

It's a terrible situation, but Nvidia has to do what AMD is currently doing and fully merge the current driver, of their own free will, while offering continued support. I don't think that will happen as I stated above.

Jump in the discussion.

No email address required.

you can just maintain it out-of-tree using modules, and you can distribute those modules to binary-only distributions using dkms.

I use all sorts of drivers that aren't in the mainline tree. It's no big deal. The whole point of it being FOSS is that it is portable, easy to document, and easy to understand.

It depends how extensive the leaks are. It might be that porting the drivers is just a matter of compiling the sources, or the linux sources may not be included and we have to reverse-engineer the verilog and other low-level crap

Jump in the discussion.

No email address required.

Who has the experience to work on linux device drivers who doesn't want to contribute to the linux kernel for the foreseeable future?

Out-of-tree modules aren't ideal by any means, the kernel changes fast and you don't get "free support" that mainline brings (i.e. someone changes a kernel API and sees your code in a grep). ZFS on Linux is widely used and was even bitten by a bug that wouldn't have happened if it was mainline (if it wasn't CDDLed a lot of things would be better, granted).

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.