Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Valentin Popa <valentin.popa@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] [V3]mesa: upgrade to 10.1.3
Date: Thu, 22 May 2014 19:28:25 +0300	[thread overview]
Message-ID: <537E25A9.9080106@intel.com> (raw)
In-Reply-To: <cover.1400690725.git.valentin.popa@intel.com>

New from V2:

(*) removed the old patch for eglinfo and updated the recipe to a newer 
version.
(*) renamed libmesa-megadriver to mesa-megadriver

The changes are available at :

  git://git.yoctoproject.org/poky-contrib vpopa/mesa
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=vpopa/mesa



On 05/21/2014 07:49 PM, Valentin Popa wrote:
> New in V2:
> (*) eglinfo: patched to compile with mesa10+
> (*) mesa: upgrade to 10.1.3 - multilib rootfs issue fixed
>
> The following changes since commit 122079e9b0b513c46ca76993403db4cfa51e858f:
>
>    bitbake: data_smart: Fix an unusual variable reference bug (2014-05-21 16:47:01 +0100)
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib vpopa/mesa
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=vpopa/mesa
>
> Valentin Popa (4):
>    dri3proto: add it to oe-core
>    libxshmfence: add it to oe-core
>    mesa: upgrade to 10.1.3
>    eglinfo: patched to compile with mesa10+
>
>   meta/recipes-graphics/eglinfo/eglinfo-fb_1.0.bb    |  2 ++
>   meta/recipes-graphics/eglinfo/eglinfo-x11_1.0.bb   |  2 ++
>   meta/recipes-graphics/eglinfo/eglinfo.inc          |  4 ++-
>   .../0001-eglinfo-x11-change-constant-name.patch    | 33 ++++++++++++++++++++
>   .../mesa/{mesa-gl_9.2.5.bb => mesa-gl_10.1.3.bb}   |  0
>   meta/recipes-graphics/mesa/mesa.inc                | 36 ++++++++++++++--------
>   .../mesa/{mesa_9.2.5.bb => mesa_10.1.3.bb}         |  4 +--
>   meta/recipes-graphics/mesa/mesa_git.bb             |  4 +--
>   meta/recipes-graphics/xorg-lib/libxshmfence_1.1.bb | 17 ++++++++++
>   meta/recipes-graphics/xorg-proto/dri3proto_1.0.bb  | 14 +++++++++
>   10 files changed, 99 insertions(+), 17 deletions(-)
>   create mode 100644 meta/recipes-graphics/eglinfo/eglinfo/0001-eglinfo-x11-change-constant-name.patch
>   rename meta/recipes-graphics/mesa/{mesa-gl_9.2.5.bb => mesa-gl_10.1.3.bb} (100%)
>   rename meta/recipes-graphics/mesa/{mesa_9.2.5.bb => mesa_10.1.3.bb} (82%)
>   create mode 100644 meta/recipes-graphics/xorg-lib/libxshmfence_1.1.bb
>   create mode 100644 meta/recipes-graphics/xorg-proto/dri3proto_1.0.bb
>



  parent reply	other threads:[~2014-05-22 16:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-21 16:49 [PATCH 0/4] [PATCH_V2]mesa: upgrade to 10.1.3 Valentin Popa
2014-05-21 16:49 ` [PATCH 1/4] dri3proto: add it to oe-core Valentin Popa
2014-05-21 16:50 ` [PATCH 2/4] libxshmfence: " Valentin Popa
2014-05-21 16:50 ` [PATCH 3/4] mesa: upgrade to 10.1.3 Valentin Popa
2014-05-21 18:33   ` Martin Jansa
2014-05-22 12:26     ` Valentin Popa
2014-05-22 13:23       ` Martin Jansa
2014-05-22 13:29         ` Valentin Popa
2014-05-21 16:50 ` [PATCH 4/4] eglinfo: patched to compile with mesa10+ Valentin Popa
2014-05-21 20:22   ` Burton, Ross
2014-05-22 12:28     ` Valentin Popa
2014-05-22 16:28 ` Valentin Popa [this message]
2014-05-22 16:58   ` [PATCH 0/4] [V3]mesa: upgrade to 10.1.3 Burton, Ross
2014-05-27 16:16     ` Sean Hudson

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=537E25A9.9080106@intel.com \
    --to=valentin.popa@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