I'm trying to tie up some loose ends from the
GL_EXT_framebuffer_object work I did a while back.
I previously updated the span functions so they'd take a
gl_renderbuffer pointer and now I'm making the code actually use that
parameter. The idea is to use the fields of the gl_renderbuffer
parameter to determine where to read/write the pixels, instead of
using per-context state which is set in the SetBuffer routine.
I'm checking in the updated radeon and r200 drivers and I'll do the
mach64 and r128 drivers next. I've tested the radeon changes, but not
the r200. If someone could run the reflect demo on r200 and use the
a/s/d/f/c keys to exercise the span routines, that would be good. The
readpix and singlebuffer demos are good tests too.
In the r200 code, I've left in the old code surrounded by #ifdef 000 /
#endif to make it obvious what I changed. I'll remove the #ifdef 000
code later. It would be nice if other driver maintainers could take a
look and carry over the changes.
The basic idea is to:
1. Remove the SetBuffer() routine.
2. In the span routines, cast the gl_renderbuffer pointer into a
driRenderbuffer pointer and use its offset/pitch/cpp fields instead of
the per-context offset/pitch/cpp fields.
3. Clean-up other code related to offset/pitch/cpp elsewhere as needed.
After this is done, I can remove a bunch of unneeded code from the
swrast module.
-Brian
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
