> Sorry. > > The problem was not in the logic of operation but in in use of variable > 'i' in this loop. After this loop it's value was never greater than > RADEON_NR_SAREA_CLIPRECTS and this variable is used in other loop (the > one containing 'smaller' one). It's value after the loop should be total > number of cliprects processed and send to hardware (correct me if I'am > wrong) not only in this pass. That's why we had this lockup. So I've > just used n wchich is not used after this loop. In my opinion each loop > should have it's own variable for iteration so we can avoid such > problems in future when for example someone changes some part of this > quite long loop not examining is as whole. In this case everything > worked well at firs sight. > > Jacek > > Sorry if my english isn't perfect but I'am not native english speaker > (writer ;-)).
OK, thanks for the explanation. It certainly needs to be cleared up... I'll commit your patch. Keith _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
