From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110229] The driver is not waiting the shader have finished to update the framebuffer before displaying it.
Date: Fri, 29 Mar 2019 15:43:32 +0000 [thread overview]
Message-ID: <bug-110229-502-BKluJSvkjF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110229-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 765 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #12 from Laurent <laurentduroisin@gmail.com> ---
Ok so the problem wasn't there.
It's when I bind a texture to an image or to a frame buffer objet that
sometimes that texture is not correctly updated. (Even if I don't use shaders)
I'll try to find where data are copied from the binded framebuffer object or
image but it'll be difficult in all this source code.
I really need to set breakpoints, but I don't know how to proceed with a
driver, with a library I can install it, compile it in debug mode, and settings
breakpoints with my EDI to find where it bugs, but, it's more difficult with a
driver...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1648 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-29 15:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-23 22:55 [Bug 110229] The driver is not waiting the shader have finished to update the framebuffer before displaying it bugzilla-daemon
2019-03-23 23:22 ` bugzilla-daemon
2019-03-24 8:34 ` bugzilla-daemon
2019-03-25 10:06 ` bugzilla-daemon
2019-03-25 10:06 ` bugzilla-daemon
2019-03-25 21:40 ` bugzilla-daemon
2019-03-26 0:27 ` bugzilla-daemon
2019-03-26 17:22 ` bugzilla-daemon
2019-03-26 22:09 ` bugzilla-daemon
2019-03-27 0:39 ` bugzilla-daemon
2019-03-27 17:33 ` bugzilla-daemon
2019-03-27 18:28 ` bugzilla-daemon
2019-03-29 14:23 ` bugzilla-daemon
2019-03-29 14:31 ` bugzilla-daemon
2019-03-29 15:43 ` bugzilla-daemon [this message]
2019-03-29 15:51 ` [Bug 110229] Textures binded to framebuffer objects or images are not correctly updated bugzilla-daemon
2019-03-29 21:36 ` bugzilla-daemon
2019-03-29 21:39 ` bugzilla-daemon
2019-03-30 8:11 ` bugzilla-daemon
2019-03-30 18:41 ` bugzilla-daemon
2019-03-31 3:08 ` bugzilla-daemon
2019-04-01 8:57 ` bugzilla-daemon
2019-04-01 9:11 ` bugzilla-daemon
2019-04-01 11:12 ` bugzilla-daemon
2019-04-01 11:19 ` bugzilla-daemon
2019-04-01 12:05 ` bugzilla-daemon
2019-04-01 12:20 ` bugzilla-daemon
2019-04-01 12:28 ` bugzilla-daemon
2019-04-08 13:19 ` bugzilla-daemon
2019-04-11 10:46 ` bugzilla-daemon
2019-04-11 10:47 ` [Bug 110229] glMemoryBarrier doesn't work bugzilla-daemon
2019-04-11 10:47 ` bugzilla-daemon
2019-04-11 11:31 ` bugzilla-daemon
2019-04-11 13:23 ` bugzilla-daemon
2019-04-11 13:28 ` bugzilla-daemon
2019-04-11 13:34 ` bugzilla-daemon
2019-04-11 15:00 ` bugzilla-daemon
2019-04-11 15:36 ` bugzilla-daemon
2019-04-11 15:39 ` bugzilla-daemon
2019-04-11 18:05 ` bugzilla-daemon
2019-04-12 9:53 ` bugzilla-daemon
2019-04-12 13:03 ` 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-110229-502-BKluJSvkjF@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