On 24/06/15 16:52, Grazvydas Ignotas wrote:
Hi,
On 06/24/2015 04:25 PM, Tomi Valkeinen wrote:
On 24/06/15 16:13, Michael Mrozek wrote:
However, I guess we need to move to omapdrm over time, as far as I know the SGX has only be compiled to be used with omapdrm, not omapfb, correct?
SGX has been used with both. The omapdrm + SGX combination has done a better job, though. Then again, at the moment mainline omapdrm can't probably be used with SGX, with the large atomic modesetting changes.
Yes but it can only use both omapfb and omapdrm only on OMAP3. The OMAP5 blobs have hard dependency on DRM. Or am I missing anything?
I haven't used the blobs out there, so you're probably right. I do know it's possible to compile the SGX driver/libs to use either omapfb or omapdrm.
Your news that the blobs lost compatibility with latest mainline are
Correct me if I'm wrong, but I don't think the mainline has ever been compatible with the SGX driver. There's always been some additional patches needed for omapdrm. At least this has been the case on the platforms I've worked on.
SGX will always be a huge pain in the ass, as long as it's closed source with no stable API towards the HW.
To be honest, I'm not sure if the compatibility has been broken. It could be, it could be not. We wanted to proceed with omapdrm modernization and cleanup, to get atomic modesetting and dmabuf fences supported, and build SGX support on top of those for a new SGX DDK. So we decided not to try too much to keep compatibility with old binary blobs out there.
really bad :( Have you heard any TI's plans about ever updating SGX blobs for OMAP5? Their latest release supporting OMAP5 is back from 2013...
For OMAP5, probably no plans. But I think OMAP5 has the same SGX as DRA7 and AM5, so when we get the new DDK working on DRA7 and AM5, it might work with OMAP5.
Tomi