If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

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.

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.

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.

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.