{"id":709,"date":"2017-02-27T14:16:15","date_gmt":"2017-02-27T13:16:15","guid":{"rendered":"http:\/\/blogs.igalia.com\/jaragunde\/?p=709"},"modified":"2017-06-14T12:55:49","modified_gmt":"2017-06-14T10:55:49","slug":"genivi-fying-chromium-part-2","status":"publish","type":"post","link":"https:\/\/blogs.igalia.com\/jaragunde\/2017\/02\/genivi-fying-chromium-part-2\/","title":{"rendered":"GENIVI-fying Chromium, part 2"},"content":{"rendered":"

In the previous blog post<\/a>, we introduced the work to port Chromium to the GENIVI Development Platform<\/a> (GDP). We have continued working to improve the integration, and make everything easier to build.<\/p>\n

In first place, we are now using the latest code from the Ozone-Wayland<\/a> project that builds on top of Chromium 53 instead of Chromium 48. We have rebased the meta-browser<\/em> recipes for the newer version and contributed the patch<\/a> to the upstream project, together with other patches to clean the build process and to fix issues on certain platforms.<\/p>\n

Some issues detected in the earlier steps of the integration were addressed. The aspect ratio of the browser window has been modified to fit the GDP demonstration HMI. A performance degradation when playing video had also been detected, the problem was not actually in Chromium, Pulseaudio was taking all the CPU away from the browser processes when using the default null sink. We fixed it by setting Alsa as the default sink with the command pacmd \"set-default-sink AlsaPrimary\"<\/code> (do it in \/etc\/pulse\/default.pa<\/code> to make the change persistent). We are obviously bypassing the GENIVI Audio Manager here, it should be integrated at a later point.<\/p>\n

We are in the process to merge our patches<\/a> into the GENIVI platform, to make the Chromium browser part of the default build. You currently have to use our fork of meta-genivi-dev<\/em><\/a>, while the meta-browser<\/em> layer has already been added<\/a> as a submodule and it’s not necessary to explicitly add it.<\/p>\n

Finally, we have been testing how Chromium and Ozone-Wayland behave in multi-seat environments using the Wayland IVI Extension<\/a> and the IVI Layer Manager libraries to have full control of screens, layers, surfaces and focus. We have extracted some conclusions<\/a> that will allow us to make Chromium behave as expected in this scenario.<\/p>\n

\"\"<\/a>

Chromium on a multi-seat environment<\/p><\/div>\n

All the work we have done is publicly available already. You may try it by:<\/p>\n