On Tue, Jan 23, 2018 at 7:48 AM, Tomi Valkeinen tomi.valkeinen@ti.com wrote:
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. 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.
TI maintains some sort of SGX library on their git repo if I am not mistaken. If we as a community can get the kernel setup enough and provide TI with patches to make the SGX library work again with omap36 and OMAP35 processors, would TI accept patches to their library? With the changes so far, we're pretty close to getting the kernel the necessary infrastructure to setup/configure the hardware and provide the closed source blobs the necessary hooks to operate.
Secondly, Nikolaus and Tony have done a great job in trying to get the hwmods and reset stuff working (mostly) for the omap36 and to some extent the am33x. Would it be possible to get some TI assistance in determining what work is left to re-integrate compatibility into either the DRM of FB drivers? The SGX drivers appear to have been broken for years and mostly abandoned by TI. I know the OMAP3, OMAP4 and AM33 are older architectures, but having TI provide the remaining assistance would go a long way in showing they still care about their products.
Tomi
Thank you,
adam
-- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki