Philipp Klaus Krause wrote:
> Ian Romanick schrieb:
> 
>> There are two separate commits.  One increases the maximum texture size
>> in the i965 driver.  The other increases the size of internal data
>> structures used to track mipmaps.  The second patch works by changing
>> the value of MAX_TEXTURE_LEVELS since this define is used to size the
>> arrays.  This define is also used to set the default value of
>> ctx->Const.MaxTextureLevels.  The r300 driver was assuming that the
>> default value of MaxTextureLevels (perviously 12) was the correct value.
>>  When the default value of MaxTextureLevels increased to 13, the r300
>> driver apparently broke.
> 
> Why wasn't it increased to at least 14? Newer hardware (e.g. R600, R700)
> can do 8192x8192 textures, so it'll be needed soon anyway.

Each time we bump up the max texture size it means we also increase the max 
drawing surface size (render to texture and all that).  One consequence of this 
is the fixed point arithmetic in the swrast triangle code may start failing.  
There's comments in the code about it.  It also means various internal buffers 
will double in size.

It's not a huge deal, but some testing needs to be done.  I really need to 
write a glean test that exercises max-sized textures/FBOs...

-Brian

------------------------------------------------------------------------------
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to