On Sun, 2004-05-23 at 11:32, Mike Mestnik wrote: > I think I finaly get it. When we have a window grater then 2048, we need > to run a GL command move the cliprect and run it again? The only way to > find out where we need is to SW render the cmd. Won't this cut our > framerate in half? Plus moving the cliprect for most of the drawing cmds, > what about non-drawing. > > First thing I see is there is no check in the client driver for 2048. > What about numbcliprects, can we treat one app like its 2? we are still > doing every thing twice, but now we just have overhead on the system CPU.
The 3D driver already handles several cliprects for when a window is partially obscured, SHAPE windows, ... That would just need to be extended to multiplex the cliprects on boundaries of multiples of 2048. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
