[wpe-webkit] Showing GPU feature states
Adrian Perez de Castro
aperez at igalia.com
Tue Nov 5 05:16:34 PST 2019
Hi,
On Tue, 05 Nov 2019 12:24:05 +0000, "Andy Pont" <andy.pont at sdcsystems.com> wrote:
> Adrian wrote...
>
> >> >We have recently added support in WebKit [1] to produce a similar report
> >> >when loading “about:gpu”. Note that currently you will need to build WPE
> >> >WebKit from the repository; the upcoming 2.27.2 development release (which
> >> >I expect to release this week) will have the feature as well.
> >>
> >> I have looked at the changeset in the SVN repository and it makes mention of
> >> MiniBrowser which I can find in the source tree. Do I need to include that
> >> in my Yocto build or will Cog equally well cope with the about:gpu URL?
> >
> >The WebKit MiniBrowser redirects “about:gpu” to “webkit://gpu”—which is the
> >actual URI for the page.
> >
> >The “webkit://gpu“ URI will work fine in Cog without needing any changes; as
> >long as you have a recent build of WPE WebKit which includes the needed patch
> >(for example the 2.27.2 development release [1], or a build from “trunk”).
>
> So I have my build now running with Cog 0.4.0 and WPE WebKit 2.27.2 and
> the webkit://gpu URL is working. Despite having a 1920x1080 resolution
> screen and setting the default font size very small I’m still not
> convinced I am seeing all of the output and I don’t have a mechanism to
> be able to scroll the screen.
If you have the possibility of plugging some USB mouse with wheel to your
device, that would let you scroll; it should be automatically detected. To
make fonts bigger, you could pass “--scale=2.0” to make rendered content
twice as big (or “1.5” for 150% scale, and so on).
> In the hardware acceleration information it says:
>
> Policy - always
> WebGL - Yes
> API - OpenGL ES 2 (libepoxy)
> Native interface - EGL
> GL_RENDERER - Vivante GC880
> GL_VERSION - OpenGL ES 3.0 v6.2.4.p4.190076
> EGL_VERSION - 1.5
>
> Does that make sense for a platform using the wpebackend-rdk for the
> i.MX6?
Yes, this looks correct
From the GL_* strings I guess that this is using the proprietary Vivante GPU
driver; the GL_VENDOR string would confirm that (if I recall correctly, if
the Etnaviv Mesa driver would be used, the GL_RENDERER string would contain
“Mesa”).
Cheers,
—Adrián
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.webkit.org/pipermail/webkit-wpe/attachments/20191105/eed85b4a/attachment-0001.bin>
More information about the webkit-wpe
mailing list