From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36131] New: r600: unknown param 45 (PIPE_CAP_VERTEX_COLOR_CLAMP_CONTROL)
Date: Mon, 11 Apr 2011 05:16:21 -0700 (PDT) [thread overview]
Message-ID: <bug-36131-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36131
Summary: r600: unknown param 45
(PIPE_CAP_VERTEX_COLOR_CLAMP_CONTROL)
Product: Mesa
Version: git
Platform: All
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: b.bellec@gmail.com
Since some days I get an error each time I run the GL stack (3D apps or glxinfo
for instance)
I am on Fedora 15, kernel 2.6.39-rc2, Mesa git (happens also with the Mesa
packaged for F15).
The error is :
EE r600_pipe.c:431 r600_get_param - r600: unknown param 45
For instance :
$ glxinfo | grep "OpenGL version string"
EE r600_pipe.c:431 r600_get_param - r600: unknown param 45
OpenGL version string: 2.1 Mesa 7.11-devel (git-a26121f)
Brian Paterni (https://bugs.freedesktop.org/show_bug.cgi?id=35434) looks at the
code, it seems that '45' is mapped to PIPE_CAP_FRAGMENT_COLOR_CLAMP_CONTROL.
Perhaps this is related to this recent patch
http://lists.freedesktop.org/archives/mesa-dev/2011-March/006218.html (gallium:
remove PIPE_CAP_VERTEX_COLOR_CLAMP_CONTROL)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-11 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 12:16 bugzilla-daemon [this message]
2011-04-11 12:49 ` [Bug 36131] r600: unknown param 45 (PIPE_CAP_VERTEX_COLOR_CLAMP_CONTROL) bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-36131-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox