OMX Tizonia Gallium3D State Tracker Sent Out For Review

[phoronix]

Phoronix: OMX Tizonia Gallium3D State Tracker Sent Out For Review

Student developer Gurkirpal Singh has sent out his OpenMAX "Tizonia" Gallium3D state tracker patches for review by upstream Mesa developers, marking a successful GSoC 2017 project...

http://www.phoronix.com/scan.php?page=news_item&px=Tizonia-G3D-Patches-For-Review

[linuxgeex]

Michael Readers might like to know that OpenMAX-IL is an API for hardware-accelerated Audio/Video/Image media.

[Nille_kungen]

Well done, work that been needed for long.
Let's hope the patches turn up correctly so it can be checked, it seems like the first patch was to big.

[Michael]

I'm so glad rich Google executives got poor kids to do all that hard intellectual work for free. They need to learn to serve their corporate masters. If they're lucky, some day Google might trickle down green toilet paper (aka "money") to them and they can then purchase the privilege of life. That's what makes America so great!

You do know that GSoC students are paid a few thousand for their 'internship', right?

[linuxgeex]

You do know that GSoC students are paid a few thousand for their 'internship', right?

That plus mentorship is a hell of a lot better deal than university where the poor kids pay to do all that hard intellectual work, and the university owns it, rarely sharing much besides a footnote of the developers' names.

[timofonic]

What's this OpenMAX IL is useful for? A multiplatform replacement of VAAPI/VDPAU/(insert here other zillion of video acceleration APIs or frameworks like libyami and qsv)?

[chithanh]

timofonic
OpenMAX is a set of multimedia/acceleration APIs used by more than a billion of devices (mostly Android or embedded). It is a vendor-neutral open standard maintained by Khronos and probably the most used video acceleration API today.

VDPAU and VA-API are NVidia's and Intel's standards respectively, although AMD does support both to some degree too.

[timofonic]

timofonic
OpenMAX is a set of multimedia/acceleration APIs used by more than a billion of devices (mostly Android or embedded). It is a vendor-neutral open standard maintained by Khronos and probably the most used video acceleration API today.

VDPAU and VA-API are NVidia's and Intel's standards respectively, although AMD does support both to some degree too.

So with not use OpenMAX instead of VDPAU and VAAPI?

[chithanh]

Historic reasons. VDPAU was the first "modern" video decode acceleration API on the desktop (earlier ones like XvMC did not support modern formats) so got most widespread support among Linux desktop applications. VA-API then became most widely used on the Linux desktop due to Intel. Also OpenMAX is somewhat complex to implement.

[timofonic]

Historic reasons. VDPAU was the first "modern" video decode acceleration API on the desktop (earlier ones like XvMC did not support modern formats) so got most widespread support among Linux desktop applications. VA-API then became most widely used on the Linux desktop due to Intel. Also OpenMAX is somewhat complex to implement.

What about time for a change for progress and FOSS being less conservative as it was in the past? :P