All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: Mark O'Donovan <shiftee@eircom.net>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Webkit2gtk opengl issue
Date: Fri, 25 Sep 2015 17:01:12 -0400	[thread overview]
Message-ID: <5605B618.7010700@gmail.com> (raw)
In-Reply-To: <CAJv4cO0rD_wNZDYAMxJdD2wJRUs6omi99j26FSj=+fzgJyWGbw@mail.gmail.com>

On 09/23/15 07:53, Mark O'Donovan wrote:
> I am working on an am335x based project, with a webkitgtk
> program on the screen, displaying a simple webpage.
>
> I want to use a standard yocto kernel, which I believe
> means I must do without the SGX hardware acceleration
> until an open-source driver is available.

You need to use whatever kernel the accelerated drivers were written
against. Sometimes that can be fairly recent, other times: not so much.

> Thus in fido I had added opengl to DISTRO_FEATURES_remove
> This worked with webkitgtk 1.x
>
> The webkitgtk 2.x recipe  also specifies opengl as optional.
> However it depends on gtk+3 which depends on libepoxy
> which requires virtual/egl.

For ARM SoCs/boards that have mali (which isn't your case, but is mine),
the user-space binary-only mali drivers PROVIDE egl, so it is possible
for me to build libepoxy with DISTRO_FEATURES_remove = "opengl" and the
mali test app and x11 server both build and run correctly.

> Is this an oversight??
>
> Is it possible to build webkit 2.x without opengl??

I don't know. But in the mali case it is possible to have mali provide
egl/gles1/gles2 and have mesa-gl provide an opengl-only solution as a
fall-back for any non-egl/gles1/2 apps (or at least theoretically it is).

Hope this helps.


  parent reply	other threads:[~2015-09-25 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-23 11:53 Webkit2gtk opengl issue Mark O'Donovan
2015-09-23 12:05 ` Burton, Ross
2015-09-25 21:01 ` Trevor Woerner [this message]
2015-09-28 10:51   ` Mark O'Donovan
2015-10-12 16:03     ` Mark O'Donovan

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=5605B618.7010700@gmail.com \
    --to=twoerner@gmail.com \
    --cc=shiftee@eircom.net \
    --cc=yocto@yoctoproject.org \
    /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.