Announcement

Collapse
No announcement yet.

NVIDIA Contributes Re-Clocking Code To Nouveau For The GK20A

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

  • NVIDIA Contributes Re-Clocking Code To Nouveau For The GK20A

    Phoronix: NVIDIA Contributes Re-Clocking Code To Nouveau For The GK20A

    One of the biggest challenges with the Nouveau open-source graphics driver for NVIDIA graphics hardware in recent times has been with regard to GPU / video memory re-clocking. As a minor step forward, NVIDIA has contributed re-clocking patches for the GK20A graphics processor...

    http://www.phoronix.com/vr.php?view=MTczOTg

  • #2
    Not good enough.

    Originally posted by Linus
    FU nvidia

    Comment


    • #3
      Cry harder.

      Wah wah wah, look at all the big babies. This time next year, OpenGL 4 will exist in Nouveau with full reclocking support on current generation GPUs. Nvidia doesn't need to release anything at the moment because the development work is basically already being done. Releasing the GLX code won't make gallium3d state tracker support happen faster.

      Comment


      • #4
        Originally posted by DMJC View Post
        Wah wah wah, look at all the big babies. This time next year, OpenGL 4 will exist in Nouveau with full reclocking support on current generation GPUs. Nvidia doesn't need to release anything at the moment because the development work is basically already being done. Releasing the GLX code won't make gallium3d state tracker support happen faster.
        And it'll still be far slower and take much longer to be implemented on Nouveau then the AMD OSS drivers because the Nouveau team has no help at all from Nvidia for the vast majority of their products, they have to reverse engineer the GPUs and make guesses at what is actually happening in the black box of the chip.

        Intel and AMD devs are the ones actually building the infrastructure while Nvidia ignores it and expects the community to do all the work for them for free except where they can't get anywhere in the market. I.E. their crappy ARM SoCs. Nvidia had hoped that their GPU tech would allow them to dominate in the ARM sector, it has never panned out for them.

        Comment


        • #5
          It really seam that mobile space have some real demand for Open Source GPU drivers!

          We even have some (small, or dev-kit) OEMs who boast FLOSS drivers support.

          Amazing.

          Comment


          • #6
            Originally posted by przemoli View Post
            It really seam that mobile space have some real demand for Open Source GPU drivers!
            More like Nvidia is banking a lot on Tegra right now and it's hardly making a dent in the market. Look at Nvidia's Shield which is great for emulation but nothing native. Thanks to Steam, Linux has more AAA native games on it compared to Android.

            Nvidia could be doing what AMD's is doing, and that's making a desktop ARM CPU. Which means they should also be focusing a lot on Linux, cause Windows on ARM is sucking. Android right now has hit a brick wall when it comes to quality applications.

            Comment


            • #7
              Originally posted by Dukenukemx View Post
              More like Nvidia is banking a lot on Tegra right now and it's hardly making a dent in the market. Look at Nvidia's Shield which is great for emulation but nothing native. Thanks to Steam, Linux has more AAA native games on it compared to Android.

              Nvidia could be doing what AMD's is doing, and that's making a desktop ARM CPU. Which means they should also be focusing a lot on Linux, cause Windows on ARM is sucking. Android right now has hit a brick wall when it comes to quality applications.
              But on desktop nobody ship floss drivers for Nvidia. And only Intel get them (but they do not have anything else, so that do not count).

              In mobile there are OEMs who ship freedreno IIRC.

              So mobile seam to be better explanation.

              Comment


              • #8
                @przemoli
                Nobody? The reason and origin of this patch is even given in the article:
                Originally posted by phoronix
                Arguably the clock can be seen as a stripped-down version of what is seen on NVE0, however instead of using NVE0 support has been written from scratch using the ChromeOS kernel as a basis.
                So it is most plausible that the Tegra 4 Chromebooks (Acer CB5 hit the news last month) is what prompted NVidia to work on this patch.
                http://www.androidpolice.com/2014/06...-and-32gb-ssd/

                Comment


                • #9
                  Originally posted by chithanh View Post
                  @przemoli
                  Nobody? The reason and origin of this patch is even given in the article:
                  So it is most plausible that the Tegra 4 Chromebooks (Acer CB5 hit the news last month) is what prompted NVidia to work on this patch.
                  http://www.androidpolice.com/2014/06...-and-32gb-ssd/
                  But that code may be from Nvidia open source kernel driver (yes all GPU vendors have more or less open source kernel drivers out there), that works with binary blob.

                  While that work is not compatible with Nvidia binary driver. And Nvidia binary driver would use different kernel driver.

                  (Its same situation as with AMD, they have 2 FLOSS kernel drivers, one for radeon driver, and one for catalyst driver)

                  Comment


                  • #10
                    No, it is not from anywhere. It has been written from scratch, as was stated by NVidia and reported by phoronix.

                    Comment

                    Working...
                    X