Announcement

Collapse
No announcement yet.

VA-API Support Set To Be Dropped From Mesa

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

  • VA-API Support Set To Be Dropped From Mesa

    Phoronix: VA-API Support Set To Be Dropped From Mesa

    The VA-API state tracker for Mesa's Gallium3D is set to be removed since it's fallen into disrepair without active maintenance...

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

  • #2
    I believe the title should say it was droped from gallium, not mesa...

    It is sad that not even the open drivers can settle for a single API, so much duplicated efforts and incompatibility...

    Comment


    • #3
      I dont understand the reason behind this, vdpau is not that good than va-api and have nvidia really no patent? If amd would announce that they will use that I would understand it maybe, but that has to be a priority to make that work in at least the next 2 years so why would you remove it then?

      Or is it the target to never be able to use gpu for video decoding at all? If thats so, ok say it, I switch then to intel inkl. processors for good.

      Comment


      • #4
        The VA-API state tracker for Mesa's Gallium3D is set to be removed since it's fallen into disrepair without active maintenance.
        Not quite. I don't think it's worked ever, actually. And the build has been disabled since July 2011. See http://cgit.freedesktop.org/mesa/mes...97d397bada650b

        However, rather than just disabling the build support for VA-API in Mesa, it's set to be removed entirely. Matt Turner sent in a patch to remove the 1.5k lines of code for this "VA" state tracker that had targets for the R300 and R600 Gallium3D hardware drivers.
        The build has been disabled since last year and it's doubtful that it ever worked before that. See above.

        Comment


        • #5
          This reminds me: weren't the nouveau developers close to getting the h264 decoders working on nvidia hw a few months ago?
          What happened to that? Does anyone know?

          Comment


          • #6
            That would be a shame.. I consider va-api the vendor neutral api that should be used by all other vendors to expose there video decoding stuff. But that's just my little perfect world

            Comment


            • #7
              title is extremely misleading...

              Comment


              • #8
                It's just a byproduct of intel not supporting gallium3d, because you know they would have the va-api state tracker in good shape. I really wish Intel would get on board the Gallium ship, but I can't blame them for not wanting to reinvent the wheel.

                Comment


                • #9
                  Originally posted by DanL View Post
                  It's just a byproduct of intel not supporting gallium3d, because you know they would have the va-api state tracker in good shape. I really wish Intel would get on board the Gallium ship, but I can't blame them for not wanting to reinvent the wheel.
                  As far as i understand it this has nothing to do with Intel. Intel uses their HW and this is a shader based implementation. So if intel was on G3D they would just plug their HW in the tracker (or whatever fits technically) and would not even bother with shaders.

                  Comment


                  • #10
                    Its too bad. Wish someone could patch this up into working condition, maybe then r600 users would have some nice VA-API.

                    Comment


                    • #11
                      Originally posted by 89c51 View Post
                      As far as i understand it this has nothing to do with Intel. Intel uses their HW and this is a shader based implementation. So if intel was on G3D they would just plug their HW in the tracker (or whatever fits technically) and would not even bother with shaders.
                      Hmm. I thought the tracker would be more generic and have the backend implementation left to the driver.

                      Comment


                      • #12
                        why mesa developer develop vdpau tracker rather than vaapi?

                        is it because that vdpau is a better api than vaapi? (i am not a expert in this area)

                        Comment


                        • #13
                          Originally posted by 89c51 View Post
                          As far as i understand it this has nothing to do with Intel. Intel uses their HW and this is a shader based implementation. So if intel was on G3D they would just plug their HW in the tracker (or whatever fits technically) and would not even bother with shaders.
                          it is normal that intel do not use Gallium3D

                          why would they develop a good shareable graphic framework that benefit their rivals directly?
                          if Gallium3D is stable, mature and fast, who will buy intel?

                          they will develop a working driver for their flagships NOW, using the old mesa infrastructure (quick, easy and dirty)

                          After a few years later, who will maintain the unmaintainable driver => let other open source enthusiast do it, developer will surely "enjoy" maintaining two different driver structure
                          Last edited by unknown2; 09-08-2012, 12:11 AM.

                          Comment


                          • #14
                            Originally posted by gururise View Post
                            Its too bad. Wish someone could patch this up into working condition, maybe then r600 users would have some nice VA-API.
                            r600 has the VDPAU state tracker, why would you additionally want VA-API? The problem is not in the api, it's writing a shader based h264 decoder. Right now the only shader based decoder in Gallium is mpeg2. This wouldn't suddenly change if someone updated the VA-API state tracker.



                            Originally posted by unknown2 View Post
                            why would they develop a good shareable graphic framework that benefit their rivals directly?
                            if Gallium3D is stable, mature and fast, who will buy intel?
                            This is pure nonsense. First, the mesa work Intel does (to bring opengl 3.1 and such) benefits *both* kinds of drivers, gallium and classic mesa ones. Gallium doesn't have a whole different opengl stack, as some seem to think.

                            The second question I can't even parse. Are you saying the radeon and nouveau drivers are in the state they are (lack of power management, low performance, no access to hardware decoders) only because Gallium isn't mature or something? And that if Intel had a Gallium driver, the radeon and nouveau drivers would magically become better in this regard? That makes no sense.

                            Intel switching to Gallium would change pretty much nothing. That's why they don't do it, it'd be a huge effort for no real gain.

                            Comment


                            • #15
                              Originally posted by markg85 View Post
                              That would be a shame.. I consider va-api the vendor neutral api that should be used by all other vendors to expose there video decoding stuff.
                              VA-API is about as vendor neutral as VDPAU.

                              Comment

                              Working...
                              X