From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>,
"Burton, Ross" <ross.burton@intel.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3
Date: Tue, 09 Dec 2014 12:14:01 -0600 [thread overview]
Message-ID: <54873BE9.9030905@linux.intel.com> (raw)
In-Reply-To: <ADD6A3980E8C39419A432FF422031B4C7CF45250@ORSMSX103.amr.corp.intel.com>
On 09/12/14 11:20, Kamble, Nitin A wrote:
>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
>> Of Aníbal Limón
>> Sent: Thursday, December 04, 2014 3:18 PM
>> To: openembedded-core@lists.openembedded.org
>> Subject: [OE-core] [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack
>> Release 2014Q3
>>
>> Testing was made building and running core-image-sato in qemux86,
>> qemumips, and qemuarm also core-image-sato/core-image-weston in Intel
>> NUC.
>>
>> Tests freedesktop piglit was run in Intel NUC with 95% of tests passes
>> (9251/9694), you can found full results at [1].
> Is there a previous data point to compare, which can indicate weather the recipe updates are causing any regression or not?
>
> Nitin
>
I don't know, maybe Ross knows?.
>> [YOCTO #6805]
>>
>> [1] https://bugzilla.yoctoproject.org/attachment.cgi?id=2267
>>
>> The following changes since commit
>> a862bf045109d213c301121961bd8d389e48b13d:
>>
>> upstream_tracking.inc: update entries for dbus (2014-12-03 12:24:01 +0000)
>>
>> are available in the git repository at:
>>
>> git://git.yoctoproject.org/poky-contrib
>> alimon/linux_intel_graphics_2014q3_v2
>> http://git.yoctoproject.org/cgit.cgi/poky-
>> contrib/log/?h=alimon/linux_intel_graphics_2014q3_v2
>>
>> Aníbal Limón (3):
>> libdrm: Upgrade to 2.4.58.
>> mesa: Upgrade to 10.3.4.
>> xorg-xserver: Upgrade to 1.16.2.
>>
>> meta/recipes-graphics/drm/libdrm.inc | 1 +
>> .../drm/libdrm/GNU_SOURCE_definition.patch | 30 --
>> meta/recipes-graphics/drm/libdrm_2.4.54.bb | 8 -
>> meta/recipes-graphics/drm/libdrm_2.4.58.bb | 7 +
>> .../mesa/{mesa-gl_10.1.3.bb => mesa-gl_10.3.4.bb} | 0
>> ..._sw-include-xlib_sw_winsys.h-only-when-HA.patch | 52 --- ...ate-
>> NativeDisplayType-depending-on-config.patch | 362 ---------------------
>> .../mesa/mesa/0006-fix-out-of-tree-egl.patch | 48 ---
>> .../mesa/{mesa_10.1.3.bb => mesa_10.3.4.bb} | 9 +-
>> meta/recipes-graphics/mesa/mesa_git.bb | 9 +-
>> .../recipes-graphics/xorg-xserver/xserver-xorg.inc | 5 +-
>> .../xorg-xserver/xserver-xorg/crosscompile.patch | 22 --
>> .../xserver-xorg/mips64-compiler.patch | 29 --
>> .../xorg-xserver/xserver-xorg/present-module.patch | 66 ----
>> ...erver-xorg_1.15.1.bb => xserver-xorg_1.16.2.bb} | 9 +-
>> 15 files changed, 21 insertions(+), 636 deletions(-) delete mode 100644
>> meta/recipes-graphics/drm/libdrm/GNU_SOURCE_definition.patch
>> delete mode 100644 meta/recipes-graphics/drm/libdrm_2.4.54.bb
>> create mode 100644 meta/recipes-graphics/drm/libdrm_2.4.58.bb
>> rename meta/recipes-graphics/mesa/{mesa-gl_10.1.3.bb => mesa-
>> gl_10.3.4.bb} (100%) delete mode 100644 meta/recipes-
>> graphics/mesa/mesa/0002-pipe_loader_sw-include-xlib_sw_winsys.h-only-
>> when-HA.patch
>> delete mode 100644 meta/recipes-graphics/mesa/mesa/0003-EGL-Mutate-
>> NativeDisplayType-depending-on-config.patch
>> delete mode 100644 meta/recipes-graphics/mesa/mesa/0006-fix-out-of-
>> tree-egl.patch
>> rename meta/recipes-graphics/mesa/{mesa_10.1.3.bb => mesa_10.3.4.bb}
>> (62%) delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-
>> xorg/crosscompile.patch
>> delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-
>> xorg/mips64-compiler.patch
>> delete mode 100644 meta/recipes-graphics/xorg-xserver/xserver-
>> xorg/present-module.patch
>> rename meta/recipes-graphics/xorg-xserver/{xserver-xorg_1.15.1.bb =>
>> xserver-xorg_1.16.2.bb} (75%)
>>
>> --
>> 1.9.1
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2014-12-09 18:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 23:18 [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3 Aníbal Limón
2014-12-04 23:18 ` [PATCHv2 1/3] libdrm: Upgrade to 2.4.58 Aníbal Limón
2014-12-04 23:18 ` [PATCHv2 2/3] mesa: Upgrade to 10.3.4 Aníbal Limón
2014-12-04 23:18 ` [PATCHv3 3/3] xorg-xserver: Upgrade to 1.16.2 Aníbal Limón
2014-12-08 9:29 ` [PATCHv2 0/3] Upgrades for comply Intel Graphics Stack Release 2014Q3 Nicolas Dechesne
2014-12-09 17:20 ` Kamble, Nitin A
2014-12-09 18:14 ` Aníbal Limón [this message]
2014-12-09 20:06 ` Burton, Ross
2014-12-09 20:19 ` Otavio Salvador
2014-12-10 11:43 ` Burton, Ross
2014-12-10 16:15 ` Richard Purdie
2014-12-10 16:17 ` Otavio Salvador
2014-12-10 16:21 ` Richard Purdie
2014-12-10 8:08 ` Nicolas Dechesne
2014-12-10 11:33 ` Burton, Ross
2014-12-10 15:46 ` Aníbal Limón
2014-12-10 23:43 ` Kamble, Nitin A
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=54873BE9.9030905@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=nitin.a.kamble@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox