From: Alexander Kanavin <alex.kanavin@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 05/13] weston-init: use the drm/kms backend rather than fbdev one for qemux86 machines
Date: Wed, 19 Feb 2020 20:47:44 +0100 [thread overview]
Message-ID: <20200219194752.7967-5-alex.kanavin@gmail.com> (raw)
In-Reply-To: <20200219194752.7967-1-alex.kanavin@gmail.com>
The fbdev backend is not documented, and not the default;
as the emulated hardware in qemu now supports DRM/KMS
(both std and virtio), we should align with upstream default
and vast majority of users. Empty init file will cause
weston to default to the KMS backend.
Note that 3D acceleration via virgl is not required; the backend
renders fine via the software driver in mesa. However, kvm
is more or less required to keep the UI responsive.
Also, other qemu targets (mips and arm in particular) continue
to use the fbdev backend, as in the absence of kvm, the performance
of software GL paths falls to unacceptable level.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
---
meta/recipes-graphics/wayland/weston-init/qemux86-64/weston.ini | 0
meta/recipes-graphics/wayland/weston-init/qemux86/weston.ini | 0
2 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-graphics/wayland/weston-init/qemux86-64/weston.ini
create mode 100644 meta/recipes-graphics/wayland/weston-init/qemux86/weston.ini
diff --git a/meta/recipes-graphics/wayland/weston-init/qemux86-64/weston.ini b/meta/recipes-graphics/wayland/weston-init/qemux86-64/weston.ini
new file mode 100644
index 0000000000..e69de29bb2
diff --git a/meta/recipes-graphics/wayland/weston-init/qemux86/weston.ini b/meta/recipes-graphics/wayland/weston-init/qemux86/weston.ini
new file mode 100644
index 0000000000..e69de29bb2
--
2.25.0
next prev parent reply other threads:[~2020-02-19 19:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:47 [PATCH 01/13] core-image-sato-sdk-ptest: do not pull in ptest-pkgs Alexander Kanavin
2020-02-19 19:47 ` [PATCH 02/13] webkitgtk: x11 and wayland are not mutually exclusive Alexander Kanavin
2020-02-23 13:02 ` Adrian Bunk
2020-02-23 13:05 ` Alexander Kanavin
2020-02-23 14:38 ` Adrian Bunk
2020-02-19 19:47 ` [PATCH 03/13] webkitgtk: unbreak wayland build Alexander Kanavin
2020-02-19 23:52 ` Richard Purdie
2020-02-19 19:47 ` [PATCH 04/13] wayland: convert to meson build Alexander Kanavin
2020-02-20 16:21 ` Joshua Watt
2020-02-20 16:38 ` Alexander Kanavin
2020-02-19 19:47 ` Alexander Kanavin [this message]
2020-03-12 20:54 ` [PATCH 05/13] weston-init: use the drm/kms backend rather than fbdev one for qemux86 machines Khem Raj
2020-02-19 19:47 ` [PATCH 06/13] qemumips: use std vga instead of cirrus vga Alexander Kanavin
2020-02-19 19:47 ` [PATCH 07/13] createrepo-c: upgrade 0.15.5 -> 0.15.7 Alexander Kanavin
2020-02-19 19:47 ` [PATCH 08/13] epiphany: upgrade 3.34.3.1 -> 3.34.4 Alexander Kanavin
2020-02-19 19:47 ` [PATCH 09/13] libsecret: upgrade 0.20.0 -> 0.20.1 Alexander Kanavin
2020-02-19 19:47 ` [PATCH 10/13] meson: upgrade 0.53.0 -> 0.53.1 Alexander Kanavin
2020-02-19 19:47 ` [PATCH 11/13] p11-kit: upgrade 0.23.18.1 -> 0.23.20 Alexander Kanavin
2020-02-20 10:26 ` Richard Purdie
2020-02-19 19:47 ` [PATCH 12/13] vala: upgrade 0.46.5 -> 0.46.6 Alexander Kanavin
2020-02-19 19:47 ` [PATCH 13/13] virglrenderer: upgrade 0.8.1 -> 0.8.2 Alexander Kanavin
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=20200219194752.7967-5-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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