From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>,
openembeded-devel <openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] [meta-oe][PATCH] libva: Import from meta-intel and update to 1.7.3
Date: Fri, 02 Dec 2016 07:54:21 -0800 [thread overview]
Message-ID: <1480694061.30023.78.camel@linux.intel.com> (raw)
In-Reply-To: <CAMKF1spw8bvo8guTWkhYeQcn+Vs0kU-2X5D-03etwOj3dGroaw@mail.gmail.com>
On Thu, 2016-12-01 at 11:58 -0800, Khem Raj wrote:
> On Thu, Dec 1, 2016 at 9:19 AM, Burton, Ross <ross.burton@intel.com>
> wrote:
> >
> > On 1 December 2016 at 03:42, Khem Raj <raj.khem@gmail.com> wrote:
> >
> > >
> > > >
> > > > >
> > > > > If libva goes in, can we get libva-intel-driver in as well?
> > > > > Those go
> > > > > hand-in-glove currently.
> > > > >
> > > >
> > > > Khem, does the AMD BSP use that? I'd have thought that bit was
> > > > actually
> > > > meta-intel specific.
> > >
> > > its intel BSPs specific
> >
> >
> > So I'd endorse libva for oe-core, and the intel-driver remains in
> > meta-intel.
>
> I am fine with proposal. This is time for someone to raise
> objections.
>
As meta-intel maintainer I am OK with this, makes more sense than going
into meta-oe. Please be sure to include meta-intel@yoctoproject.org for
this.
I'm wondering if we should also move the gstreamer-vaapi-1.0 recipe to
oe-core to be with it's brethren?
Sau!
> >
> >
> > Ross
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > Openembedded-devel@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2016-12-02 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161128225759.9756-1-raj.khem@gmail.com>
[not found] ` <CAJTo0LZ+2+MhZ4TepH1dDzC3LyG7gz70TNEzoDjXgaBTjvHOsg@mail.gmail.com>
[not found] ` <o1jct4$pvp$1@blaine.gmane.org>
[not found] ` <CAJTo0LYLgFFR+6d3SDkso6X28N00tVAnUGuJg4sPG-msMKWU6A@mail.gmail.com>
[not found] ` <8632C69E-1C6B-482D-AF15-965F55F0AF88@gmail.com>
[not found] ` <CAJTo0LYTYa4A42+FA9Ou=bVA6ddH8gzVBpJZJvNfa9Jyb9QQfA@mail.gmail.com>
2016-12-01 19:58 ` [oe] [meta-oe][PATCH] libva: Import from meta-intel and update to 1.7.3 Khem Raj
2016-12-02 15:54 ` Saul Wold [this message]
2016-12-02 16:13 ` 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=1480694061.30023.78.camel@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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