The (new) piglit test fp-fog shows this bug. The fragment.fogcoord state variable is supposed to contain {f, 0, 0, 1}. On 965 it seems to be getting {f, 1, GARBAGE, 0}. See the output from fp-fog: GL_RENDERER = Mesa DRI Intel(R) 965GM GEM 20080716 0.5, 1.5 => { 0.298039 1.000000 0.000000 0.000000 } 1.5, 1.5 => { 0.600000 1.000000 0.000000 0.000000 } 0.5, 0.5 => { 0.800000 1.000000 0.082353 0.000000 } 1.5, 0.5 => { 0.400000 1.000000 0.000000 0.000000 }
commit 411d913ccea362dbd75411266d7abb685214ee93 Author: Eric Anholt <eric@anholt.net> Date: Mon Mar 23 22:35:03 2009 -0700 i965: Fix fog coordinate g,b,a values when glFrontFacing isn't used. Previously, we would sample (f,glFrontFacing,undef,undef) instead of the (f,0,0,1) that fragment.fogcoord is supposed to return. Due to glFrontFacing's presence in FOGC.y, we'll still give bad results there when glFrontFacing is used. Bug #19122, piglit testcase fp-fog.
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.