From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92236] [ColorTiling2D] R600 BARTS radeon: pipe_context->clear with color tiling enabled doesn't immediately affect color buffer
Date: Fri, 02 Oct 2015 08:04:01 +0000 [thread overview]
Message-ID: <bug-92236-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1180 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92236
Bug ID: 92236
Summary: [ColorTiling2D] R600 BARTS radeon: pipe_context->clear
with color tiling enabled doesn't immediately affect
color buffer
Product: Mesa
Version: git
Hardware: x86 (IA32)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: siro@das-labor.org
QA Contact: dri-devel@lists.freedesktop.org
There's an open Gallium nine bug: https://github.com/iXit/Mesa-3D/issues/138
It looks like pipe_context->clear called with PIPE_CLEAR_COLOR isn't applied
immediately to the buffer.
As nine mimics swap-chains, the buffer is reused after some frames resulting in
"delayed" presentation.
The problem doesn't exist with R600_DEBUG=notiling and it doesn't exists when
using pipe_context->clear_render_target instead.
Tested with mesa git: https://github.com/iXit/Mesa-3D/
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2638 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
next reply other threads:[~2015-10-02 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 8:04 bugzilla-daemon [this message]
2015-10-02 8:16 ` [Bug 92236] [ColorTiling2D] R600 BARTS radeon: pipe_context->clear with color tiling enabled doesn't immediately affect color buffer 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-92236-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.