Announcement

Collapse
No announcement yet.

MSAA For Mesa Finally Moves Closer

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

  • MSAA For Mesa Finally Moves Closer

    Phoronix: MSAA For Mesa Finally Moves Closer

    Mesa is finally getting closer to properly supporting MSAA, a.k.a. Multi-Sample Anti-Aliasing, but for now this is just Intel Sandy Bridge supported...

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

  • #2
    All I can say is: mwahahahahahaha!!!
    MSAA has been with us like 10 years now?

    Comment


    • #3
      Intel is doing so much work updating OSS technologies, I'm very thankful for it.

      Originally posted by bug77 View Post
      All I can say is: mwahahahahahaha!!!
      MSAA has been with us like 10 years now?
      I'm just glad it's not 15 years. Or 20. Or more.

      Comment


      • #4
        Originally posted by bug77 View Post
        All I can say is: mwahahahahahaha!!!
        MSAA has been with us like 10 years now?
        Step by step, we're getting closer to a fully open OpenGL implementation running on all relevant hardware.

        People used to laugh at the state of Mozilla, OpenOffice, GCC, Linux, and almost everything else we now take for granted. There was always a clever guy who was convinced that WordPerfect and IE, in their binary emulated form, were the eternal future of the Linux desktop.

        All in due time. The gap is closing, as negative as Michael is towards it.

        Comment


        • #5
          Now if the other Mesa/Gallium3D drivers would move on with proper MSAA anti-aliasing support, albeit the drivers are already not fast enough without AA.
          Not fast enough for what?

          I am a gamer and I am using them to great effect. They may not be perfect, but to just say are "not fast enough" to me crosses a line.

          I just won Trine 2 with them again, a game originally released in 2011 and noted for it's graphics. Now, it did not have all of the effects going (the lack of AA being one of them) but it was certainly playable and workable.

          So it was fast enough for that...

          Comment


          • #6
            MLAA in Mesa though is done on the CPU and is already not well supported by all Mesa/Gallium3D drivers.
            Huh? MLAA is implemented by adding a post processing shader, which runs on the GPU.

            I'm not sure what Michael meant there...

            Also, what drivers does it not work on? Does he mean pre r5xx hardware?

            Comment


            • #7
              Support for evergreen/cayman and WIP support for 6xx/7xx is available here:
              http://cgit.freedesktop.org/~airlied...og/?h=r600g-ms

              Support for r3xx-r5xx shouldn't be too hard to add. See section 10.8 of the r5xx acceleration programming documentation:
              http://www.x.org/docs/AMD/R5xx_Acceleration_v1.5.pdf
              Last edited by agd5f; 05-10-2012, 09:03 PM.

              Comment


              • #8
                Sweet, keep up the good work.

                Comment


                • #9
                  MSAA and GL 3.0

                  I did read somewhere that MSAA is actually required in GL 3.0 and later? If this is true? I mean Intel has been advertising GL 3 for a while now and the only add MSAA now?

                  Comment


                  • #10
                    Originally posted by Paulie889 View Post
                    I did read somewhere that MSAA is actually required in GL 3.0 and later? If this is true? I mean Intel has been advertising GL 3 for a while now and the only add MSAA now?
                    I am curious about it, too.

                    Comment


                    • #11
                      Originally posted by agd5f View Post
                      Support for evergreen/cayman and WIP support for 6xx/7xx is available here:
                      http://cgit.freedesktop.org/~airlied...og/?h=r600g-ms

                      Support for r3xx-r5xx shouldn't be too hard to add. See section 10.8 of the r5xx acceleration programming documentation:
                      http://www.x.org/docs/AMD/R5xx_Acceleration_v1.5.pdf
                      I'm not a programmer, though I'm slowly starting to build some basic skills, so I don't really understand how the documentation is translated to code. Do you know of walk-through example of this? Like a blog post detailing how a specific feature was implemented (in some level of detail)? It could be an interesting read!

                      Comment


                      • #12
                        Originally posted by Paulie889 View Post
                        I did read somewhere that MSAA is actually required in GL 3.0 and later? If this is true? I mean Intel has been advertising GL 3 for a while now and the only add MSAA now?
                        Idk about "required", but it has been around since like OpenGL 1.5

                        Comment


                        • #13
                          Nouveau.

                          Excuse me, but nouveau/nv50,nvc0 have been supporting MSAA for a year now (http://cgit.freedesktop.org/mesa/mes...2820b00a9ce667).

                          Comment


                          • #14
                            Michael, this is wrong:
                            MLAA in Mesa though is done on the CPU
                            It runs entirely on the GPU.

                            Of course Mesa as a whole may be cpu-limited, but please don't confuse the two

                            Comment


                            • #15
                              Originally posted by anbog View Post
                              I'm not a programmer, though I'm slowly starting to build some basic skills, so I don't really understand how the documentation is translated to code. Do you know of walk-through example of this? Like a blog post detailing how a specific feature was implemented (in some level of detail)? It could be an interesting read!
                              For an extremely simple feature (ROUND support), it went something like
                              - read the docs to pick a suitable opcode, if it exists
                              - check the right file on how the other opcodes around it are implemented, copy-paste a suitable function / add an argument to the handler
                              - bind it to that function in the tables for the hw

                              And the result:
                              http://cgit.freedesktop.org/mesa/mes...bfafcd0800f4f8

                              Comment

                              Working...
                              X