Brian,
I'm wondering if there isn't some way to rationalize the multiple
sp_quad stages that each individually readback the current framebuffer
values for use within the stage.
At the moment that looks like:
- blend
- colormask
- final write (masked case)
It seems like reading the values once and carrying them along the
pipeline would be a good strategy *except* for the fast path of
non-masked, non-blended full quad writes. Perhaps there should be
something like:
- early write stage (write & terminate pipeline if mask == 0xf)
- framebuffer readback
- blend
- colormask
- masked-copy (to apply quad->mask)
- late write stage.
Similarly for Z, stencil, early-z-test, etc, it might make sense to read
the framebuffer Z/stencil values at an early point and carry them along
with the quad...
Keith
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
