jzencovich,
The problem with this device is where the powervr writes to.

Unlike other omap2 devices (mainly phones) its not a straight forward binary thats required.
other omap2 devices use the framebuffer directly on the omap2 chip and output video to the lcd directly out of the omap2 itself.

( triangles+textures->powervr->framebuffer->screen )

The nokia device uses a resolution which is simply too large to enable to the use of this on omap framebuffer which meant an alternative seperate LCD driver chip is used which has a framebuffer inside main memory.

(this kind of arrangement is also inside the 770 - the only difference is the older CPU on the 770 did not have a dedicated framebuffer on the cpu chip)

A "normal" driver for other operating systems running the same omap chip therefore will not work and would need to be specially constructed (which is possibly what has happened and appears to exist within nokia).


On the drivers justification page, a possible way through this problem is outlined which would require setting up a pipeline to render 3d data to the internal SRAM framebuffer with the powervr, then using the IVA to convert this data to YUV and sending over to main memory for actual rendering by the LCD chip.
Its a longshot and we have no documentation for any of the components but according to everything I know could get us 640*480 at 30fps...

*de-emphasised due to being told its not sustainable.

Of course, there may be a simpler way to tell the powervr to render its frames directly to main memory (so the lcd can see them) in YUV mode, but again without documentation we will never know.


that is my understanding of the problem, if I'm wrong please correct me.