On Nov 22, 2007 4:03 AM, Thomas Hellström <[EMAIL PROTECTED]> wrote: ... > There are probably various ways to do this, which is another argument > for keeping super-ioctls device-specific. > For i915-type hardware, Dave's approach above is probably the most > attracting one. > For Poulsbo, all state is always implicitly included, usually as a > reference to a buffer object, so we don't really bother about contexts here. > For hardware like the Unichrome, the state is stored in a limited set of > registers. > Here the drm can keep a copy of those registers for each context and do > a smart update on a context switch. > > However, there are cases where it is very difficult to use cliprects > from the drm, though I wouldn't say impossible.
The idea is to keep the cliprects in the kernel and only render double buffered. The only code that needs to worry about cliprects is swap buffer, either immediate or synced to vblank. What are the cliprect problems you mention? 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
