<div class="gmail_quote">2009/4/3 Carsten Haitzler <span dir="ltr"><<a href="mailto:raster@rasterman.com">raster@rasterman.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
so the other side of that is to do everything with the cpu in system ram and<br>
transfer to the glamo when done - so you only deal with the slow write once, at<br>
the end. but remember the write - when being done, will hold the cpu hostage<br>
and as it is now slowed down to 1/6th its normal speed during this write - you<br>
lose even more cpu power.<br>
<br>
the solution is to just update less of the screen, make drawing simple so the<br>
cpu has to do less when software-rendering, and/or drop down to qvga.<br>
<br>
please dig over the archives of this list. this has been gone over in gory<br>
detail before :)<br></blockquote></div><br>Hi Raster. Thanks for your splendid presentation of the graphics issue... I didn't<br>manage to find it from the archives.<br><br>What really surprises me is the fact that if this is so clear, why is Comunity not working<br>
on qvga graphics yet? Is it not a waste of time to try to get glamo fully working and then<br>keep on going over VGA resolution?<br><br>I'd prefer to drive the funnier modest car than to have the ferrary parked outside... I though <br>
linux and free software people were mostly this way. <br clear="all"><br>--<br>There is no spoon<br><br>