From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108487] Wayland compositors are unable to use hardware acceleration on i915
Date: Tue, 04 Dec 2018 13:23:14 +0000 [thread overview]
Message-ID: <bug-108487-502-SZXH88H2b2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108487-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 955 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108487
--- Comment #10 from Pekka Paalanen <ppaalanen@gmail.com> ---
(In reply to magiblot from comment #9)
> The workaround dismisses the error message but, unfortunately, doesn't
> enable hardware acceleration
Yes, the whole point of --use-pixman is to use Pixman software rendering which
will be faster than GL with a software renderer. If anything, it will disable
hardware acceleration for the compositor and apps.
It is used to get something on screen, when hardware acceleration doesn't work
for any reason.
Daniel's guess in comment #3 is still the best guess here.
One thing to test to confirm would be to hack Weston's build so that
HAVE_GBM_MODIFIERS will not get defined. If that works, then we know that using
gbm_surface_create_with_modifiers() does not work while gbm_surface_create()
works.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1891 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-12-04 13:23 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
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 [this message]
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-SZXH88H2b2@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