From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 82253] JanusVR Browser rendering misses floors on radeonsi, works on intel
Date: Thu, 07 Aug 2014 06:11:16 +0000 [thread overview]
Message-ID: <bug-82253-502-krkPZVPCMP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-82253-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 919 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=82253
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
|.org |org
Component|Drivers/Gallium/radeonsi |Mesa core
--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
Could be an issue in st/mesa or other driver-independent Gallium code then.
Does glretrace also report a few OpenGL API errors like these on intel?
5946: message: major api error 1: GL_INVALID_OPERATION in Inside glBegin/glEnd
5947 @0 glTranslatef(x = 2.000085, y = 0, z = 0)
5947: warning: glGetError(glTranslatef) = GL_INVALID_OPERATION
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2422 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-08-07 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 15:01 [Bug 82253] New: JanusVR Browser rendering misses floors on radeonsi, works on intel bugzilla-daemon
2014-08-06 23:02 ` [Bug 82253] " bugzilla-daemon
2014-08-06 23:12 ` bugzilla-daemon
2014-08-06 23:13 ` bugzilla-daemon
2014-08-07 6:11 ` bugzilla-daemon [this message]
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-82253-502-krkPZVPCMP@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