dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93648] Random lines being rendered when playing Dolphin on radeonsi (w/ apitrace)
Date: Sat, 09 Jan 2016 18:15:22 +0000	[thread overview]
Message-ID: <bug-93648-502-4cUKY7CwyS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93648-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 486 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93648

--- Comment #1 from Pierre Bourdon <delroth@gmail.com> ---
Someone on IRC just reported something that sounds like the same issue, but on
r600.

It's likely that this issue comes from geometry shaders, which we are using to
generate stripes from lines. Disabling the use of geometry shaders breaks some
features in Dolphin but fixes that particular problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1301 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

  reply	other threads:[~2016-01-09 18:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09 16:49 [Bug 93648] Random lines being rendered when playing Dolphin on radeonsi (w/ apitrace) bugzilla-daemon
2016-01-09 18:15 ` bugzilla-daemon [this message]
2016-01-16  8:17 ` bugzilla-daemon
2016-01-16  8:36 ` [Bug 93648] Random lines being rendered when playing Dolphin (geometry shaders related, w/ apitrace) bugzilla-daemon
2016-01-16 10:31 ` bugzilla-daemon
2016-01-20 15:14 ` bugzilla-daemon
2016-01-22 22:59 ` bugzilla-daemon
2016-01-25 15:23 ` 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-93648-502-4cUKY7CwyS@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