[ozone-dev] Running content_shell with ozone-gbm on Yocto Linux

[Joone Hur]

Hi,

There have been some updates on ozone-gbm for a Linux system since I
announced the project in the last year:

https://groups.google.com/a/chromium.org/d/msg/ozone-dev/Cu1rOusi4BU/m98xPMxVBgAJ

1. Some of the patches are merged upstream:

* https://chromium-review.googlesource.com/c/chromium/src/+/886836: it
enables the Intel i965 driver for mini-gbm, which allocates a buffer
directly to GPU memory. The use_intel_minigbm build flag is added for this
purpose.

* https://chromium-review.googlesource.com/c/chromium/src/+/969416: it
moves all files in ui/display/manager/chromeos to ui/display/manager. This
is necessary because non-Chrome OS Linux also requires a display
configurator, but it was only used for CrOS. You can add the display
configurator to your build by adding the build_display_configuration build
flag to your project.

2. content_shell runs with ozone-gbm without Mus.

* Chromium for desktop was able to run using Mus(Mojo UI service) with
ozone-gbm, but Mus will be only used for ChromeOS.

3. content_shell works with mouse and keyboard input: it runs in fullscreen
without any view UI with all the hardware accelerations: zero-copy texture
upload, video accelerations and hardware overlay on Intel GPU.

Note: For test purpose, you can build your own image with the Yocto recipe:
https://github.com/joone/meta-browser/tree/ozone-gbm-67. Here is a demo
video at

If you have any questions, please reply to this mailing list or send me an
email at ***@intel.com.

Thanks,

Joone