All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Tomas Frydrych <tf+lists.yocto@r-finger.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] OpenGL packaging/staging policy
Date: Tue, 23 Oct 2012 13:06:00 +1100	[thread overview]
Message-ID: <CAPj87rOXzZ5EwKYCrBnYtYAQo3cUyXtXyyDSh2nKh05Gy=uY9A@mail.gmail.com> (raw)
In-Reply-To: <5085800A.4060600@r-finger.com>

Hi,

On 23 October 2012 04:19, Tomas Frydrych <tf+lists.yocto@r-finger.com> wrote:
> b) Split the ginormous mesa recipe, so that it is, for example, possible
> to stage mesa gl without mesa egl, so that we can accommodate HW that
> wants to use bits of mesa.

What? You can't do that.  Well, you kinda can if you're using GLX and
nothing else, maybe, sorta.  But the EGL and GL (ES) implementations
are very heavily tied together and can't be used as independent works.
 You can separate GLU, which we've already done.  I think you can
split out the core of libgbm, but not the DRI plugin.  And that's
about it.

I've got gles2/opengl/egl MACHINE_FEATURES in my tree at
git://git.collabora.com/~daniels/poky, which goes some way towards
improving the current GL (ES) situation.  But trying to split the
actual stacks into multiple parts helps no-one.

Cheers,
Daniel



  parent reply	other threads:[~2012-10-23  2:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 16:35 [RFC] OpenGL packaging/staging policy Burton, Ross
2012-10-22 17:19 ` Tomas Frydrych
2012-10-22 19:27   ` Burton, Ross
2012-10-22 20:25     ` Tomas Frydrych
2012-10-23  2:06   ` Daniel Stone [this message]
2012-10-23  8:37     ` Tomas Frydrych
2012-10-23  9:18       ` Daniel Stone
2012-10-23  9:49         ` Tomas Frydrych
2012-10-29 17:26           ` Burton, Ross
2012-10-29 17:26             ` [OE-core] " Burton, Ross
2012-10-29 18:27             ` Tomas Frydrych
2012-11-20 16:52             ` Burton, Ross
2012-11-20 16:52               ` [OE-core] " Burton, Ross
2012-10-22 17:32 ` [oe] " Phil Blundell
2012-10-22 17:38   ` Otavio Salvador
2012-10-22 19:26   ` Burton, Ross
2012-10-22 17:33 ` Otavio Salvador
2012-10-22 17:33   ` [OE-core] " Otavio Salvador
2012-10-22 19:25   ` Phil Blundell
2012-10-22 19:25     ` [OE-core] " Phil Blundell
2012-10-22 17:37 ` Mark Hatle
2012-10-22 19:29   ` Burton, Ross

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='CAPj87rOXzZ5EwKYCrBnYtYAQo3cUyXtXyyDSh2nKh05Gy=uY9A@mail.gmail.com' \
    --to=daniel@fooishbar.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=tf+lists.yocto@r-finger.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.