61–68 of 68 posts
Earlier quoted context omitted.
But how does the leak change any of that?
Yeah, just gotta echo this. That was a whole lot of noise to really not make any point. Like - I even agree with most of what was typed, but I don't see it's relevance to anything here.
Earlier quoted context omitted.
Yeah, just gotta echo this. That was a whole lot of noise to really not make any point. Like - I even agree with most of what was typed, but I don't see it's relevance to anything here.
None at all, if you check their post history they've been going on about MMOs stealing code for a whole day on multiple threads. It's probably some novelty troll account.
Earlier quoted context omitted.
What about projects like WINE - now in use by corporations like Valve? Surely someone who's worked on the project must have seen Microsoft/Windows source code.
Wine explicitly disallows contributions from anyone who has seen Microsoft Windows source code: https://wiki.winehq.org/Developer_FAQ#Who_can.27t_contribute... Also, their Clean Room Guidelines: https://wiki.winehq.org/Clean_Room_Guidelines
Earlier quoted context omitted.
Replacing the firmware blob too is kinda the point of the driver. Now, if also the signing key were in the dump, people could finally sign their own firmware blobs. It's probably not legal to facilitate that in any way, but how can it be proven if you don't distribute any homegrown blobs? Edit: even if the Nvidia blob were used, it would (i) be a big departure from Mesa architecture and infrastructure and (ii) it wou…
> it would be illegal to distribute it Fortunately Nvidia provides all their drivers free of charge on their website, so it shouldn't be hard to download and extract it at install time?
Earlier quoted context omitted.
Wine explicitly disallows contributions from anyone who has seen Microsoft Windows source code: https://wiki.winehq.org/Developer_FAQ#Who_can.27t_contribute... Also, their Clean Room Guidelines: https://wiki.winehq.org/Clean_Room_Guidelines
Sure but the WINE folk don’t really know either way if a contributor who contributes has seen it, unless they do some background checks or their email literally ends with @microsoft.com (even then they could be in another Microsoft team away from Windows)
Earlier quoted context omitted.
> it would be illegal to distribute it Fortunately Nvidia provides all their drivers free of charge on their website, so it shouldn't be hard to download and extract it at install time?
The other points still stand. And it's possible there is also a legal reason that prohibits taking apart the driver. In any case, it would defeat the purpose of having an open source driver.
Not really. Having a closed-source on-card firmware blob but linking it with an open source kernel-side driver would have so many benefits, first of all not needing to depend on NVIDIA to keep up with upstream changes and stuff breaking at every kernel, xorg or whatever upgrade.
Very exciting, I hope this will help open-source hardware-accelerated image upscaling. To get an idea of what image upscaling can do, check out this subreddit dedicated to artificially increasing the resolution of old video game assets to give them a new life: https://www.reddit.com/r/GameUpscale/ Here's eg some personal experiments with the game Baldur's Gate: https://www.reddit.com/r/baldursgate/comments/aemu8u/ups…
> Very exciting, I hope this will help open-source hardware-accelerated image upscaling. It is also a legal minefield. Nvidia is certainly going to look closely at whatever may contain the leaked code. They are unlikely to do much if you just copy their techniques (unless they are patented, you need to watch that out too), but on community projects, you have to make sure that none of your contributors copy the code i…
Earlier quoted context omitted.
The other points still stand. And it's possible there is also a legal reason that prohibits taking apart the driver. In any case, it would defeat the purpose of having an open source driver.
> In any case, it would defeat the purpose of having an open source driver. Not really. Having a closed-source on-card firmware blob but linking it with an open source kernel-side driver would have so many benefits, first of all not needing to depend on NVIDIA to keep up with upstream changes and stuff breaking at every kernel, xorg or whatever upgrade.