Announcement

Collapse
No announcement yet.

Linux Developers Still Reject NVIDIA Using DMA-BUF

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #71
    Originally posted by droidhacker View Post
    How do we know and trust that the nvidia driver doesn't do something horribly dangerous?
    Yeah, that's the reason why DMABUF isn't getting non-GPL exported. Because of danger.

    I don't care if it's got security vulnerabilities. All software got those, regardless of license. There were more than enough root exploits in the Linux kernel itself over the years. If you care, then don't use it. Don't impose your security pedantry on me.

    Comment


    • #72
      Originally posted by RealNC View Post
      Yeah, that's the reason why DMABUF isn't getting non-GPL exported. Because of danger.

      I don't care if it's got security vulnerabilities. All software got those, regardless of license. There were more than enough root exploits in the Linux kernel itself over the years. If you care, then don't use it. Don't impose your security pedantry on me.

      Then use Windows and don't force your opinion to Linux developers. They may have different opinion.

      Comment


      • #73
        Originally posted by artivision View Post
        Then use Windows and don't force your opinion to Linux developers. They may have different opinion.
        Is this how we talk these days? "I have a different opinion, so don't talk to me"?
        I mean, he does have a point: If DMA-BUF is that dangerous it shouldn't be there in the first place. If DMA-BUF can be exploited it will be. But surely not from a company like Nvidia.

        Comment


        • #74
          Originally posted by Paradox Uncreated View Post
          Lol, well cry have a heartattack, do some cottaging and kill yourself I guess.
          Qaridarium? is it you? you are back? are you not banned life time?

          I found some funny quotes from you:



          V!NCENT: "maybe Qaridarium saying it, knowing you'd think about it, which resulting in mentioning it, making other people think about something the projectbleader said and finaly resulting in naking it happen... Casualty of nature "
          V!NCENT: "Qaridarium, do you believe in... time travel? "

          d2kx: "You better listen when Qaridarium announces"

          Welsh Dwarf: "Qs psychic abilities never cease to amaze me :P"

          Qaridarium: "Whats wrong with my dices? My cubes told me more than that can be."

          crazycheese:"Q, give me your dices please. Just one roll... "

          found here: http://phoronix.com/forums/showthrea...no-APU-Support

          Comment


          • #75
            Originally posted by RealNC View Post
            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?
            Oh please, enough with the strawman. This is the same as always, NVidia wants their proprietary drivers to be able to directly interact with the kernel subsystems to make life easier for them. Now they are using the possibility of optimus support as a carrot to try and leverage ways for them to do so.

            It's their typical BS, the reason Linux has such an incredible amount of hardware support out-of-the-box is because they haven't budged on this issue. One by one hardware companies have seen the advantages of this, or atleast have come to terms with the idea, except NVidia which still holds out. So let them, they will have to reimplement the necessary functionality for optimus support inside their proprietary driver if they want it under Linux.

            Meanwhile fully open source gpgpu solutions from the likes of Intel and to a lesser extent AMD is rendering NVidia obsolete on the desktop for all but those with extreme performance needs so it's not as if this is a problem we'll keep on having in the future.

            NVidia will continue to cater for Linux with their proprietary driver in sectors where Linux is huge or totally dominant like HPC and 3D/SFX while the end user desktop needs will be met by the aforementioned Intel and AMD gpgpu solutions.

            Originally posted by ryao View Post
            When will we be able to see optimus support on other operating systems like Illumos, Solaris, FreeBSD, Haiku, Darwin, etcetera?
            Good point, here are operating systems which allow proprietary drivers to interact directly with the kernel interface and yet the only chance they will see optimus support is if an open source reverse-engineered driver emerges, like Bumblebee. This again highlights the shortcomings of relying on proprietary drivers, it's simply another form of vendor lock-in.

            Originally posted by johnc View Post
            What, from a business perspective, does the Linux desktop bring to the table?
            Prior to the announcement of Steam on Linux, nothing for the likes of NVidia. Post-announcement (or pehaps rather post-release), I guess we'll have to wait and see.

            Comment


            • #76
              Originally posted by entropy View Post
              What do you think, can we expect a comment of Torvalds on that matter?

              Not sure what he would say. Isn't he more on the liberal side concerning the blobs?
              Hardly when it comes to driver blobs in the kernel, as for his overall thought on licences there was a very recent slashdot interview where he stated his position:

              Originally posted by linus
              So I'm a huge believer in the GPLv2, and I really do believe the license matters. And what - to me - is important for an open-source license is not whether you can fork (which the BSD's allow), but whether the license encourages merging things back.

              And btw, before people go all "license flamewar" on me, I would like to really emphasize the "to me" part. Licensing is a personal choice, and there is no "wrong" choice. For projects *I* care about, and that I started and can make the licensing decision for, I think the GPLv2 is the right thing to do for various reasons. But that does *not* mean that if somebody else makes another choice for his or her code, that wouldn't be the right choice for *that* person.

              For example, I'd use a BSD-like license for code that I simply didn't care about, and wanted to just "push out there in case somebody else wants to use it". And I don't think proprietary licenses are evil either. It's all fine, it's up to the original author to decide what direction you want to do in.

              Anyway, to just get back to the question - I really do think that encouraging merging is the most important part for a license for me. And having a license like the GPLv2 that basically *requires* everybody to have the right to merge back useful code is a great thing, and avoids the worry of forking.

              ...

              Comment


              • #77
                Originally posted by frantaylor View Post
                WHAT A JOKE!!!

                Your ethernet card has a PROCESSOR ON IT. It is running CLOSED SOURCE CODE. Your "open source" ethernet driver is talking to CLOSED SOURCE CODE. The part of that "closed source" code that talks to its bus controller is called a "driver".

                Your disk controller has a PROCESSOR ON IT. It is running CLOSED SOURCE CODE.

                Your sound card has a PROCESSOR ON IT. It is running CLOSED SOURCE CODE.

                ALL of the "open source" drivers on your linux system are interacting with CLOSED SOURCE DRIVERS and VICE VERSA.

                But SOMEHOW zealots can PUT THEIR HEAD IN THE SAND and PRETEND that their computers are "open".
                Modern Graphics cards pretty much are running their own OS on the card. Open hardware models aren't even competitive with the worst POS card you can buy new, But the GPL doesn't care about this. There is no linking, no merging of program memory between the two.

                From a practical standpoint having the black boxes separated (and generally tuned to provides a standard documented interface) make is easier to know/predict/sanitize inputs and outputs. When you drop three black boxes in the middle of the kernel capable of modifying 20-30 memory address within the kernel space without any apparent scheme, then you've got a problem orders of magnitude more complex.

                Comment


                • #78
                  Nvidia is infringing.

                  Per the xorg-devel list and irc, they've been testing their blob with dma-buf internally.

                  Comment


                  • #79
                    Originally posted by LLStarks View Post
                    Nvidia is infringing.

                    Per the xorg-devel list and irc, they've been testing their blob with dma-buf internally.
                    GPL only kicks in when distributing.

                    Comment


                    • #80
                      Originally posted by LLStarks View Post
                      Nvidia is infringing.

                      Per the xorg-devel list and irc, they've been testing their blob with dma-buf internally.
                      That's not infringing.

                      Comment

                      Working...
                      X