Bug 48702 - copypix demo not working correctly on nv43
Summary: copypix demo not working correctly on nv43
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-14 15:16 UTC by Andrew Randrianasulu
Modified: 2012-04-15 05:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
with LLVMpipe (653.34 KB, image/png)
2012-04-14 15:17 UTC, Andrew Randrianasulu
Details
with nouveau (462.61 KB, image/png)
2012-04-14 15:19 UTC, Andrew Randrianasulu
Details

Description Andrew Randrianasulu 2012-04-14 15:16:58 UTC
Same setup as in bug 48701:

kernel: commit 965a47fb8ec0a72324aad8b9c0bd1c8b98cc7ca1 (3.4.0-rc2 nouveau,
master branch up to "drm/nouveau/bios: fix regression on some nv4x board")

mesa: commit b2df031a959f36743527b9abc89913ce4f895de3 ("r300/compiler: Fix
nested flow control in r500 vertex shaders")

libdrm: master branch commit 292da616fe1f936ca78a3fa8e1b1b19883e343b6
("nouveau: pull in major libdrm rewrite")

ddx: master up to commit fb3a36b1e5af0f81bb266da894d3442eed8e4e55 ("nve0:
initial exa/xv acceleration for kepler chipsets")

X server - 1.10.4

Hardware:
01:00.0 VGA compatible controller: NVIDIA Corporation NV43 [GeForce 6600 GT]
(rev a2) - AGP version.

trying copypix mesa demo i see difference between llvmpipe and nouveau/gallium drivers. See screenshots.
Comment 1 Andrew Randrianasulu 2012-04-14 15:17:51 UTC
Created attachment 59997 [details]
with LLVMpipe

LIBGL_ALWAYS_SOFTWARE=1 was set
Comment 2 Andrew Randrianasulu 2012-04-14 15:19:09 UTC
Created attachment 59998 [details]
with nouveau

Note black bars
Comment 3 Ben Skeggs 2012-04-15 05:14:55 UTC
Thanks for the report, should be fixed in mesa commit 29128e5ee20b198ebedf0ff979d96c78ad264b8f.


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.