On 05/08/2013 08:06 PM, Eric Anholt wrote: > Tapani Pälli <tapani.pa...@intel.com> writes: > >> Patch makes sure in conservative way that the depth_clear_value >> is correct and represents max depth of current depth buffer. >> >> This fixes the case where user has 16bit color buffer but 24bit >> depth buffer and 'fb->_DepthMax' has a wrong value. I'm currently >> investigating how to get _DepthMax corrected on mesa side, but >> meanwhile this patch will enable correct rendering results for >> 16bit benchmarks instead of displaying only white color on the >> screen. This bug does not happen with user created framebuffers, >> only with window system ones. > > _DepthMax should actually get fixed, instead. _DepthMax should have > nothing to do with color bits per pixel. >
Yes I agree, I'm investigating the root cause in framebuffer renderbuffer mgmt. I know color buffer depth should not matter here but that is basically the environment where bug is currently reproduced. // Tapani
signature.asc
Description: OpenPGP digital signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
