Page 1 of 3 123 LastLast
Results 1 to 10 of 21

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

  1. #1
    Join Date
    Jan 2007
    Posts
    14,645

    Default 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. #2
    Join Date
    Sep 2011
    Location
    Rio de Janeiro
    Posts
    202

    Default

    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...

  3. #3
    Join Date
    Jul 2008
    Posts
    780

    Default

    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.

  4. #4
    Join Date
    Jan 2008
    Posts
    299

    Default

    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.

  5. #5
    Join Date
    Jun 2006
    Location
    Portugal
    Posts
    526

    Default

    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?

  6. #6
    Join Date
    Oct 2007
    Posts
    284

    Default

    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

  7. #7
    Join Date
    May 2010
    Posts
    684

    Default

    title is extremely misleading...

  8. #8
    Join Date
    Oct 2007
    Posts
    1,269

    Default

    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.

  9. #9
    Join Date
    Jan 2009
    Posts
    1,656

    Default

    Quote 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.

  10. #10
    Join Date
    Dec 2008
    Location
    San Bernardino, CA
    Posts
    232

    Default

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

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •