Re: [CFT] Mesa 18.3.0 update (mesa-libs, mesa-dri, libosmesa, clover)

Jan Beich <[email protected]>
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]>
Kevin Oberman <[email protected]> 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.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.