Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3 00/11] Mesa upgrade/improvements
Date: Fri, 3 Aug 2012 14:19:45 +0100	[thread overview]
Message-ID: <EC2F754A1E854583B06C4E1BF18AB5F9@intel.com> (raw)
In-Reply-To: <C94E9933-5642-406C-ACBC-2F0A13E6AB41@dominion.thruhere.net>

On Friday, 3 August 2012 at 11:18, Koen Kooi wrote:
> libegl and libgles aren't built nowadays, so the problem is avoided. Noone has dared to touch this subject the past 2.5 years: http://cgit.openembedded.org/openembedded/commit/recipes/mesa?id=3d96f8cb61225d515b5cb4fe863f0d50c3ced436
> 
> The best solution[1] is to disable egl/gles in the mesa-recipes and add a seperate recipe for them. That way you still get glu and other useful mesa bits needed for gnome/efl/xfce/etc, but you can skip the sysroot/shlib poisoning if needed.
After much digging I see that the Beagle PVR drivers only provide gles and egl, which is why you say that the problem was avoided.  Of course that's just one specific driver, for example the Cedar Trail EMGD driver does build libgl, libgles and libegl.

If the solution is "put the egl/gles bits in another package" then I'm totally confused as to what the actual problem is.  Considering there's numerous libegl libraries for the many variants of PVR on ARM, I'm struggling to understand exactly what is new here.

Can you explain clearly what the problem is, I'm obviously missing something.  Once I understand the problem I can help with a solution.
> [1] The best solution if of course getting sgx support into mesa, but nothing is happening on that front apart from some posturing on the fsf side, no actual code.

HahahHAHAHAHahha.  (wipes tears from eyes)  The FSF can posture all they want (wasn't aware they'd done that as the code is clearly closed source), but I can't see Imagination opening all their code any day soon.

Cheers,
Ross 




  reply	other threads:[~2012-08-03 13:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02 16:48 [PATCH V3 00/11] Mesa upgrade/improvements Ross Burton
2012-08-02 16:48 ` [PATCH V3 01/11] mesa: no need to depend on python-native, the class does that Ross Burton
2012-08-02 16:48 ` [PATCH V3 02/11] mesa: format the packages list nicely Ross Burton
2012-08-02 16:48 ` [PATCH V3 03/11] mesa: move glu.pc to libglu-dev Ross Burton
2012-08-02 16:48 ` [PATCH V3 04/11] mesa: add --enable-shared-glapi, and package it in libglapi Ross Burton
2012-08-02 16:48 ` [PATCH V3 05/11] mesa: enable the Graphic Buffer Manager library Ross Burton
2012-08-02 16:49 ` [PATCH V3 06/11] mesa: Update to 8.0.4 (latest stable version) Ross Burton
2012-08-02 16:49 ` [PATCH V3 07/11] mesa: Use 'require' instead of 'include' Ross Burton
2012-08-02 16:49 ` [PATCH V3 08/11] mesa: enable GLES v1 and v2 Ross Burton
2012-08-02 16:49 ` [PATCH V3 09/11] mesa-demos: fix GLES2 build Ross Burton
2012-08-02 16:49 ` [PATCH V3 10/11] mesa: respect x11 DISTRO_FEATURE Ross Burton
2012-08-02 16:49 ` [PATCH V3 11/11] mesa: enable EGL, with DRM and X11 platforms Ross Burton
2012-08-02 17:04 ` [PATCH V3 00/11] Mesa upgrade/improvements Martin Jansa
2012-08-02 17:13   ` Burton, Ross
2012-08-02 18:38 ` Koen Kooi
2012-08-02 19:03   ` Ross Burton
2012-08-03 10:18     ` Koen Kooi
2012-08-03 13:19       ` Ross Burton [this message]
2012-08-03 15:46         ` Koen Kooi
2012-08-06 12:43           ` Richard Purdie
2012-08-06 13:24             ` Koen Kooi
2012-08-06 14:04               ` Richard Purdie
2012-08-06 14:24                 ` Koen Kooi
2012-08-06 19:47                 ` Phil Blundell
2012-08-06 14:19 ` Richard Purdie

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=EC2F754A1E854583B06C4E1BF18AB5F9@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox