Announcement

Collapse
No announcement yet.

Nouveau Gallium3D Now Supports OpenGL 3.2, 3.3

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

  • Nouveau Gallium3D Now Supports OpenGL 3.2, 3.3

    Phoronix: Nouveau Gallium3D Now Supports OpenGL 3.2, 3.3

    With a fresh round of Mesa Git commits on Monday morning the support landed for OpenGL 3.2 and OpenGL 3.3 within Nouveau's NV50 and NVC0 Gallium3D drivers...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Boy, I am really disappointed in YKW....
    How its possible to write an article and not mention the fact that in essence all NV50 class cards, have feature party with binary driver now....

    Comment


    • #3
      when will r600 get 3.3. support

      Comment


      • #4
        Thanks for the shout-out, Michael!

        Originally posted by phoronix View Post
        landed for OpenGL 3.2 and OpenGL 3.3 within Nouveau's NV50 and NVC0 Gallium3D drivers
        Actually the NVC0 driver was already at OpenGL 3.2, which got turned on when the mesa state tracker got support for OpenGL 3.2. The patchset from the article included patches to move that up to 3.3 though by adding support for the 10/10/10/2-related extensions.

        Originally posted by phoronix View Post
        NVC0 (the GeForce 4 and newer; Fermi and Kepler)
        Presumably you meant GeForce 400 and newer...

        Originally posted by phoronix View Post
        All of these Nouveau changes will be part of the upcoming Mesa 10.1 release, but too bad that many Nouveau bugs and regressions remain.
        Yes, it is unfortuante that bugs/regressions exist (and even more unfortunate that in many cases they remain unreported, but what can you do). Is the suggestion that the nouveau project should concentrate exclusively on fixing bugs and avoid new feature work until there are no more bugs? Hopefully not -- most of the time the developers can't see the issues themselves, or those issues would be fixed already.

        Comment


        • #5
          Again, GLSL 150 is for GL 3.2, GL 3.3 needs GLSL 330.

          Comment


          • #6
            Originally posted by sharan View Post
            when will r600 get 3.3. support
            There is WIP support here:

            Comment


            • #7
              Sweet! GL4 is now the next step, which will lande some nice new extension allowing even better performance on supporting hardware.

              I do wonder however if non compliant hardware like the NV50 will get GL4 support. What happens to extensions that doesn't have hardware support, do they get implemented on CPU or using GPU-compute?

              Comment


              • #8
                Interestingly, the OpenGL 3.3 changes for Nouveau were committed, while the OpenGL 3.3 updates for RadeonSI are still outstanding -- have not yet been committed. The patch set seems to be about the same size. Anyone know why that is?

                Comment


                • #9
                  Originally posted by werfu View Post
                  I do wonder however if non compliant hardware like the NV50 will get GL4 support. What happens to extensions that doesn't have hardware support, do they get implemented on CPU or using GPU-compute?
                  It's unlikely that NV50 would get GL4.0 -- that requires tesselation shaders, which NV50-class cards just don't have. The proprietary driver also only goes up to GL3.3 (for nv50), but also exposes a bunch of GL4-era extensions that are possible to implement using the hardware available. (Nouveau is definitely behind in that regard, but working on it!)

                  Comment


                  • #10
                    Originally posted by dffx View Post
                    Interestingly, the OpenGL 3.3 changes for Nouveau were committed, while the OpenGL 3.3 updates for RadeonSI are still outstanding -- have not yet been committed. The patch set seems to be about the same size. Anyone know why that is?
                    Why would you expect any correlation between the two? Different hw, different teams of people working on it, different review procedures, I posted my patchset 2 weeks earlier...

                    Comment

                    Working...
                    X