Intel's EMDG expert Kirk Blum asked me to pass along this reply (he was having some technical issue accessing the site)...
From Kirk -
Let me answer your last question first as it has bearing on the first question.
The IP contained in the PowerVR is very carefully licensed by the owner and greatly restricts the information we can make available. What we have released in source code in the EMGD package is everything that we are allowed to release including information on the APIs used.
As such, the specific calls, even though exposed in the kernel code, the inner workings are still considered private by the IP owner (and is the reason they run in User space, not the Linux kernel).
I think you are getting the idea about the first question- I just do not have anything that we can provide on how that specific call works. It may actually be a generic item in a standard PowerVR header but is not "wired up" inside the driver. It is also subject to change so if you managed to figure out how it works, there is a really good chance it would change in the future.
From my experience, your idea is very elegant, but may be trying to be "too cleaver". If I am not mistaken, there are other ways to stream textures that will work through more standard calls and you probably should be looking for those..
I hope this helps
J. Felix McNulty
Community Moderator (Intel contractor)