Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 08 Dec 2018 22:37:53 +0100
From:      Jan Beich <jbeich@FreeBSD.org>
To:        Kevin Oberman <rkoberman@gmail.com>
Cc:        greg@unrelenting.technology, yuripv@yuripv.net, "freebsd-x11\@freebsd.org" <x11@freebsd.org>
Subject:   Re: [CFT] Mesa 18.3.0 update (mesa-libs, mesa-dri, libosmesa, clover)
Message-ID:  <va43-r972-wny@FreeBSD.org>
References:  <wool-v81e-wny@FreeBSD.org> <790ba1cb-7251-e8b3-f7a3-6de3cdee9958@yuripv.net> <8t11-v5xg-wny@FreeBSD.org> <CAN6yY1ukNSMR%2B%2B=XqHAOHx6akvXu3_u4mi2iuu0DOX_5gsoHNg@mail.gmail.com> <1544292716.1907.0@smtp.migadu.com> <CAN6yY1ukNWYsw8-McDN3pvVgao3ZJtkde2mVK-Lb42b16wUXow@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Oberman <rkoberman@gmail.com> writes:

> As far as firefox is concerned, I tried running it with the "MOZ" variables
> Jan listed, but I still got the same status message in about:support. I
> also looked though about:config for relevant settings, but came up blank.

That's expected. Environment variables override hardware qualifications.
Whether WebRender is actually in-use is decided by Compositing field.
WebRender (like WebGL 2) requires OpenGL 3.2+ which SandyBridge supports.
If it fails you'd see "unavailable by runtime: WebRender initialization failed".

  $ MOZ_ACCELERATED=1 MOZ_WEBRENDER=1 firefox --new-instance --profile $(mktemp -dt ffprofile) about:support
  [...]
  Features
  ------------------------------------------------------------------------------
  Compositing		WebRender
  ------------------------------------------------------------------------------
  WebGL 2 Driver Renderer	Intel Open Source Technology Center -- Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
  ------------------------------------------------------------------------------
  WebGL 2 Driver Version	4.5 (Core Profile) Mesa 18.3.0
  ------------------------------------------------------------------------------
  [...]
  Decision Log
  ------------------------------------------------------------------------------
  HW_COMPOSITING	blocked by default: Acceleration blocked by platform
  			available by user: Enabled by envvar
  ------------------------------------------------------------------------------
  WEBRENDER		opt-in by default: WebRender is an opt-in feature
  			available by user: Force enabled by envvar
  ------------------------------------------------------------------------------
  WEBRENDER_QUALIFIED	blocked by env: No qualified hardware
  ------------------------------------------------------------------------------

If you're curious how fast WebRender is try toggling gfx.webrender.debug.profiler
which would enable profiling overlay that shows FPS, CPU/GPU usage, etc.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?va43-r972-wny>