Slashdot Mirror


Alan Cox to NVIDIA: You Can't Use DMA-BUF

DMA-BUF is a recent kernel feature that allows multiple GPUs to quickly copy data into each others' framebuffers. A use case would be the NVIDIA Optimus that pairs a fast GPU with an Intel integrated GPU, where the NVIDIA GPU writes into the Intel framebuffer when it is active. But, NVIDIA won't be able to use this infrastructure because it's GPL. Alan Cox replied on LKML to a request from one of their engineers to mark the API non-GPL: "NAK. This needs at the very least the approval of all rights holders for the files concerned and all code exposed by this change. Also I'd note if you are trying to do this for the purpose of combining it with proprietary code then you are still in my view as a (and the view of many other) rights holder to the kernel likely to be in breach of the GPL requirements for a derivative work. You may consider that formal notification of my viewpoint. Your corporate legal team can explain to you why the fact you are now aware of my view is important to them." The rest of the thread is worth a read (a guy from RedHat agrees that this code is GPL and cannot become non-GPL without relicensing from a major subset of graphics system contributors). This has a ripple effect: it means that all of the ARM SoC GPU drivers can't use it either, and it may prevent any proprietary drivers for the proposed DRI version 3.

22 of 946 comments (clear)

  1. Re:So? by Anonymous Coward · · Score: 5, Insightful

    And this is why graphics support will always be a third class citizen on linux.
    Congratz!

  2. One more bullet on proprietary drivers by Pope+Raymond+Lama · · Score: 5, Insightful

    They woul dhave a bad time coming along anyway, since they can't be compatible with the secure boot (UEFI) way of working (workaround if one prefers), that is being adopted by major distributions: all Kernel level code, and X11 code, will have to be signed to work out of the box in a UEFI restricted boot environment. And any distro that would sign binary code coming from NVIDIA or whoever else would be mad.

    It may be we get some months across a new "no working 3d drivers" dark ages on the Linux desktop, but one way or the other, the time for proprietary drivers is past.

    --
    -><- no .sig is good sig.
  3. What Cox is saying... by AliasMarlowe · · Score: 5, Insightful

    Actually, he's telling them that they can use DMA-BUF in their video drivers. And so can anyone else, provided those drivers are released under GPL.

    --
    Those who can make you believe absurdities can make you commit atrocities. - Voltaire
    1. Re:What Cox is saying... by MtHuurne · · Score: 5, Insightful

      Intel releases their drivers as GPL, I don't see why NVIDIA couldn't do the same. They choose not to.

      Now, there might be sublicensed code in the driver that NVIDIA doesn't own, so maybe they cannot release it under GPL tomorrow, but it would be feasible as a long term project.

    2. Re:What Cox is saying... by TheRaven64 · · Score: 5, Insightful

      Intel did not release their drivers under the GPL. Intel implemented new drivers from scratch. Relicensing existing code is really hard for something like a graphics driver, which contains code licensed from third parties. Oh, and they're under an MIT license like the rest of X11 and the DRI infrastructure, not the GPL.

      --
      I am TheRaven on Soylent News
    3. Re:What Cox is saying... by jedidiah · · Score: 5, Insightful

      > rather than the usual GPL zealot approach of Plagiarism-then-shouting-innovation.

      In truth, that pretty much describes the entire industry and creative efforts in general.

      Bitching about "innovation" generally is a smokescreen to excuse abusive, anti-competitive, and monopolistic business practices.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    4. Re:What Cox is saying... by TFAFalcon · · Score: 5, Insightful

      Well DMA-BUF (what this article is about) seems to be pretty innovative. And it is covered by GPL.

  4. Re:And this is why by D.+Taylor · · Score: 5, Insightful

    No, they would have called this API from their proprietary binary blob drivers, not copied or modified the code implementing it.

  5. Re:And this is why by Serious+Callers+Only · · Score: 5, Insightful

    And if it leads hardware vendors to avoid writing sophisticated drivers for Linux (a far more likely outcome), what then?

    Why would nvidia want to deal with fanatics like this when they can just ignore them?

  6. Re:Face Reality: by amorsen · · Score: 5, Insightful

    Nvidia isn't going to GPL its drivers and it couldn't do so even if it wanted to.

    Of course Nvidia could GPL its drivers. That "they can't do it" been said ever since the first proprietary Nvidia Linux driver, and back then it was blamed on non-specified technology licensed from SGI. SGI then stated publicly that they had absolutely no problem with their technology ending up in a GPL'd Linux driver.

    It is just a pitiful excuse. Luckily, between "secure boot" and this, the excuse will not last much longer. Then it will be either GPL or nothing at all.

    --
    Finally! A year of moderation! Ready for 2019?
  7. Re:Honest Question by Anonymous Coward · · Score: 5, Insightful

    I appreciate how you used the term "competitive edge" three times in such a short post. Oh, wait, no, I meant "I am nauseated by how". Don't they teach marketing shills anything in terms of subtlety any more?

    Anyway, you seem to be asserting that Nvidia's "competitive edge" is completely software-related. As in, the hardware — the actual graphics-computing stuff they sell, mind you — is somehow less important than the exact underpinnings of the drivers. This is an assertion that makes no sense to kernel developers. The drivers are just there to provide a way for the OS to communicate with the hardware. The hardware is supposed to be the magical part here.

    In my opinion, the ridiculously secretive nature of Nvidia, especially in the face of their major competitors opening up their drivers, is highly suspicious. After all, I thought they sold video cards, not drivers. It makes me think they're hiding Bad Things(tm) in the drivers. Unlicensed IP, perhaps? Evidence that their "value" models of video cards are actually the "premium" cards with drivers that shut down certain features? Crappy code? Or maybe just a behind-the-times product manager?

  8. Re:And this is why by Anonymous Coward · · Score: 5, Insightful

    Okay, great, if the world was perfect you'd have a great day! Yay!

    But, what if this change means that nVidia and all ARM graphics drivers come up with their own non-GPL kernel API, it would probably not be compatible with DMA-BUF, and that means that the graphics drivers in the Linux kernel - both open source and not - would pick and choose which buffer sharing mechanism they support/use, leaving the rest out in the cold. This situation just so happens to negate the ENTIRE purpose DMA-BUF was created for, namely, to act as a SINGLE way for ALL drivers to share and pass buffers around. So, instead of creating a BETTER situation where all graphics drivers are compatible with each other (even the proprietary ones), we have a crappy situation that we've continued to have since day one - proprietary and open source graphics driver not playing nice with each other.

    It's even in your short term and long term best interests to get everybody to use DMA-BUF, because the faster that happens the easier it is to use Linux, the more people start to use Linux, and Linux users slowly start to become more and more relevant to driver manufacturers to the point that, like Mac users, they become a profitable segment of the computer using population (note that this is both for desktop users with nVidia cards, or short term uses, and all ARM drivers for embedded devices which are becoming more popular, or long term uses), and graphics developers start to support them as best they can (read: supporting open source driver development).

    While this is happening - in other words, while the world is ruled by proprietary graphics drivers because the open source ones suck (as is currently the case, and although it's improving is likely to continue to be the case for at least another two years), you can have your Left 4 Dead 2 on Linux with the proprietary nVidia driver that it needs, you can have lower power usage on all Linux laptops because Intel and nVidia cards can share buffers and therefore change which card is actively processing depending on what is running, and you can actually have useful drivers for all embedded devices until open source graphics drivers are available (whenever that happens, as it is barely on the radar of developers at this point).

    So, you (and Alan Cox) can be complete dicks about this and hold the Linux desktop and Linux embedded devices with decent drivers back for years because nobody bothers to support such a tiny market with open source drivers, or you can allow proprietary graphics card manufacturers to keep their hold on graphics drivers for a few years and keep the vast majority of users happy because they have a device that works well enough (even though it doesn't have open source graphics drivers) UNTIL the community develops open source drivers themselves.

    So, what's more important to you, possibly helping proprietary vendors temporarily and helping desktop and embedded users out tremendously for the next few years; or keeping your kernel untainted by proprietary crap, unhelpful to proprietary vendors, and keeping the kernel the same mess it has always been, and pissing off the vast majority of desktop and embedded users for years?

    I would argue that Valve is only porting Steam and their games to Linux because the nVidia graphics drivers exist (because their games require OpenGL 4+, which isn't supported, and will not be support for years, by open source drivers). And yet, them porting their AAA title games is going to tremendously help Linux break out of its insignificant shell on the desktop - which will drive adoption, drive demand for Linux, and ultimately drive the demand for open source drivers anyway.

    So, take a deep breath, calm down, and just accept the fact that allowing something to be temporarily imperfect in your world is a good trade off to make to have a much better world a few years from now.

    Furthermore, DRI3 (the userspace API) will become dependent on DMA-BUF once it is developed, which means that DMA-BUF will become a usersp

  9. Re:So? by Anonymous Coward · · Score: 5, Insightful

    Are you hating or just misinformed? NVIDIA ranks second in terms of total lines changed for the ARM kernel, and fourth in terms of number of changesets for all employers or organizations. That's sharing.

    The only thing they don't share is their graphics drivers - which seems like a fair trade overall. nVidia has licensed patented code which they couldn't share even if they wanted to.

    NVIDIA will likely just build their own DMA memcpy routine - because copying memory is SOOO unique.

    Full disclosure: I develop (unrelated) proprietary kernel modules, I'm very familiar with the licensing, patent and copyright issues and we work within the GPL limits defined by the kernel team.

  10. Re:This is why I suggest BSD by oPless · · Score: 5, Insightful

    PSST, this is an API called marked in such a way that only GPL modules are allowed to call it.

    It's a deliberate act of douchbaggery by kernel developers to force manufacturers to open source their drivers, not to steal code from the kernel.

  11. Re:So? by peppepz · · Score: 5, Insightful

    No, this is why linux exists in the first place.

  12. Re:Honest Question by Yvanhoe · · Score: 5, Insightful

    Well, we do want an open source system, for a variety of legitimate reasons. NVIDIA's edge is in hardware design, not software design. I, for one, would be happy that they provided an open source driver that give me access to all the 1 year old functionalities of their cards. That would not make them lose any edge.

    Also, a thing that NVIDIA probably fails to realize is that open sourcing their drivers will result in far more developers on it, therefore will probably raise their quality.

    I honestly doubt that ATI could get an edge from looking at the code of NVIDIA's drivers. Maybe some small marginal improvement but nothing that would improve their hardware.

    I think that this argument has been mainly FUD. Linux developers are a small population but they are opinion leaders in the market. The first company that goes open source will probably receive a popularity boost that will offset the little "edge" that they fear losing. Right now, this is Intel, despite very inferior hardwares, that is becoming more popular because of their 100% open source drivers.

    --
    The Wise adapts himself to the world. The Fool adapts the world to himself. Therefore, all progress depends on the Fool.
  13. Re:It would still become a derived work of the ker by MickyTheIdiot · · Score: 5, Insightful

    Please don't echo the Microsoft buffoonery of calling the GPL "viral".

    If it's viral it's a virus you choose to contract.

  14. you got your backwards backwards by IBitOBear · · Score: 5, Insightful

    Linux developers are not trying to "force" anybody to do anything. Nvidia is trying to force the linux community to accept their unacceptable "super secret" blob into the kernel agains the linux community's development and participatation standards.

    If I showed up on your doorstep and said "you have to let me use your bathroom and your kitchen, but I am not going to wash my hands or put on pants" you would not be "forcing" me to (anything) by saying that my intended pantless, unwashed use of your facilities was unacceptable.

    The Linux community is telling nvidia "we use soap and pants here, if you won't do likewise, we don't feel like accomodating you."

    Nvidia _knows_ they want in, otherwise they wouldent be trying to get in, Linux Don't Care if they come or not, but if they come they need pants...

    Requiring someone to meet minimum standards for participation is not "forcing them" to do anything,

    No pants, no access is not an unreasonable position.

    --
    Innocent people shouldn't be forced to pay for inferior software development.
    --"Code Complete" Microsoft Press
  15. Hmmm by AdmV0rl0n · · Score: 5, Insightful

    I've never really understood so much of the background on this. I really don't. Nvidia are probably *the only* fucking company that really went the whole way and really release the right 'kind of ' full drivers for Linux. Yes, they are closed source binary. Yes, they are proprietry. Yes, they don't comply with religious level political idealogy. But they contribute in a less than optimal way to your platform.

    And your platform, at least in the short and medium term would be vastly shittier without their efforts.

    So, next you publicly go viral dropping a bucket of shit over them. Their response has been moderatly to try to come in and talk, make changes and be more of a interactive unit with you. I bet that the devs inside the company are probably very pro making progress but face real world limits of legal and other things that they themselves are not empowered to fundamentally change.

    I'm not surprised at Alan's answer - but here is my raw take on this. What would have been the better way forward was to take their request and frame it globally to that group of people and put Nvidia's request forward. I appreciate that many would likely answer no, and I appreciate this would perhaps not be what Nvidia wanted, but it would have opened a bridge for interaction and perhaps longer term bridge building. Instead, they get a fuck you, fuck your company, and do this our way or the highway.; What were Nvidia trying to do? Provide an answer to the problem they had a bucket of shit thrown over them in public about. ie - trying to solve a problem they were abused about.

    The benefit of doing this is fixing something in linux - albeit with a closed driver that people asked for. Linux users asked for this. Linux Kernal people bitched about it. Linux coders refusing to help provide this moves this off being a purely Nvidia are a bunch of fucks to shooting your own platform in both feet.

    I don't fucking get it. These bits of code I presume are already fully in Linux. Sat there in daylight .Refusing to let Nvidia use them to help you do something_you_asked for is demented. Or rather - let me reframe that - Its really lame to not engage in a process to find a way forward instead of ramming the ideology down the throat of a vendor who is a closed source bunch - but have come to try and engage with you on a problem.

    Let me put it more plainly. Linux needs Nvidia more than Nvidia needs linux - but together you make something that is symbiotic. You think your mythical Ubuintu tablets are going to surface on the very proprietry ARM platform by not getting down and working with people like Nvidia on problems. Linux won't run 'well' on their platform without their help. You want to be there? Take your heads out of your asses.

    As much as Linux gets hobbled by closed source folks not playing the game, its just as hobbled by killing off their interactions and opportunities by being too hard headed about the religio-political idealogy.

    And a fucking note to the Intel GPU Linux fanboys. The drivers have almost always been shit. And the hardware is low end garbage. I'll take a Linux box with Nvidia GPU *EVERY fucking time over intel gfx. Every time.

    --
    We`re all equal .. Just some of us are less equal than others.
  16. Re:Why is this supposed to be a good thing? by Svartalf · · Score: 5, Insightful

    No, it's not.

    You and everyone KEEP presuming the only space at stake here. There's another and they want to play in this space badly because it's big-bucks for them or they wouldn't have done it in the first place. (Hint: There was no good reason for the Linux drivers they've made to date- because there really wasn't a market for those end-user drivers (these are treated as such by the community, but they're not really for the consumer market...) until recently in the first place.

    Think engineering workstations (early reasons...seriously, for both AMD and NVidia...) and supercomputing clusters using GPGPU computation (There's a reason for the opening of AMD's stuff...that's part of that.).

    If they want to play in that space...they're going to have to change attitudes, much like AMD did.

    --
    I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  17. A good step in the right direction by jcdr · · Score: 5, Insightful

    The GPU is no anymore a peripheral device, it's more and more integrated on the same die as the CPU. Intel, AMD or ARM have plans to lowering the difference even more on how GPU and CPU will exchange data and will view the rest of the system. Basically, the CPU cores and GPU cores will share the same location into the architecture. This move is not so different from the integration of the FPU core into the CPU that have existed back to the 80486/68040 days. About ten years before the FPU integration, the FPU chips was a lucrative business: this part was so expensive that it was an option that only a few can buy. Not anymore, FPU less CPU are now only found in the lower part of the ARM embedded market. There is no x86_64 chip without FPU by the design of the instruction set. GPU is the next core to get the same integration.

    What this means ?

    First, since Nvidia don't own a licence to build x86_64 chip, the game is actually already over for them. There known that since the failed merge talk with AMD and explain why there focus on the high end and ARM chips since this time. This also explain why Linus Torvalds "fuck you Nvidia" response was focused on the Tegra ARM SoC despite the fact that the original question was about a x86_64 laptop.

    Secondly, Intel and AMD known that sooner or later, the GPU core will be so integrated with the CPU core that there cannot be managed anymore by only a driver to do in a efficient way there new roles aside of the graphic display. The trigger point will probably be when the GPU will passe on the CPU side of the MMU (or something that look like this). At this stage the paging management for the GPU will be almost impracticable from within a driver to cooperate efficiently with the core operating system, not counting the brainfuck crap in case there are not developed by closely related peoples. This don't automatically say that GPU driver will cease to exist for some graphic aspect, but the GPUCPU part will end up into the kernel for the most critical aspects. It's easy to see why on Linux, access to the GPU from a proprietary driver is really not an option for the future (even if the current issue is only about DMA sharing data between devices).

  18. Re:Honest Question by dudpixel · · Score: 5, Insightful

    I disagree. AMD has had open source drivers (and specs) for years now, and the quality is still terrible. Intel has open source drivers and I still wouldn't choose Intel graphics for anything serious.

    Sure, if all you want is a picture on your screen, then even the nouveau driver will get you there. But if you want fast graphics, like you get on windows, then this licensing crap is just another way of ensuring it won't come to linux.

    If NVIDIA started only offering its binary driver on BSD, windows and OSX, I think it's more likely that Linux users (particularly commercial ones) would switch to another OS, than switch to another graphics card manufacturer.

    If the quality of the other drivers/hardware was better, then that might not be the case, but AFAIC(oncerned) AMD's drivers are a bit flaky (even on windows) and intel's hardware has yet to come near the performance of AMD/NVIDIA.

    --
    This seemed like a reasonable sig at the time.