All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-browser] calling all chromium recipe users
Date: Wed, 29 Mar 2017 18:04:01 -0400	[thread overview]
Message-ID: <20170329220401.GQ15664@denix.org> (raw)
In-Reply-To: <CAHUNapSj77gK_kExofCWaeREZOqwQoHQei4YZbqE1F5Uh=2CFA@mail.gmail.com>

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


  reply	other threads:[~2017-03-29 22:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-29 19:35 [meta-browser] calling all chromium recipe users Trevor Woerner
2017-03-29 22:04 ` Denys Dmytriyenko [this message]
2017-03-31 18:27   ` Ian Coolidge

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=20170329220401.GQ15664@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /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.