On Thu, 2003-10-30 at 20:17, Alex Deucher wrote: > Hopefully I'll have some time this weekend to look into this, what > files in the r200 client driver should I be looking at? Having looked > at the code I'm guessing r200_state. Scissor and cliprect stuff.
Yes, I'd say split the cliprects into the zones after DRI_VALIDATE_DRAWABLE_INFO() in GetLock() and then add zone handling anywhere cliprects are dealt with. > Although thinking about it more, there are probably more changes > required since I guess every part of the 3D pipeline must be updated > (or at least where the commands are issued to the card) depending on > which "2048 zone" the rendering falls into. I hope only the viewport transformation needs updating for each zone? > Would it be better to make the solution more generic? I.e., introduce > the concept of "zones" of cliprects, the extents of which would be > determined based on the limitations of the hardware. the driver would > then render based on zones. Maybe I'm overthinking it... Not sure either, I guess you can still consider generalizing it once it's working. -- Earthling Michel DÃnzer | Debian (powerpc), X and DRI developer Software libre enthusiast | http://svcs.affero.net/rm.php?r=daenzer ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
