Bug 18992 - [i965 gem] glsl demo twoside fails
Summary: [i965 gem] glsl demo twoside fails
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Ian Romanick
QA Contact:
Depends on:
Reported: 2008-12-09 23:42 UTC by lin, jiewen
Modified: 2009-09-18 00:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

screenshot (16.91 KB, image/png)
2008-12-09 23:42 UTC, lin, jiewen
log (46.02 KB, application/octet-stream)
2008-12-09 23:44 UTC, lin, jiewen
conf (3.76 KB, application/octet-stream)
2008-12-09 23:44 UTC, lin, jiewen
twoside_after_presskb (35.21 KB, image/png)
2009-03-18 20:07 UTC, zhao jian
screenshot of mesa/progs/glsl twoside (2.63 KB, image/png)
2009-06-05 00:50 UTC, Yifei Chen

Note You need to log in before you can comment on or make changes to this bug.
Description lin, jiewen 2008-12-09 23:42:12 UTC
Created attachment 20976 [details]

System Environment:

--Platform: 965
--Architecture(32-bit,64-bit,compatiblity): 32-bit
--2D driver: (xf86-video-intel-2.6-branch)                                      6ca0d7e6ff05bff2bb88bfae64c2d79ac115bd38
--3D driver: (intel-2008-q4)154a9e5317f890618932cea0129ef887e16baf84
--DRM:shipped with kernel 2.6.28-rc6 for-airlied
--libdrm: (master)c99566fb810c9d8cae5e9cd39d1772b55e2f514c
--Xserver: (server-1.6-branch)b268458eab2f213ec14dfe8013aa714c187e3aab
--Kernel: 2.6.28-rc6 for-airlied

Bug detailed description:
start X and twoside, the display is not correct. Details could be got in the attachment screenshot.

Reproduce steps:
1. xinit &
2. ./twoside
Comment 1 lin, jiewen 2008-12-09 23:44:31 UTC
Created attachment 20977 [details]
Comment 2 lin, jiewen 2008-12-09 23:44:47 UTC
Created attachment 20978 [details]
Comment 3 Gordon Jin 2008-12-10 05:12:58 UTC
The case is under mesa/progs/glsl/
Comment 4 lin, jiewen 2009-01-16 00:24:16 UTC
This issue still eixsts with current build.
Comment 5 zhao jian 2009-03-18 19:59:45 UTC
It still existed on G45-64 with the latest code. When it start it will be same with that screenshot attached bu jiewen. But if I press the keyboard, it will have two colors shown but in the wrong place(shown as the picture I attached). The configuration is : 
Kernel_version:         2.6.29-rc7
Libdrm:         (master)2e2e8575b1ed4703653a72ac2b60b75316c388d7
Mesa:            (mesa_7_4_branch)a8528a2e8653b5237c1d1d66fe98c6e031d007f9
Xserver:         (server-1.6-branch)60c161545af80eb78eb790a05bde79409dfdf16e
Xf86_video_intel:      (2.7)238c2c40afd9f8b61479b8640d53f20d52fd7ddf
Kernel:       (for-airlied)dc529a4fe1ae4667c819437a94185e8581e1e680
Comment 6 zhao jian 2009-03-18 20:07:08 UTC
Created attachment 24023 [details]
Comment 7 Yifei Chen 2009-06-05 00:48:17 UTC
twoside works better now, but it still do not rendered correctly, see attachment for screenshot.
Comment 8 Yifei Chen 2009-06-05 00:50:22 UTC
Created attachment 26454 [details]
screenshot of mesa/progs/glsl twoside
Comment 9 Eric Anholt 2009-08-04 18:24:00 UTC
commit 78c022acd0b37bf8b32f04313d76255255e769c1
Author: Eric Anholt <eric@anholt.net>
Date:   Tue Aug 4 18:02:31 2009 -0700

    i965: Respect CondSwizzle in OPCODE_IF.
    Fixes piglit glsl-vs-if-bool and progs/glsl/twoside, and will likely be
    useful for the looping code.
    Bug #18992

commit 7007f8b352763af89805f287153cb7972bff0523
Author: Eric Anholt <eric@anholt.net>
Date:   Tue Aug 4 14:13:27 2009 -0700

    i965: Emit conditional code updates as required for GLSL VS if statements.
    Previously, we'd be branching based on whatever condition code happened to b
    laying around.

Comment 10 fangxun 2009-09-18 00:16:21 UTC
Verified with following commints:
Libdrm:  (master)cdd325b59a17a614b90fc2f8b388175e6d79e3cf
Mesa:    mesa_7_6_branch)fac38e8c8f1814ae54703b872db8c6dd21c34a3b
Xserver:   (server-1.6-branch)3044711412d0a08ba65a491bd2441c0c8980f5e2
Xf86_video_intel: (master)b8c5c996e888485c3a16d645c8490592534a7882
Kernel: (master)74fca6a42863ffacaf7ba6f1936a9f228950f657

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.