Announcement

Collapse
No announcement yet.

NVIDIA Tries To Put Fence Sync Into X Server 1.10

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

  • #16
    I think with APIs that lock out closed-source drivers people in general mean DRM and/or KMS stuff.

    Comment


    • #17
      Originally posted by brent View Post
      I think with APIs that lock out closed-source drivers people in general mean DRM and/or KMS stuff.
      Care to share some examples?
      (Beyond the symbol management API's that are GPL-only for obvious reason - they can be used to let a non-GPL modules force-load GPL-only symbols)

      - Gilboa
      DEV: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB + 2x3TB, GTX780, F21/x86_64, Dell U2711.
      SRV: Intel S5520SC, 2xX5680, 36GB, 4x2TB, GTX550, F21/x86_64, Dell U2412..
      BACK: Tyan Tempest i5400XT, 2xE5335, 8GB, 3x1.5TB, 9800GTX, F21/x86-64.
      LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F21/x86_64.

      Comment


      • #18
        Originally posted by deanjo View Post
        Politics over practicality, developers wants over end user wants. Why do they have to fight them, they don't, but they choose to because nvidias offering is unpure to them.
        the better way is just Ignor nvidia in any kind of ways

        Comment


        • #19
          Originally posted by Qaridarium View Post
          the better way is just Ignor nvidia in any kind of ways
          No, a "better way" is to work together regardless of personal opinion, politics, and ideologies for the greater good of the end user whom more then likely don't care about how it is done but the end result is providing a product that does what the end user wants it to do.

          Comment


          • #20
            Originally posted by deanjo View Post
            No, a "better way" is to work together regardless of personal opinion, politics, and ideologies for the greater good of the end user whom more then likely don't care about how it is done but the end result is providing a product that does what the end user wants it to do.
            what is the basement of "work together" ?? there are just enemys the best they can do is ignore the others

            Comment


            • #21
              From: Dave Airlie
              "[...]This goes for nvidia type situations as well, the whole point is
              to place the maintainer burden at the feet of the people causing the
              problems in an effort to make them change."
              Here is the whole thing: http://kerneltrap.org/mailarchive/li...4589722/thread

              Maybe "not being nice" was the wrong expression, it's more of a not giving a sh*t.

              Comment


              • #22
                The OSS people don't create APIs to be unusable for closed source drivers - they simply don't the burden of trying to maintain compatibility with closed source drivers for no reason other than to keep those drivers running. The kernel APIs should not be held hostage by some binary blob, and in practice there's not much effort in keeping the binary blobs working anyway.
                It's this way because the devs care about the sanity of kernel interfaces and don't want them bogged down in ancient cruft.

                Comment


                • #23
                  Originally posted by mirv View Post
                  The OSS people don't create APIs to be unusable for closed source drivers - they simply don't the burden of trying to maintain compatibility with closed source drivers for no reason other than to keep those drivers running. The kernel APIs should not be held hostage by some binary blob, and in practice there's not much effort in keeping the binary blobs working anyway.
                  It's this way because the devs care about the sanity of kernel interfaces and don't want them bogged down in ancient cruft.
                  Well you would like to think that was the way it worked but we have already seen in the past that Xorg, even though the patch would require virtually no maintenance at all (remember the 3 line patch nvidia submitted that simply gave priority to the blob if detected?). Also you can't say "don't want them bogged down in ancient cruft." as the kernel is full of ancient cruft.

                  Comment


                  • #24
                    Originally posted by Qaridarium View Post
                    what is the basement of "work together" ?? there are just enemys the best they can do is ignore the others
                    That is not the best they can do, the best they can do is to attempt to work together. The worst they can do is ignore each other.

                    Comment


                    • #25
                      Originally posted by deanjo View Post
                      No, a "better way" is to work together regardless of personal opinion, politics, and ideologies for the greater good of the end user whom more then likely don't care about how it is done but the end result is providing a product that does what the end user wants it to do.
                      You are confused. The end users of the kernel are its own developers, paid or unpaid. The paid ones work on the kernel for the benefit of their company. The unpaid ones work on it as a hobby.

                      Why should either category bend over to accept and *maintain* code for the benefit of a closed-source company that doesn't help in Linux development (e.g. Nvidia)?

                      Comment


                      • #26
                        Originally posted by BlackStar View Post
                        You are confused. The end users of the kernel are its own developers, paid or unpaid. The paid ones work on the kernel for the benefit of their company. The unpaid ones work on it as a hobby.

                        Why should either category bend over to accept and *maintain* code for the benefit of a closed-source company that doesn't help in Linux development (e.g. Nvidia)?
                        I'm not confused. There are a hell of a lot more end users that are not devs then there are devs. Whether you like to admit it or not, nvidia does help out in linux development. In fact I would go so far as to venture that without nvidias solutions being available you would not have seen so much progress being made on the linux desktop over the last 8 years simply for the fact of them offering a full featured working solution. Then there is also items such as nvidia's contribution to the open API's such as openGL, openCL, etc. To say that nvidia doesn't contribute to development is BS, it may not offer open documentation to it's products but to say that it doesn't contribute to open projects isn't the truth at all.

                        Comment


                        • #27
                          nvidia does what is best for nvidia. AMD does what is best for AMD. Intel does what is best for Intel. It's the same for any company. It's competition (in this case, usable drivers from both nvidia and amd) that have driven things forward.

                          Comment


                          • #28
                            Originally posted by deanjo View Post
                            I'm not confused. There are a hell of a lot more end users that are not devs then there are devs. Whether you like to admit it or not, nvidia does help out in linux development. In fact I would go so far as to venture that without nvidias solutions being available you would not have seen so much progress being made on the linux desktop over the last 8 years simply for the fact of them offering a full featured working solution. Then there is also items such as nvidia's contribution to the open API's such as openGL, openCL, etc. To say that nvidia doesn't contribute to development is BS, it may not offer open documentation to it's products but to say that it doesn't contribute to open projects isn't the truth at all.
                            Strawmen and more strawmen.

                            I said that Nvidia does not contribute to Linux (i.e. kernel) development. With that in mind, why should kernel developers be tasked with maintaining Nvidia's blob? What would e.g. Red Hat gain from that? Or independent contributors?

                            Like it or not, the kernel is not developed for you and me. It's developed by Red Hat, AMD, Intel, etc *for* Red Hat, AMD, Intel, etc. The fact that we can use this kernel on our desktop is awesome, but we are certainly not the primary target.

                            Comment


                            • #29
                              Originally posted by BlackStar View Post
                              With that in mind, why should kernel developers be tasked with maintaining Nvidia's blob? What would e.g. Red Hat gain from that? Or independent contributors?
                              Hey Redhat fixes bugs when they effect workstations with Maya on it. Why would they do that? Oh ya, probably because their customers use such applications.

                              Comment


                              • #30
                                Originally posted by deanjo View Post
                                Hey Redhat fixes bugs when they effect workstations with Maya on it. Why would they do that? Oh ya, probably because their customers use such applications.
                                Since when does Maya contain kernel modules?

                                Comment

                                Working...
                                X