From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72198] New: driDriverGetExtensions_r600 not implemented
Date: Sun, 01 Dec 2013 16:07:46 +0000 [thread overview]
Message-ID: <bug-72198-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1301 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72198
Priority: medium
Bug ID: 72198
Assignee: dri-devel@lists.freedesktop.org
Summary: driDriverGetExtensions_r600 not implemented
Severity: enhancement
Classification: Unclassified
OS: All
Reporter: i.gnatenko.brain@gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
$ DRI_PRIME=1 LIBGL_DEBUG=verbose glxinfo64
name of display: :0
libGL: OpenDriver: trying /usr/lib64/dri/tls/r600_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/r600_dri.so
libGL: driver does not expose __driDriverGetExtensions_r600():
/usr/lib64/dri/r600_dri.so: undefined symbol: __driDriverGetExtensions_r600
libGL: Can't open configuration file /home/carasin/.drirc: No such file or
directory.
libGL: Can't open configuration file /home/carasin/.drirc: No such file or
directory.
display: :0 screen: 0
direct rendering: Yes
[snipped]
I think could be good if we will have implemented this func.
Found about the same funcs for intel:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=1925a9aebd64b2e08574118891394d9d56db25ae
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2704 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-12-01 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 16:07 bugzilla-daemon [this message]
2013-12-03 1:31 ` [Bug 72198] driDriverGetExtensions_r600 not implemented 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-72198-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.