Am 23.01.2018 um 16:34 schrieb Tomi Valkeinen tomi.valkeinen@ti.com:
On 23/01/18 16:41, H. Nikolaus Schaller wrote:
Hi Tomi,
Am 23.01.2018 um 14:48 schrieb Tomi Valkeinen tomi.valkeinen@ti.com:
Hi,
On 23/01/18 15:38, H. Nikolaus Schaller wrote:
In the end we should have a single, generic SGX driver for all OMAP SoC variants sitting in mainline drivers/gpu/pvr. So the goal is to end the era of out-of tree SGX drivers for a significant portion of OMAP processors.
I don't think that will ever happen, because there is no open source userspace library for SGX. That library is the "real" driver here.
Yes and no... It can be seen as application software for the SGX and consists of a microkernel and user-space libs to communicate with it. Both are unfortunately closed source but no kernel components and need no integration. Just data sent back and forth through open source drivers.
At least the policy has been (I believe it still is) that you can't have a driver in the kernel which can only be used with a closed source userspace component.
I see counter-examples, mainly in the WiFi area. There are drivers for Realtek, Marvell, TI WiFI chips and firmware is separate and required to make it useful.
Other examples may also exist.
Well, you can refer to
https://dri.freedesktop.org/docs/drm/gpu/drm-uapi.html#open-source-userspace...
Interesting.
But I don't see how it is related to OMAP-SGX at all (except that it is about a GFX subsystem).
I understand that this is for the case we would plan to craft a proper DRM based solution so that DRM API and user space libs can be used.
This is obviously far beyond feasibility and maybe the fifth or tenth step.
But we want to do what can be done.
My idea is also to get it placed in drivers/staging/pvr and not drivers/gpu/drm.
BR, Nikolaus