In order to support automatic in-ring flushing when the DRM_BO_FLAG_WRITE is dropped from a buffer object. We'd be using the command_stream_barrier() method. We need to have two driver-dependent fence type flags instead of one. One for read an one for write. The idea would be to _consider_ an MI_FLUSH if
1) The read flag is dropped and the write flag is not set. 2) The write flag is dropped. We could still support the RW flag as the or-ed together value of these two, so the mesa drivers would need no code change. /Thomas ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. 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
