From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61419] New: r600g: No OpenGL Core 3.1 available on Cayman
Date: Mon, 25 Feb 2013 02:10:15 +0000 [thread overview]
Message-ID: <bug-61419-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1001 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=61419
Priority: medium
Bug ID: 61419
Assignee: dri-devel@lists.freedesktop.org
Summary: r600g: No OpenGL Core 3.1 available on Cayman
Severity: normal
Classification: Unclassified
OS: All
Reporter: alexandre.f.demers@gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 75469
--> https://bugs.freedesktop.org/attachment.cgi?id=75469&action=edit
glxinfo, no OpenGL Core 3.1
According to docs/GL3.txt, it should be possible to create an OpenGL Core 3.1.
Latest glxinfo doesn't report it.
GL_ARB_texture_buffer_object is not reported.
GL_ARB_uniform_buffer_object is reported.
If I understand correctly, without TBO extension, there is no GLSL 1.40 and
thus no OpenGL Core 3.1.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2447 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:[~2013-02-25 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 2:10 bugzilla-daemon [this message]
2013-02-25 2:13 ` [Bug 61419] r600g: No OpenGL Core 3.1 available on Cayman bugzilla-daemon
2013-02-25 8:54 ` bugzilla-daemon
2013-02-25 10:06 ` bugzilla-daemon
2013-02-25 15:16 ` bugzilla-daemon
2013-02-26 5:37 ` bugzilla-daemon
2013-03-06 3:15 ` 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-61419-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.