On 03/30/2014 11:39 PM, Grazvydas Ignotas wrote:
- The source image can't be linear, some padding is needed after every
line so that TILER could work with it. This is a problem with some software, especially some currently on pandora, although it can be fixed or worked around it's still extra effort or performance loss. 2. Today I found out that TILER memory can't be read, reading causes data abort. Every device since GP2X could read it's framebuffer, so this sucks. Same consequences like above, could also be OMAP misconfiguration, who knows.. 3, Writing to that memory currently is real slow. As the resolution increases it becomes even slower, it's like from 60% performance hit on low resolutions to 10x slowdown for fullhd. It would look like TILER can't keep up and is halting the CPU, from OS point of view it's 100% CPU usage. 4. Writing larger blocks to tiler memory is causing DISPC FIFO underflows, which means dropped frames (really bad for gaming console). 5. Mysterious L3 error interrupts from OMAP during writes 6. Xorg crash when xf86-video-omap is used with rotation 7. Some googling shows that TILER is not working with some formats used for video
Oh and 8. Corruption seen when rotated image is scaled
.. probably layer is set up incorrectly in the driver, should be fixable.