All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ayoub Zaki <ayoub.zaki@googlemail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-browser] CFT: Chromium 62 in meta-browser
Date: Tue, 28 Nov 2017 13:47:21 +0100	[thread overview]
Message-ID: <CA+-BmJbzMoPd2bEyzJkrHN=+RvUmJu0F0XVFmPSSCJcKcUPe7A@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKqei-6juaQQOZ04mpF5Er8n1Op8s_Q6NfR9J2STY8fqsg@mail.gmail.com>

Hi Otavio,

that's a shame :-( thanks for the information.
are they other browsers that are well supported with GPU acceleration on
iMX6 ?
what about Firefox ?
Thank you!

On Tue, Nov 28, 2017 at 12:58 PM, Otavio Salvador <
otavio.salvador@ossystems.com.br> wrote:

> On Tue, Nov 28, 2017 at 6:13 AM, Ayoub Zaki <ayoub.zaki@googlemail.com>
> wrote:
> > Thank you, indeed I used rocko branches and it seems to build and also
> run
> > on an iMX6!
> > I use a mainline kernel 4.14  and with iMX6 Etnaviv GPU acceleration
> > support.
> > It's not clear for me how to enable GPU acceleration with chromium +
> > Etnaviv :
> > I tried the switch --use-gl=any,  it starts up but when running WebGL
> demo
> > Chromium/Etnaviv is crashing...
> > For normal browsing it works just fine however I noticed that CPU
> > consumption is very high > 50%
> > Anyone having better experience with Chromium + HW accleration support on
> > iMX6 ?
>
> The i.MX6 support requires a number of patches to properly support its
> hardware. Currently not well supported ...
>
> --
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
>


  reply	other threads:[~2017-11-28 12:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 16:28 [meta-browser] CFT: Chromium 62 in meta-browser Raphael Kubo da Costa
2017-11-09 16:54 ` Otavio Salvador
2017-11-09 17:08   ` Raphael Kubo da Costa
2017-11-10 19:49 ` Trevor Woerner
2017-11-11  0:10   ` Ian Coolidge
2017-11-11 17:25     ` Otavio Salvador
2017-11-13 21:51       ` Ian Coolidge
2017-11-13 21:56         ` Ian Coolidge
2017-11-15 12:04 ` Raphael Kubo da Costa
2017-11-15 12:38   ` Martin Jansa
2017-11-15 14:20     ` Martin Jansa
2017-11-15 17:08     ` Raphael Kubo da Costa
2017-11-15 17:41       ` Martin Jansa
2017-11-15 17:49         ` Kubo Da Costa, Raphael
2017-11-15 19:34         ` Khem Raj
2017-11-23 10:22           ` Ayoub Zaki
2017-11-28  0:52             ` Ian Coolidge
2017-11-28  8:13               ` Ayoub Zaki
2017-11-28 11:58                 ` Otavio Salvador
2017-11-28 12:47                   ` Ayoub Zaki [this message]
2017-11-28 13:05                     ` Otavio Salvador
2017-11-28 21:44                       ` Ian Coolidge
2017-12-11 11:30             ` Raphael Kubo da Costa
2017-12-11 11:35               ` Ayoub Zaki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+-BmJbzMoPd2bEyzJkrHN=+RvUmJu0F0XVFmPSSCJcKcUPe7A@mail.gmail.com' \
    --to=ayoub.zaki@googlemail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.