Well I've traced this a bit, an operation appears to be hanging the chipset,
Keith, maybe you can tell me, in i830_span.c you no longer have a HW_LOCK or HW_UNLOCK defined for the i830 has something happened elsewhere that makes these unnecessary,
There are the i830SpanRenderStart() and i830SpanRenderFinish() callbacks from swrast which do the locking now.
what blender seems to be doing is loading up a string of glBitmaps to create its frontend, and after a bunch of these a HW_LOCK call from i810WriteRGBAPixels_565 calls DMAFinish which doesn't seem to have finished for some reason from the previous one, any ideas why this might happen?
If dma hasn't finished, the worst that will happen is some of the uploaded bitmap on the screen will be corrupted.
Maybe the vast number of HW_LOCK calls is an issue?
Keith
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
