[meta-browser] calling all chromium recipe users

[meta-browser] calling all chromium recipe users

[Trevor Woerner]

When testing changes to the chromium[-wayland] recipes, it would be
great to know the layers, configurations, and MACHINEs with which
people are building.

For example I care about chromium running on X11 for minnow
(meta-intel) and raspberry pi (meta-raspberrypi). How are other people
running chromium?

Also, are you able to run with accelerated graphics? If so, what
configuration are you using?

Specifically, I assume the trick is the correct configuration of various

    PREFERRED_PROVIDER_virtual/X = Y

where X is one of {mesa|gl|egl|gles1|gles2} and Y is probably
something BSP-specific. Is anything else needed to get accelerated
graphics working with chromium?

Re: [meta-browser] calling all chromium recipe users

[Denys Dmytriyenko]

On Wed, Mar 29, 2017 at 03:35:22PM -0400, Trevor Woerner wrote:
> When testing changes to the chromium[-wayland] recipes, it would be
> great to know the layers, configurations, and MACHINEs with which
> people are building.
> 
> For example I care about chromium running on X11 for minnow
> (meta-intel) and raspberry pi (meta-raspberrypi). How are other people
> running chromium?

chromium-wayland on TI platforms from meta-ti.


> Also, are you able to run with accelerated graphics? If so, what
> configuration are you using?

Full acceleration is still in the works for our platforms.
Very basic "hacky" way was to patch wayland.gyp to bypass the configure check 
for Mesa version:
http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta-arago-distro/recipes-browser/chromium/chromium-wayland/0001-wayland.gyp-adjust-Mesa-version-to-work-with-TI-SGX-.patch;hb=HEAD

-- 
Denys


> Specifically, I assume the trick is the correct configuration of various
> 
>     PREFERRED_PROVIDER_virtual/X = Y
> 
> where X is one of {mesa|gl|egl|gles1|gles2} and Y is probably
> something BSP-specific. Is anything else needed to get accelerated
> graphics working with chromium?
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Re: [meta-browser] calling all chromium recipe users

[Ian Coolidge]

Chromium and Chromium-Wayland on IMX platform

Chromium is working great, although chromium-imx hasn't been updated yet
for the later 53.x versions as the patches for graphics need to be updated.

Chromium-Wayland hasn't worked in any of it's versions, or on wayland on
IMX in general for some time. Unless i'm doing something wrong... I've been
trying to get this working on the 48x version for a while now, I just get a
segfault on startup that looks like this

root@nitrogen6x-lite:~# google-chrome www.google.com
>
> [1:1:0327/214358:ERROR:image_metadata_extractor.cc(112)] Couldn't load
>> libexif. libexif.so.12: cannot open shared object file: No such file or
>> directory
>
> error: XDG_RUNTIME_DIR not set in the environment.
>
> error: XDG_RUNTIME_DIR not set in the environment.
>
> [512:512:0327/214400:ERROR:display.cc(148)] WaylandDisplay failed to
>> initialize hardware
>
> [512:512:0327/214400:FATAL:ozone_platform_wayland.cc(115)] failed to
>> initialize display hardware
>
> #0 0x00005524860a <unknown>
>
> #1 0x000055257dd0 <unknown>
>
> #2 0x0000558a506e <unknown>
>
> #3 0x000055989104 <unknown>
>
> #4 0x000055989a54 <unknown>
>
> #5 0x000055989b26 <unknown>
>
> #6 0x0000578ca552 <unknown>
>
> #7 0x00005521a1d4 <unknown>
>
> #8 0x00005521900a <unknown>
>
> #9 0x000054f3e4f8 ChromeMain
>
> #10 0x0000766e246a __libc_start_main
>
>
>> Received signal 6
>
> #0 0x00005524860a <unknown>
>
> #1 0x0000552488cc <unknown>
>
> #2 0x0000766f1020 <unknown>
>
> #3 0x0000766e26b6 <unknown>
>
> #4 0x0000766f040c gsignal
>
> #5 0x0000766f10fa abort
>
> #6 0x00005524842a <unknown>
>
> #7 0x000055257e98 <unknown>
>
> #8 0x0000558a506e <unknown>
>
> #9 0x000055989104 <unknown>
>
> #10 0x000055989a54 <unknown>
>
> #11 0x000055989b26 <unknown>
>
> #12 0x0000578ca552 <unknown>
>
> #13 0x00005521a1d4 <unknown>
>
> #14 0x00005521900a <unknown>
>
> #15 0x000054f3e4f8 ChromeMain
>
> #16 0x0000766e246a __libc_start_main
>
> [end of stack trace]
>
> Segmentation fault
>
>
>
On Wed, Mar 29, 2017 at 3:04 PM, Denys Dmytriyenko <denis@denix.org> wrote:

> On Wed, Mar 29, 2017 at 03:35:22PM -0400, Trevor Woerner wrote:
> > When testing changes to the chromium[-wayland] recipes, it would be
> > great to know the layers, configurations, and MACHINEs with which
> > people are building.
> >
> > For example I care about chromium running on X11 for minnow
> > (meta-intel) and raspberry pi (meta-raspberrypi). How are other people
> > running chromium?
>
> chromium-wayland on TI platforms from meta-ti.
>
>
> > Also, are you able to run with accelerated graphics? If so, what
> > configuration are you using?
>
> Full acceleration is still in the works for our platforms.
> Very basic "hacky" way was to patch wayland.gyp to bypass the configure
> check
> for Mesa version:
> http://arago-project.org/git/?p=meta-arago.git;a=blob;f=
> meta-arago-distro/recipes-browser/chromium/chromium-
> wayland/0001-wayland.gyp-adjust-Mesa-version-to-work-
> with-TI-SGX-.patch;hb=HEAD
>
> --
> Denys
>
>
> > Specifically, I assume the trick is the correct configuration of various
> >
> >     PREFERRED_PROVIDER_virtual/X = Y
> >
> > where X is one of {mesa|gl|egl|gles1|gles2} and Y is probably
> > something BSP-specific. Is anything else needed to get accelerated
> > graphics working with chromium?
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>