Bug 28184

Summary: [bisected] oglc case pxconv-gettex.c/pxstore-gettex.c/pxtrans-gettex.c regressed(on mesa master branch)
Product: Mesa Reporter: fangxun <xunx.fang>
Component: Drivers/DRI/i965Assignee: Eric Anholt <eric>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: high    
Version: unspecified   
Hardware: All   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description fangxun 2010-05-20 03:25:51 UTC
System Environment:
--------------------------
machines: piketon, G45, Pineview
Libdrm:   (master)a3305b076c005e0d3bd55da0214e91413cf65b48
Mesa:		(master)5a5a82d7e88c2971acad026b94e90588b2367a22
Xserver:	(master)673eb707ce6737284c4886265ba149c5587a74e2
Xf86_video_intel: (master)509df27c7401e96d3062890da73f6af6629adef4
Kernel:		v2.6.34


Bug detailed description:
-------------------------
This issue happens on mesa master branch. Bisect show following commit brings in this issue:
commit 7554b83a21bd62b20df5a7327b69f08108ac9ab6
Author: Eric Anholt <eric@anholt.net>
Date:   Thu May 13 14:48:13 2010 -0700

    intel: Handle arbitrary compressed formats in intel_compressed_num_bytes.

    Note that we don't support arbitrary block size for compressed quite
    yet -- block height of 4 is hard-coded all over the place.

    Bug #27098 (srgb dxt1 producing a bytes per pixel of 0).
Comment 1 fangxun 2010-05-24 02:14:35 UTC
This issue still happens on mesa master branch.
Comment 2 Eric Anholt 2010-06-04 12:47:05 UTC
commit 18a6e5ee73c5cef283c6bef906e5f8e4f60d4000
Author: Eric Anholt <eric@anholt.net>
Date:   Fri Jun 4 12:43:15 2010 -0700

    intel: Fix intel_compressed_num_bytes for FXT1 after I broke it.
    
    Fixes piglit fxt1-teximage since
    7554b83a21bd62b20df5a7327b69f08108ac9ab6, and also OGLC tests that hit
    FXT1 with a million other things.
    
    Bug #28184.
Comment 3 fangxun 2010-06-08 19:04:13 UTC
Works well, mark it as verified.

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.