From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915: missing EGL_ANDROID_native_fence_sync extension
Date: Fri, 19 Oct 2018 14:02:54 +0000 [thread overview]
Message-ID: <bug-108487-502-fMuhCXUZDX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108487-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 533 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108487
--- Comment #2 from Chris Wilson <chris@chris-wilson.co.uk> ---
Just realised I missed the "timeline" part of
[17:35:45.463] warning: Disabling render GPU timeline due to missing
EGL_ANDROID_native_fence_sync extension
(read as "disabling render GPU due to missing extension").
Since it doesn't say why it doesn't create the GL context, that looks like the
easiest warning to fix first.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1475 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-10-19 14:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 17:51 [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915 bugzilla-daemon
2018-10-19 13:18 ` [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915: missing EGL_ANDROID_native_fence_sync extension bugzilla-daemon
2018-10-19 13:56 ` bugzilla-daemon
2018-10-19 14:02 ` bugzilla-daemon [this message]
2018-10-19 14:10 ` bugzilla-daemon
2018-10-19 17:00 ` bugzilla-daemon
2018-10-19 17:12 ` bugzilla-daemon
2018-10-29 10:56 ` [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915 bugzilla-daemon
2018-10-29 10:57 ` bugzilla-daemon
2018-12-04 6:46 ` bugzilla-daemon
2018-12-04 6:59 ` bugzilla-daemon
2018-12-04 11:13 ` bugzilla-daemon
2018-12-04 13:23 ` bugzilla-daemon
2018-12-05 19:47 ` bugzilla-daemon
2018-12-10 8:36 ` bugzilla-daemon
2019-01-31 3:02 ` bugzilla-daemon
2019-01-31 18:25 ` bugzilla-daemon
2019-03-09 14:18 ` bugzilla-daemon
2019-03-09 14:21 ` bugzilla-daemon
2019-04-27 23:33 ` bugzilla-daemon
2019-05-13 2:23 ` bugzilla-daemon
2019-05-16 14:14 ` 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-108487-502-fMuhCXUZDX@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;
as well as URLs for NNTP newsgroup(s).