Originally posted by RealNC
View Post
Announcement
Collapse
No announcement yet.
Linux Developers Still Reject NVIDIA Using DMA-BUF
Collapse
X
-
The kernel allows closed source software to run on it. DMABUF, being an API that can be used externally, should be exported to be used by anyone, regardless of license. What's next? GPLing the mmap() interface and making it illegal to run non-GPL software under Linux? You seriously think that's a good thing?
This has nothing to do with licenses. This has to do with AMD and Intel trying to stay ahead of NVidia by abusing their position within the kernel developer community.
Comment
-
Originally posted by DaemonFC View PostAlso, the "taint" warning is there for a good reason. It lets the user know they are running the kernel in a configuration that is totally unsupportable by either the upstream kernel developers or by the distribution that the user is running.
Yeah, you get an Ubuntu every once in a while that claims they "support" proprietary broken crap drivers, but they really can't. Their ability to support it is the same as your ability to support it. They can *ask* the developer and *hope* that it gets fixed, some month, year, ever....
Comment
-
Originally posted by gamerk2 View Post2) The drivers for the H/W are going to be at a VERY low level, and will basically show how NVIDIA accomplished everything in its H/W. You think AMD/Intel would like to see that information? This is especially notable, since NVIDIA has a lot of specialized components on its cards to handle certain tasks (they've hinted at such over the years...)
Comment
-
Originally posted by phoronix View PostSo while many Linux desktop users are quick to bash NVIDIA over their lack of proper Optimus support, right now they are also being forced down by the Linux kernel developers not wanting to allow non-GPL drivers to use this unified buffer sharing infrastructure and reducing driver interoperability.
They may at least release docs.
Comment
-
Originally posted by gamerk2 View Post2) The drivers for the H/W are going to be at a VERY low level, and will basically show how NVIDIA accomplished everything in its H/W. You think AMD/Intel would like to see that information? This is especially notable, since NVIDIA has a lot of specialized components on its cards to handle certain tasks (they've hinted at such over the years...)
On the other hand, Nvidia does not stand to lose any vital hardware design information by providing source code and programming documentation. Intel already provides a voluminous quantity of source code and programming documentation, yet we do not see them having lost secrets because of it. Anyone who knows how hardware works will know that the exact circuit designs that implement a programming API cannot be obtained by looking at the programming API and if they are good then making a good copy based on the API is hard.Last edited by ryao; 11 October 2012, 01:11 PM.
Comment
-
Nvidia must release everything till the OGL3.3 under GPL, in a form of a unified_driver that is multilevel and can target various CPUs and various GPUs with LLVM and backends. Then they have to provide all the rest (OGL4+) with a closed extension package, that uses a specific path of the backend, made only for Nvidia GPUs. That extensions can be: extra compilers, extra programs for the synthesizer, extra FX, but not driver functionality like memory management, that should be open. I don't wont to refer to known security issue with Nvidia drivers, that the company didn't fix for 5 years. With that kind of unified_driver Nvidia can explore all the open source, and can use it for all operating systems.
Comment
-
Originally posted by XorEaxEax View PostBullshit, DRM exists to prevent end users from doing what they want, GPL exists to make sure end users can do whatever they want and have all that is necessary for them to do so. IIRC you work for Apple so I can see why this is so confusing for you.
Comment
-
Originally posted by gilboa View PostSorry, you are being *very* naive.
Here's a number of other reasons:
1. Your code includes licensed 3'rd party code that cannot be opened.
2. Your code includes patent-infringing code that will get you sued.
3. Your code is multi-platform (more on that later) and includes platform specific code that prevents it from being opened.
4. Your code is being used by clients and you're prohibited by contract from releasing your code.
On a personal note (Ignoring for a second that we've yet to hear the code owner's view on the matter), I believe the Linux devs are being right instead of being smart.
nVidia is actually trying to play nice - I believe this behavior should be encouraged instead of being ignored. (E.g. trying to reach a gentleman's agreement that DMA-BUF will be made EXPORT_SYMBOL in-exchange to some documentation or headers)
Nothing wrong with ASKING POLITELY, however, even if they did, it should STILL be declined. Closed drivers have no business interacting with open drivers.
Comment
Comment