As I mentioned in a couple earlier threads, there are some problems with enabling this extension in a couple different drivers. Because of that I have not committed any device-dependent code. Attached to this message are the patches to the Radeon and MGA drivers to enable SGI_make_current_read. I expect similar patches will be needed for the other drivers. The MGA patch seems okay, but I have not had a chance to test it much. The Radeon patch has several problems with both xdemos/wincopy from Mesa and my patched glxgears (see the previous thread for that patch).
I took a quick at this problem again last night. I'm a bit confused by spantmp.h and how it interacts with Mesa. The generated functions get used, for example, by _mesa_read_rgba_span. This function gets used in all the expected places: CopyTexImage, ReadPixels, etc. However, it also gets used by _mesa_blend_span and a few other places that use the ctx->DrawBuffer.
The problem is that the information about which buffer is needed (i.e., read or draw) is NOT passed into swrast->Driver.ReadRGBASpan. How does even the software rasterizer work correctly? Won't there be problems with alpha blending if the read-drawable is set to something different from the draw-drawable?
------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
