https://bugs.freedesktop.org/show_bug.cgi?id=93216
Axel Davy changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.freedesktop.org/show_bug.cgi?id=93216
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
---
https://bugs.freedesktop.org/show_bug.cgi?id=93216
--- Comment #6 from Bas Nieuwenhuizen ---
Does the series available at
https://patchwork.freedesktop.org/series/8048/
fix this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=93216
--- Comment #5 from Bas Nieuwenhuizen ---
I think we have cache coherency issues within a single draw call. One of the
situations in which a feedback loop is allowed is if we read and write every
texel at most once and we read the texel from the
https://bugs.freedesktop.org/show_bug.cgi?id=93216
--- Comment #4 from Axel Davy ---
I added these at the end of si_emit_draw_packets.
It doesn't solve the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=93216
--- Comment #3 from Marek Olšák ---
What happens if you set these flush flags after every draw call?
SI_CONTEXT_FLUSH_AND_INV_FRAMEBUFFER
SI_CONTEXT_INV_GLOBAL_L2
SI_CONTEXT_INV_VMEM_L1
SI_CONTEXT_PS_PARTIAL_FLUSH
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=93216
Axel Davy changed:
What|Removed |Added
Attachment #120280|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=93216
--- Comment #1 from Axel Davy ---
Created attachment 120281
--> https://bugs.freedesktop.org/attachment.cgi?id=120281=edit
After a buggy draw call
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=93216
Bug ID: 93216
Summary: Artifacts with DCC when render target also texture
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal