Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Phoronix link about what this actually means:

https://www.phoronix.com/scan.php?page=article&item=nvidia-o...

Main takeaways:

- support for gaming workstation GPUs is alpha

- the user space stuff (OpenGL/Vulkan) is still closed source. (A LOT of heavy lifting is done here.)



Ok, we've changed to that from https://developer.nvidia.com/blog/nvidia-releases-open-sourc... above. Thanks!

Edit: ok, changed back


Uh why would you change from a good, official source to a worse rehash of the same stuff with less detail from Phoronix?

I don't even dislike Phoronix, but what was wrong with the first-party source?


User suggestions about better articles tend to be pretty reliable, so we tend to trust them. Sometimes they turn out not to be better (at least not by consensus)—in which case we can change the link back. I've done so in this case.

If you want to understand this process, you should understand that none of it involves actually reading the articles!


I would argue the Phonorix is the vastly superior link.

That blog is the most dedicated to the confluence of 3D, Linux, and open source.

The Nvidia copy is typical engineering marketing copy. The Phonorix post dives into everything with great detail and goes further by discussing the future of open source Nvidia support with the upcoming technologies, and existing technologies (Noveau, Mesa, etc)

Nvidia fanboys care little for Phonorix because that site consistently points out how unfriendly and uncooperative Nvidia has been with the whole of the Linux community. (Web search for yourself Nvidia EGLStreams GBM.)


Please change it back. Nvidia was the official source and Phoronix is low-quality blogspam of dubious accuracy.


> the user space stuff (OpenGL/Vulkan) is still closed source. (A LOT of heavy lifting is done here.)

Much like AMD - surely they benefit a lot from having a relatively stable non-kernel ABI they can target, though. The problem right now is that everything changes every time the kernel is updated, but if you turn it into a "here's how you dispatch PTX to the card" layer and a "here's how you turn OGL/Vulkan into PTX" blob then the dispatch layer probably isn't changing as much.

(graphics doesn't really use PTX but you get what I mean... dispatching compiled assembly and graphics API calls to the card.)

It doesn't help further the copyleft cause as much as if NVIDIA had open-sourced everything, of course, but from an end-user perspective of "I don't want my kernel updates to be tied to my driver release-cycle" it should solve almost all of the problem?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: