Announcement

Collapse
No announcement yet.

Mesa 10.2 Features Are Quite Exciting

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

  • Mesa 10.2 Features Are Quite Exciting

    Phoronix: Mesa 10.2 Features Are Quite Exciting

    Mesa 10.2 is expected to be released in the next few days and with this three-month update will come many improvements to the Intel, Radeon, and Nouveau graphics drivers plus other improvements to core Mesa/Gallium3D, the advancement of the Freedreno Gallium3D driver, and much more...

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

  • #2
    I'm confused about Openmax. What was wrong with vaapi / vdpau to warrant a replacement?

    Comment


    • #3
      What about R600 improvements?

      Comment


      • #4
        Originally posted by zanny View Post
        I'm confused about Openmax. What was wrong with vaapi / vdpau to warrant a replacement?
        VDPAU is used for decoding, OpenMAX for encoding right now.

        Comment


        • #5
          any news for OpenGL 3.3 support on SandyBridge hardware?

          Comment


          • #6
            Originally posted by edoantonioco View Post
            What about R600 improvements?
            There's none.

            Comment


            • #7
              A small correction: Mesa 10.2 does not support compute shaders. Paul landed some of the initial API code, but no driver actually supports them yet. There's a lot of work left before that can happen.
              Free Software Developer .:. Mesa and Xorg
              Opinions expressed in these forum posts are my own.

              Comment


              • #8
                Originally posted by zanny View Post
                I'm confused about Openmax. What was wrong with vaapi / vdpau to warrant a replacement?
                VDPAU doesn't support encoding.

                VAAPI does things in a way that's specific to intel hardware - it's easier and more efficient for AMD hardware to use OpenMAX instead.

                Comment


                • #9
                  Originally posted by zanny View Post
                  I'm confused about Openmax. What was wrong with vaapi / vdpau to warrant a replacement?
                  OpenMAX is another Khronos specification like OpenGL and OpenCL. OpenMAX supports both Encode and Decode but it really hasn't seen that much adoption in applications, AFAIK.

                  VAAPI is Intel's Encode / Decode library. Its seen a fair bit of adoption in video applications but its not the most widely adopted.

                  VDPAU Is Nvidia's Decode only (no Encode) spec. Its seen the most adoption and is supported by the Radeon driver already.

                  Personally seeing increased OpenMAX adoption would make me happy, but thats a chicken-egg problem since not many applications support it.

                  Comment


                  • #10
                    Originally posted by gufide View Post
                    any news for OpenGL 3.3 support on SandyBridge hardware?
                    As far as I know SandyBridge GPU supports OpenGL up to 3.1 only..

                    Comment


                    • #11
                      Sandy Bridge can very much do OpenGL 3.3, but someone needs to write support for geometry shaders. Someone not Intel, they've moved on to newer hardware already. Your link shows what's supported by the Windows driver, not what the hardware is capable of.

                      Comment


                      • #12
                        hm

                        Originally posted by Gusar View Post
                        Sandy Bridge can very much do OpenGL 3.3, but someone needs to write support for geometry shaders. Someone not Intel, they've moved on to newer hardware already. Your link shows what's supported by the Windows driver, not what the hardware is capable of.
                        it will not happen without intel support

                        Comment


                        • #13
                          Isn't that vce firmware naming which trying to load in 3.15 kernel also confusing to anyone else ? When i first saw it, i am thinking... why this bloody bonaire wants to load on kabini .

                          It is named BONAIRE_vce.bin , but seems like trying to load for all Temash, Kabini, Kaveri, Bonaire and Hawaii hardware . I think that deserves better naming like UNIVERSAL_vc2.bin or something like that .
                          Last edited by dungeon; 05-26-2014, 03:31 PM.

                          Comment


                          • #14
                            Obligatory reference

                            Since Michael is a poor "journalist" who never cites his sources.

                            http://cgit.freedesktop.org/mesa/mesa/tree/docs/GL3.txt

                            Comment


                            • #15
                              The only thing missing for 3.3 compilance is the geometry shader, and reading the mailing list it was possible to implements, but a little harder than the others

                              source: http://lists.freedesktop.org/archive...er/046150.html

                              Comment

                              Working...
                              X