On Tue, Oct 22, 2002 at 10:24:04PM +0100, Alan Cox wrote: [...]
I can believe there are objects in 3D rendering big enough to be worth mapping but I'd be guessing to name a size. Linus as a chip hacker might actually have more detailed numbers.
At least with the Mach64 is very rare for this to happen - vertex data is fairly compact and usually there is some state change which forces to flush the buffer. The only application that would be an exception is for scientific visualization, where large and dense meshes can be processed without any state change.
I'm not sure what you mean with "cache" above, but the Mach64 has a ringIs it neccessary to copy all the data then DMA it or can you pipeline it so that the DMA is writing out some of the cache while you copy data in and verify it ?
buffer with all the pending DMA buffers, so there will be DMA transfer
simultaneously with the copy/verify, but with unrelated DMA buffers.
I hope this has answered your questions. I'm still not sure what should
be the best approach here in detail after reading this thread. There seems to be a consensus regarding verifying on the source and not on the destination, but not whether verify and copy should be done at the same time or in distint steps, which relates to benefit of prefetching and/or uncached-writes (which isn't even clear if are actually a benefit
or not).
Jos� Fonseca
-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576301;v?http://www.sun.com/javavote
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
