The reason I am asking is that R300 appears to support all (or almost all)
GL texture formats and it would not be too difficult to add this support,
but we are using R200 switch() due to lack of understanding of Mesa->driver interface.
Well, even if the hardware does support all the present Mesa texture formats doesn't mean you _have_ to use them all.
The end user isn't really going to care.
Is there no penalty for format conversion ?
Sure there is, but it varies. If the user specifies his texture images as GL_RGB/GL_FLOAT and the hardware texture format chosen is
_mesa_texformat_argb155, clearly, there's going to be a cost to doing the conversion.
In some cases, however, the "conversion" can be done with memcpy(). For example, if the incoming image is GL_UNSIGNED_INT_8_8_8_8/GL_RGBA and the chosen hardware format is _mesa_texformat_rgba8888, the memcpy_texture() texture routine will be used. See texstore.c.
Mesa's texture conversion functions also handle all the GL_UNPACK_* parameters, color table lookup, scale and biasing, convolutions, etc.
-Brian
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
