<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<div>> From: henrik@henriknordstrom.net<br>> My understanding is that the A10 is capable of<br>> <br>> - direct FB playback<br>> - playback in a movable 2D overlay region of the screen. There is a<br>> (limited) number of these 2D overlays available.<br>> - indirect playback via a 3D texture drawn into by the VPU and rendered<br>> by the GPU.<br>> <br>> In neither case you use the GPU for video decoding. At most YUV-RGB<br>> transformation.<br>> <br><br></div><div>Changed topic of this thread to better suit the discussion.</div><div><br></div><div>No matter how the video is decoded,it must still be presented synchronized to</div><div>the display clock driving the HDMI or VGA port. If you look at the source and</div><div>settings available in Android, you will see they only offer a limited set of</div><div>timings:</div><div><br></div><div>Under:</div><div><a href="https://github.com/amery/linux-allwinner/blob/leak-lichee-3.0.8/drivers/video/sun4i/hdmi/drv_hdmi.c">https://github.com/amery/linux-allwinner/blob/leak-lichee-3.0.8/drivers/video/sun4i/hdmi/drv_hdmi.c</a>
</div><div><br></div><div>You will see they are missing 23.976 and 59.940. There are movies for example encoded in both</div><div>23.976 and 24.000 fps so you must have a way to set both modes individually.</div><div><br></div><div>The reason I think a custom modeline might solve the problem is that looking into:</div><div><br></div><div><a href="https://github.com/amery/linux-allwinner/blob/leak-lichee-3.0.8/drivers/video/sun4i/disp/de_bsp/de/disp_clk.c">https://github.com/amery/linux-allwinner/blob/leak-lichee-3.0.8/drivers/video/sun4i/disp/de_bsp/de/disp_clk.c</a>
</div><div><br></div><div>You find a table that corresponds to the pre-defined output modes available in Android. Hopefully the hardware</div><div>supports timings that are not included in this table so we can manually define a proper 23.976 and 24.000 mode</div><div>for example. I have not seen where one can define the other video timing related parameters such as horizontal</div><div>and vertical sync width, front/back porch, and pixel counts.</div> </div></body>
</html>