On Nov 22, 2007 12:19 PM, Jerome Glisse <[EMAIL PROTECTED]> wrote: > Hi Kristian, > > Got a question on cliprect this might be dumb but what happen if hw is limited > on numbers of cliprect it can handle ? Does the X server also provide some > kind > of informations like buffer draw order (in which case cliprect are only > usefull > to save cpy memory) ?
The plan for DRI2 is to always have private back buffers (well, non-clipped at least, they may be shared with other clients), and to do double buffering, even for single-buffered fbconfigs. The cliprects are kept in the kernel and the swap buffer is implemented there. This will just do a copy of the clip rects from the back buffer to the front buffer. So the DRI driver won't have to worry about cliprects at all, and hardware can't limit the amount of cliprects, since we just have to do a bitblt per cliprect. cheers, Kristian ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
