Bug 21866

Summary: radeon-rewrite: Multitexturing failure on r250 in DRI2 codepath
Product: Mesa Reporter: Stefan Dösinger <stefandoesinger>
Component: Drivers/DRI/r200Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Stefan Dösinger 2009-05-22 03:18:23 UTC 
Multitexturing does not work correctly on r250 cards in the radeon-rewrite branch if the DRI2 codepath is enabled(KMS et al).  Any texture other than the first one returns a solid color. This happens with both GL_ATI_fragment_shader fragment processing and GL_ARB_texture_env_combine.

A small open source sample to show this issue can be found in the codesampler.com opengl demos:
http://www.codesampler.com/oglsrc/oglsrc_3.htm#ogl_multitexture
It is a Win32 app, but it runs fine in Wine, even in very old ones, so the distro Wine should be OK.

I haven't yet figured out where things go wrong, but I suspect that the texture sampling itself is correct, and the texture coordinates aren't handled properly on texture units > GL_TEXTURE0.
Comment 1 Jerome Glisse 2009-06-02 02:01:49 UTC 
I think i fixed this, do you still have multi-texture problem with dri2 on r2xx ?
Comment 2 Stefan Dösinger 2009-06-02 02:23:50 UTC 
The codesampler sample works, and the BumpUnderWater and BumpLens dx8 SDK samples work as well. BumpEart and BumpWaves still fail, but in a different way than before.

I don't know if it is still the same bug, or if it is an ATI_fragment_shader failure or a Wine regression(our ATI_fragment_shader codepath gets very little testing exposure). I'll close this bug as fixed for now and investigate the remaining issues in two weeks - I am away for WWDC for a while.
Comment 3 Stefan Dösinger 2009-06-02 03:03:09 UTC 
These problems I described may be bug 22030.
Comment 4 Adam Jackson 2009-08-24 12:32:17 UTC 
Mass version move, cvs -> git

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.