<br><br><div class="gmail_quote">On Tue, May 15, 2012 at 5:23 AM, lkcl luke <span dir="ltr"><<a href="mailto:luke.leighton@gmail.com" target="_blank">luke.leighton@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, May 14, 2012 at 9:20 PM, Jaroslaw Niec <<a href="mailto:zuljin@go2.pl">zuljin@go2.pl</a>> wrote:<br>
<br>
> I have gone through files that Mark posted and found another one that is<br>
> also important<br>
> <a href="https://github.com/amery/linux-allwinner/blob/leak-lichee-3.0.8/drivers/video/sun4i/hdmi/aw/hdmi_core.c" target="_blank">https://github.com/amery/linux-allwinner/blob/leak-lichee-3.0.8/drivers/video/sun4i/hdmi/aw/hdmi_core.c</a><br>
> I have compared parameters from these files to HDMI Specification and it<br>
> looks like that the only way to have 23.976 and 59.940 is to reduce HDMI<br>
> clocks.<br>
<br>
</div> hmmm.... *thinks*. we need a bugtracker. this is quite complex, and<br>
very useful investigation jaroslaw. it will however get completely<br>
lost if noone takes it up, and that spells "bugtracker".<br>
<br>
tom, do allwinner have an internal bugtracker at all?<br></blockquote><div>Yes, we use bugzilla. But all android stuff there, so usually i don't need to care about it. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
l.<br>
<br>
_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk">arm-netbook@files.phcomp.co.uk</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><font face="'trebuchet ms', sans-serif">Keep simple, stay foolish.</font>
<div> </div><br>