2008/11/21 The Rasterman Carsten Haitzler <span dir="ltr"><<a href="mailto:raster@rasterman.com">raster@rasterman.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div class="Wj3C7c"><br>
</div></div>XSync sends a request to x and waits for a reply - so your client app will stop<br>
and wait until x replies. x will reply once it has completed all existing<br>
requests - that means the XCopeArea. while your app is waiting xglamo is<br>
waiting for the gfx chip to do the work - and likely its sitting in a loop<br>
polling checking when the command is done.<br></blockquote></div><br>Thanks Raster, now things are becoming clear :)<br>The glamo chip should raise an interrupt when the command is done, a specialized kernel module should export this interrupt to the userspace so Xglamo may suspend waiting for this interrupt without wasting cpu cycles!<br>
I suppose that this should be quite easy and cheap for Openmoko developers, may it be considered?<br>This will really improve the device performance!<br><br>Regards<br><br> Nicola<br><br><br><br><br>