From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110229] glMemoryBarrier doesn't work.
Date: Fri, 12 Apr 2019 13:03:11 +0000 [thread overview]
Message-ID: <bug-110229-502-8I5YFZ2iMw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110229-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1354 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #35 from Laurent <laurentduroisin@gmail.com> ---
(In reply to Andre Klapper from comment #34)
> Right. And we cannot waste time going through your custom code if you do not
> provide a minimal self-contained test case.
Ok next time I'll provide a test case, anyway, I'll have to do this, because,
I've a lot of bugs (or crash) with new opengl features. (From opengl 3.3 to
opengl 4.4 (opengl 4.5 with GL_ARB_bindless_texture is not supported by my GPU)
but normally (I've the specs of my GPU here), all functionalities until opengl
4.4 should be supported)
This is why my shader version is 140 and not 330.
On windows I've a driver which runs opengl 3.3 without any problems but it's an
old driver and some shaders doesn't seems to run properly, and most of all,
only opengl 4.1 is supported by this driver, and the driver on amd website
doesn't work too I had to doawnload the driver on the asus website.
And I haven't the bases to code a simple driver by myself. (Even if I have the
technical specifications of the r600 GPU here, as far as I don't have a simple
tutorial to simply run a basic shader to display something without passing by
opencl which is not supported by my GPU)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2230 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
prev parent reply other threads:[~2019-04-12 13:03 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
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 [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-110229-502-8I5YFZ2iMw@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