From: Chris Billington Subject: Re: webkit2gtk and DRM To: Antoine Jacoutot Cc: ports@openbsd.org Date: Thu, 19 Mar 2026 16:42:00 +0800 Antoine Jacoutot wrote: > On Wed, Mar 18, 2026 at 12:40:56PM +0800, Chris Billington wrote: >> On OpenBSD 7.8-stable and 7.9-beta amd64, I notice that video hardware >> acceleration is not working in webkit2gtk-based browsers such as luakit, >> badwolf and epiphany. >> >> Specifically, the DRM Primary Node /dev/dri/card0 and DRM render Device >> /dev/dri/renderD128 do not appear in the webkit://gpu info page like they do >> on a Linux machine I tested. >> >> The HW Acceleration policy is listed on the info page as 'never' but >> overriding it to 'always' in Luakit settings, for example, does not change >> the result. >> >> Sites with video content therefore fall back to software rendering. >> >> Is this a known limitation of our DRM implementation, or is there a possible >> configuration issue in webkit2gtk on our platform? >> >> EGL and VAAPI seem to be present and functional (vainfo, and a query of the >> available EGL extensions). >> >> Are others seeing the same on other amd64 platforms? > > It's probably due to our lack of dma-buf support. > Thanks. I guess the demand to add dma-buf support is not strong either, for such a niche requirement. So from webkitgtk 2.44 onwards it seems that dma-buf is the only option, when X11 backend was finally removed, and is still used to render to screen even if the Gstreamer VAAPI decoders are in the chain. Kind of Linux-centric and limits the usefulness of Webkit-based browsers for us, unless an alternative path is added in the future. Oh well. Chris