Quote:
My first thought on seeing the efikamx was whether I could replace my aging Xbox1 setup that runs XBMC with a low power, noise-less efika. The only major output missing IMO, is a digital audio out to carry raw PCM streams. With 3D drivers, the i.MX515 should be able to drive 420p and perhaps 720p (haven't checked). Thoughts regarding the feasibility of this are welcome.
hello Amit, welcome aboard!
with the risk of slightly hijacking your thread, let me try to partially answer your question about imx515's display-driving 3D capabilities.
the original XGPU has indisputably higher raw characteristics - at ~930MPix/s raw peak fillrate and two TMUs, it can output notably more '3D' pixels than the z430 (166MPix/s peak), or any other mobile SoC GPU today. that said, xbox has a rather hapless memory architecture (framebuffer in UMA, with no local 'tile' buffers whatsoever), which brings to some serious CPU/GPU bus contention. additionally, z430 is a contemporary mobile GPU, capable of things that are either too difficult on the XGPU (nv2a) or plain impossible.
I think that you would be more interest how z430@EfikaMX compares to other contemporary SoC GPUs. And there it stands its grounds.
While not the fastest ROP performer (1 pixel/clock @ 166MHz), imx515's z430 has probably the highest ALU shader performance in its class today (I'm yet to check SGX54x though) - that means that the z430 is better suited for 'complex' pixel scenarios, at modest resolutions - 1024x768 is about as high as I'd try to drive the chip to do real-time 3D; at that res, we get a peak of 166Mp/s / (1024 * 768) = 211 framebuffers/s, @30 fps = 7x overdraw factor - that's not abound but it's still usable in game-like scenarios. needless to say, at such resolutions you'd also need good occlusion techniques for your complex-shader pixels, and you have to be careful not to go overboard with 'dumb' pixels (such as those in particles, post-process filters, etc).