Oh, I forgot the rationale:
1. I think we are heading towards a reality where some kind of working
GL is a 'must' for any kind of UI work.
2. Typically people build images and then transfer them to the NUC or
even target boards for testing - using qemu would be less awkward.
3. Current qemu configuration is basically useless here.
Alex
On Mon, 14 Jan 2019 at 16:03, Alexander Kanavin wrote:
>
> 0. TLDR:
>
> $ . oe-init-build-env build-virgl
> $ bitbake core-image-sato-sdk
> $ runqemu kvm gl
> $$ run glxgears or any other GL-capable binary inside qemu
>
> 1. qemu is switched over to use gtk frontend. I simply couldn't get SDL
> frontend to work properly, it only displays a blank black window or doesn't
> start at all. Same thing happens with qemu binaries provided by Fedora and
> opensuse (Ubuntu's qemu lacks virgl support). Seems like SDL support has
> regressed.
>
> 2. While the components are built against the most minimum necessary
> mesa-native set (gbm, egl, dri with no drivers), libepoxy loads and uses the
> host GL implementation (through a chrpath hack). This is both to save build
> times, and because the host is likely to have a set of drivers more
> appropriate for the physical machine (e.g. proprietary nvidia stack,
> although I didn't test that).
>
> 3. I tested this with
> - glamor X server
> - weston compositor with drm backend (build core-image-weston, then edit
> weston.ini in the image to use drm backed instead of fbdev).
> - kmscube
> - glxgears
> - https://www.geeks3d.com/gputest/
>
> The latter two show FPS that is similar to running them directly on the host.
>
> 4. Some things I am not sure about:
>
> - how much of a 'default' should this be for running qemu. It works for me,
> but other people might find it less stable compared to the existing
> sdl-vmware-swrast setup.
>
> - what other tests and demos could be run
>
> - how could this be tested on the autobuilder. I wrote an oe-selftest for
> this, but it does require an X session, and ability to create opengl
> contexts on the host.
>
> The following changes since commit 0c9f6e9bb18b2a52b5a5e828772a9619ee4d8515:
>
> strace: add lost Upstream-Status (2019-01-14 11:49:07 +)
>
> are available in the Git repository at:
>
> git://git.yoctoproject.org/poky-contrib akanavin/virgl-gtk
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=akanavin/virgl-gtk
>
> Alexander Kanavin (23):
> gtk+3: enable native/nativesdk variant
> gtk+3: remove the gtk-icon-utils-native recipe
> shared-mime-info: update the database also in native builds
> gtk+: drop support for choosing between 2.x and 3.x implementations of
> gtk-update-icon-cache
> pixbufcache.bbclass: remove a dependency loop introduced by enabling
> gtk+3-native
> meta: add native and nativesdk variants to various recipes to enable
> gtk+3-native/nativesdk
> libepoxy: enable native/nativesdk variants
> mesa: enable native and nativesdk variants
> virglrenderer: add a recipe
> qemu: enable virglrenderer and glx options for native/nativesdk builds
> qemu: drop --with-gtkabi option, as it is no longer supported
> mesa-gl: do not enable nativesdk variant to avoid clashes with main
> mesa recipe
> local.conf.sample: adjust the qemu config to enable gtk+ instead of
> sdl
> qemu: build target variant with gtk+, and nativesdk variant without
> sdl
> qemu: remove support for building against host sdl
> atk: disable gobject-introspection for nativesdk
> qemu: add a gettext-native dependency
> libjpeg-turbo: fix nativesdk build in same way as native builds are
> qemu: add a patch to avoid a missing include error
> runqemu: add support for virgl GL acceleration
> runqemu: do not check for GL libraries
> qemu: add environment variable wrappers to make qemu look good with
> gtk frontend
> selftest: add a test for virgl GL acceleration
>
> meta-poky/conf/local.conf.sample | 10 +-
> meta-selftest/lib/oeqa/runtime/cases/virgl.py | 17 +++
> meta/classes/pixbufcache.bbclass | 2 +-
> meta/conf/machine/include/qemuboot-x86.inc| 2 +-
> meta/lib/oeqa/selftest/cases/runtime_test.py | 19
> meta/recipes-devtools/qemu/qemu.inc | 40 ---
> .../qemu/0001-Add-a-missing-X11-include.patch | 23
> meta/recipes-devtools/qemu/qemu_3.1.0.bb | 1 +
> .../gdk-pixbuf/gdk-pixbuf_2.36.11.bb | 2 +-
> .../gnome/adwaita-icon-theme_3.28.0.bb| 2 +
> meta/recipes-gnome/gtk+/gtk+.inc | 5 +-
> meta/recipes-gnome/gtk+/gtk+3.inc | 29 +++--
> .../gtk+/gtk-icon-utils-native_3.22.30.bb | 63 ---
> ...endency-from-gtk-encode-symbolic-svg.patch | 102 --
> .../hicolor-icon-theme_0.17.bb| 2 +
> meta/recipes-graphics/cairo/cairo_1.14.12.bb | 2 +-
> .../harfbuzz/harfbuzz_2.2.0.bb| 2 +-
> .../jpeg/libjpeg-turbo_2.0.1.bb | 3 +-
>
