Michel Dänzer wrote:
I guess the trouble is with what else gets copied. I'm not sure exactly what I ended up deciding (whether copying was ok or not), but things to think about revolve around what happens when Xlib and GL drawing occur in the same drawable (yes, it's well defined).On Mon, 2002-12-16 at 13:47, Keith Whitwell wrote:Michel Dänzer wrote:You have to double draw everything. I don't have an implementation, but a correct one would do those twice, too.On Mon, 2002-12-16 at 13:34, Keith Whitwell wrote:Michel Dänzer wrote:I haven't. I'll have to go back to the last email thread I had on this, with Alan Hourihane, where (I think) I convinced myself once again that there was no way any copying scheme could ever be completely correct, and that only double-drawing could do the job properly.On Mon, 2002-12-16 at 10:47, Keith Whitwell wrote:The 830 page flipping code is turned off for some good reasons:
- I haven't seen it work without really visible corruption on the flip - typically flashing and blank areas
Presumably it uses the mi shadow module, and you should try shadowfb instead? Have you (or anyone else, for that matter) had a chance to try my patch for the radeon driver?
I on the other hand am pretty convinced that double drawing will never work. :) Because it doesn't handle unaccelerated primitives, or how does it?
And how is drawing things twice different to drawing them once and then copying? The problem with the mi shadow module is that the copy doesn't happen immediately after drawing.
Keith
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
