From: Pengyu Ma <pengyu.ma@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [V2][PATCH] mesa: Upgrade to 10.4.0
Date: Fri, 30 Jan 2015 09:51:15 +0800 [thread overview]
Message-ID: <54CAE393.2020605@windriver.com> (raw)
In-Reply-To: <CAJTo0LaxjO4nX9fWWQN-e0EgTSt6RRc9U-DovdQFY5+z7tMLmw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On 01/29/2015 06:35 PM, Burton, Ross wrote:
>
> On 29 January 2015 at 10:10, Nicolas Dechesne
> <nicolas.dechesne@linaro.org <mailto:nicolas.dechesne@linaro.org>> wrote:
>
> well, i am not sure this is right... at least probably not the right
> argument. oe-core is not meant to be tied to specific intel stable
> releases, whether it is about content or schedule..
>
> i would believe our goal is to provide the most recent stable release
> instead. so that each OE (well, Yocto) release ends up with the most
> recent versions.
>
> fwiw, for the boards/platforms i care about, 10.4.3 would be fine.
>
>
> Agreed. The Intel driver release is tested with 10.4.0 but 10.4.3 is
> a newer point release so should work, and Intel's aim of ensuring that
> the latest driver stack is supported doesn't trump having the latest
> upstream releases in oe-core.
>
> If it turns out that 10.4.3 is critically broken with the Intel driver
> then *meta-intel* can ship 10.4.0.
>
> Please re-submit this with 10.4.3 instead of 10.4.0.
>
mesa_git bb will keep sync the latest version 10.4.3, that's why we keep
both _git and 10.4.0.
Now all all the version of xorg-video-intel, libdrm, and xserver-xorg
are the same with Intel Graphic stack 2014 Q4.
So mesa_10.4.0 will make a stable and verified solution here,
and _git version will make the latest version here.
Pengyu
> Ross
[-- Attachment #2: Type: text/html, Size: 3255 bytes --]
next prev parent reply other threads:[~2015-01-30 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 8:57 [V2][PATCH] mesa: Upgrade to 10.4.0 Pengyu Ma
2015-01-29 9:53 ` Nicolas Dechesne
2015-01-29 10:05 ` Pengyu Ma
2015-01-29 10:10 ` Nicolas Dechesne
2015-01-29 10:35 ` Burton, Ross
2015-01-30 1:51 ` Pengyu Ma [this message]
2015-01-30 7:51 ` Nicolas Dechesne
2015-01-30 7:56 ` Pengyu Ma
2015-01-30 8:02 ` Nicolas Dechesne
2015-01-30 9:05 ` Richard Purdie
2015-01-30 9:12 ` Pengyu Ma
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=54CAE393.2020605@windriver.com \
--to=pengyu.ma@windriver.com \
--cc=nicolas.dechesne@linaro.org \
--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