6 ms·
Sadly, it's also not the actual GPU driver, just the kernel part; you still need their massive closed blob in userspace. Almost had me excited there for a momen
by mort96 5y ago
Sadly, it's also not the actual GPU driver, just the kernel part; you still need their massive closed blob in userspace. Almost had me excited there for a moment.
- erung88 5y agoIt takes time for Nvidia to become open-source friendly. Still a good move. Hopefully the GPU driver is next in their open-source roadmap.
- greggsy 5y agoHas any rationale been provided around the blob being closed? Is it licensed, or simply too too complicated to pick apart? Graphics is a complicated field, but the techniques could still be patented - surely their market status isn’t dependent on trade secrets?
- shmerl 5y agoMy guess - tangled code mess without clear control over ownership and bean counters not approving the work of untangling all that to open things up - it's not an easy process for huge legacy codebase.
- prash_ant 5y agoThere have been reports earlier [1] that processing power of some GPUs is suppressed by software rather than the hardware capability itself. It is frequently easier to mass produce similar chips than to have different chips for different priced devices. I had come across comments in other online forums where the users alleged that some software flags restrict the capability. I hope someone else will link those webpages if they come across them [1] https://www.tomshardware.com/news/nvidia-gpu-system-processor-introduction https://www.tomshardware.com/news/nvidia-gpu-system-processo...
- hyperionplays 5y agothis was the case with RTX voice, a simple regedit made it work on non-RTX cards fine.
- cvuls 5y agoFrom my understanding, it used CPU acceleration instead
- IntelMiner 5y agoIt would use RT cores by default, but if they weren't available or in use (EG: running a game with Ray Tracing) it could fall back to the older CUDA That's also why they split it out into two products now "Nvidia Broadcast" is their "you bought an RTX GPU so here's a shiny toy" And "RTX Voice" for people with GPU's dating back to the Geforce 400 series that only does it via CUDA
- imtringued 5y agoThey can move those restrictions into firmware otherwise someone is going to develop a tool that unlocks the driver like people did for the Intel compiler.
- azeirah 5y agoI suppose this is also used for yield quality? For instance, AMD is known to sell the same actually-8-core chip as a 6-core if the transistor yield was poorer. I believe this is a standard in the industry, right? You can theoretically unlock these cores yourself, but there's a decent chance it will break or cause other significant problems.
- nimish 5y agoIt's pretty common to license peripheral bits of an ASIC from other companies. You don't even get to look at their blobs or much else.
- native_samples 5y agoYes. Drivers represent enormous amounts of work and large parts of the overall development/IP effort in a GPU. Asking why nVidia don't open source it is like asking why they don't just open source the entire GPU. Answer: because then they'd have a much smaller and less valuable business, if they even had a business at all.
- account42 5y ago> because then they'd have a much smaller and less valuable business, if they even had a business at all. This does not follow. While GPU drivers are a huge development effort, they are also very specific to the hardware. This is even more true with modern APIs that are closer to how the hardware works. AMD and Intel both have open source GPU drivers and they are still in business. Are you claiming that their business would be much bigger if not for those open source drivers?
- Qwertious 5y ago>AMD and Intel both have open source GPU drivers and they are still in business. Are you claiming that their business would be much bigger if not for those open source drivers? AMD and Intel are underdogs, and benefit from open standards. Nvidia has an outright majority, and as a result their incompatible "standards" benefit them, because it forces everyone to choose between supporting Nvidia (and therefore the majority of their userbase), or "open standards" (a minority).
- native_samples 5y agoApparently nVidia believe that is the case, and they are the market leaders, so - yes?
- shmerl 5y agoI expect once Nouveau will have reclocking ironed out, there will be an effort to implement Vulkan on top of it in Mesa. OpenGL is already available. That will allow avoiding Nvidia blob except for the firmware.
- eek2121 5y agoI came here to say that. This isn't an NVIDIA commitment to open source; it is a slap in the face. Rather than open sourcing the drivers, they are patching the kernel to fit the needs of their proprietary driver. Note that I'm not against proprietary software, however, title of this post was super misleading and NVIDIA needs to grow up and work on an open-source driver. The world will NOT change for them.
- kaladin-jasnah 5y agohttps://www.collabora.com/news-and-blog/blog/2022/03/23/how-to-write-vulkan-driver-in-2022/ https://www.collabora.com/news-and-blog/blog/2022/03/23/how-... What is this effort?
- lstamour 5y agoIt’s not actually a driver. Note comments like “Initialize driver-specific stuff” in the code. Mesa refers to https://docs.mesa3d.org/systems.html https://docs.mesa3d.org/systems.html and Vulkan refers to https://en.m.wikipedia.org/wiki/Vulkan https://en.m.wikipedia.org/wiki/Vulkan To quote the linked blog post: > This blog post will be a tutorial of sorts (we won't have a functioning Vulkan driver in the end, sorry) > First off, every driver needs a name. We're not actually writing one here but it'll make the examples easier if we pretend we are. Just for the sake of example, I'm going to pick on NVIDIA because... Why not? Such a driver is clearly missing and really should happen soon. (Hint! Hint!) We're going to call this hypothetical new Vulkan driver NVK. That said… NVIDIA did release a Vulkan driver in January 2022 which supports Vulkan 1.3 so… this blog post is slightly outdated. But it certainly does not include or reference work on an actual NVIDIA driver.
- ColonelPhantom 5y agoThe blog post is about writing a Vulkan driver inside Mesa. Nvidia's blob driver does not count here.
- IshKebab 5y agoThe world doesn't need to change for them. They already have successful closed source drivers. You're right that this isn't about nVidia suddenly deciding to open source anything, but it's still good for compatibility reasons.
- parasense 5y agoThat's a bit of a tired and somewhat misleading argument. Take a look into the kernel-firmware repo, and you will see a tremendous amount of binary firmware blobs. For example the Intel micro-code blobs are protected by ~7 layers deep of encryption, wifi drivers may have government regulatory issues with sharing firmwares in anything but binary form. So let's please drop the evil binary blob nonesense... The kernel does in fact accept small or large binary blobs, and some of them even come with source code...So I guess the key takeaway is to look at what separate the Nvidia driver/firmware from all those other binary firmware loading drivers. Hint, it has more to do with hiding the program interface, and using abstractions within abstractions.
- hda2 5y agoThis small tirade of yours is arguing against a strawman. GP is likely referring to the userspace component of nvidia's driver, not the actual blob that gets loaded onto the gpu. If it is indeed true that you need to run proprietary userland code, then this open-source release is nothing but a way to circumvent the GPL issues that lead to nvidia's driver partially breaking in Linux 5.??. While not ideal, I like many don't have a hard stance against loading proprietary hardware firmware blobs. I, however, absolutely take issue with running opaque user-space programs.
- pjmlp 5y agoInteresting, so they can do whatever they want, provided it runs as firmware.
- chme 5y agoI think this firmwareblob vs. kernelblob vs. userspace blob needs to be decided on a case by case basis, and no strict line that shall not be crossed can be drawn anywhere. The important factor is, does their contribution help the community or not, will it allow the community to fix bugs and port stuff to a new innovative kernel, without it needing to re-implement everything from Linux? Personally I would try to decide on blob size and scope. With nvidias driver I suspect that require massive firmware and userspace blobs, and the kernel driver is probably just a pass-through API. I would argue that this doesn't really move the community forward. However if the blobs are small and simple, and have specific scope and a reason, like legislation or security, maybe even calibration data blobs, are useful independent of the OS itself, then I would give them a pass, since it allows the community to build upon.
- adrian_b 5y agoWhile this is not as good as an open-source GPU driver, it is nonetheless a significant progress, which cannot be dismissed as useless. It is far more important to have open sources for all programs that are executed in privileged mode than to have the source for the programs that are executed in user mode. The kernel can control what a user-mode program does and limit its access to any hardware resources or CPU time, but it cannot do anything against kernel modules that are executed in privileged mode. So having the source for all the kernel modules is the main priority. With this new open-source kernel module from NVIDIA, the only closed-source kernel module used by a large number of Linux users is no longer so. Now the main problems remain the BIOS/UEFI of the computers, which is free to override what the operating system does, due to the exceedingly stupid System Management Mode invented by Intel, and the firmware for the auxiliary CPUs that may be used for unauthorized remote management in most Intel- and AMD-based computers.
- microtonal 5y agoPlus, I assume that this would make it possible for distributions to provide signed modules, making it much easier to use secure boot on systems with NVIDIA drivers (before you had to sign the drivers yourself after building them).
- gpderetta 5y agoIt is not, but I think it removes a giant blocker for a truly OSS driver with Mesa/nouveau.
- PaulHoule 5y ago... and like any new software from NVIDIA it only supports the most recent generation of cards. In normal times that might be a fair way to get people to upgrade but in the last few years (when crypto bros and scalpers have gotten all the cards) it's been outright cruel.
- TomVDB 5y agoTuring is not the most recent generation of cards. But that aside, Turing is their first generation that a GPU System Processor (GSP) that runs the heavy binary blob that comes with the open source driver.