I am trying to understand the s3tc init code as nv50 gallium has a
problem with that.
It looks like some drivers (r300g and llvmpipe) actually inits s3tc in
two places :
./src/mesa/main/texcompress_s3tc.c _mesa_init_texture_s3tc()
./src/gallium/auxiliary/util/u_format_s3tc.c
On Mon, 2010-05-03 at 01:36 -0700, Xavier Chantry wrote:
I am trying to understand the s3tc init code as nv50 gallium has a
problem with that.
It looks like some drivers (r300g and llvmpipe) actually inits s3tc in
two places :
./src/mesa/main/texcompress_s3tc.c _mesa_init_texture_s3tc()
On Mon, 2010-05-03 at 05:18 -0700, Marek Olšák wrote:
On Mon, May 3, 2010 at 1:57 PM, José Fonseca jfons...@vmware.com
wrote:
On Mon, 2010-05-03 at 01:36 -0700, Xavier Chantry wrote:
I am trying to understand the s3tc init code as nv50 gallium
has a
problem
On Mon, May 3, 2010 at 1:57 PM, José Fonseca jfons...@vmware.com wrote:
On Mon, 2010-05-03 at 01:36 -0700, Xavier Chantry wrote:
I am trying to understand the s3tc init code as nv50 gallium has a
problem with that.
It looks like some drivers (r300g and llvmpipe) actually inits s3tc in
