Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Wed, 2013-02-27 at 12:35 +0200, Laurentiu Palcu wrote:
> Laurentiu Palcu (2):
> libva-intel-driver: upgrade to 1.0.19
> libva: upgrade to 1.1.0
>
> ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
> rename common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC1-and-H264-vid.patch
> (100%)
> rename common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> libva-intel-driver_1.0.19.bb} (64%)
> rename common/recipes-multimedia/libva/{libva_1.0.16.bb => libva_1.1.0.bb}
> (47%)
>
Pulled into meta-intel/master (along with some other patches that
enabled it all to finally work). See for details:
https://lists.yoctoproject.org/pipermail/meta-intel/2013-April/000636.html
Thanks,
Tom
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
> -Original Message- > From: Palcu, Laurentiu > Sent: Tuesday, March 12, 2013 9:25 AM > To: Kamble, Nitin A > Cc: Burton, Ross; meta-intel@yoctoproject.org > Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver > > On Tue, Mar 12, 2013 at 05:10:08PM +0200, Kamble, Nitin A wrote: > > > > Hi Laurentiu, > > You can create the patch for the affected libraries as Ross has mentioned > in the other email on this thread. > > If more .pc fixes are needed for EMGD, I will take look at that. > > > > Thanks, > > Nitin > This approach might be trickier than I first thought... And that's because, > apart from the usual fields (like Cflags, Libs) which are easy to fill in, > there are > a few harder ones: Require, Require.private, Libs.private. I'm not 100% I can > do that without having access to EMGD project source code... I can inspect > the .so file to see the libraries it depends on but, again, I cannot > guarantee I'll > have it perfectly right. > > For example I've been looking at the mesa EGL implementation and, from > the .pc file, I have this: > > Requires.private: libdrm >= 2.4.24 x11 xext xdamage xfixes x11-xcb xcb-glx > >= 1.8.1 xxf86vm > Libs.private: -lm -lpthread -ldl > > Inspecting the libEGL.so, I get the following list: > > 0x0001 (NEEDED) Shared library: [libX11-xcb.so.1] > 0x0001 (NEEDED) Shared library: [libxcb-dri2.so.0] > 0x0001 (NEEDED) Shared library: [libxcb-xfixes.so.0] > 0x0001 (NEEDED) Shared library: [libxcb-render.so.0] > 0x0001 (NEEDED) Shared library: [libxcb-shape.so.0] > 0x0001 (NEEDED) Shared library: [libgbm.so.1] > 0x0001 (NEEDED) Shared library: [libglapi.so.0] > 0x0001 (NEEDED) Shared library: [libX11.so.6] > 0x0001 (NEEDED) Shared library: [libxcb.so.1] > 0x0001 (NEEDED) Shared library: [libXau.so.6] > 0x0001 (NEEDED) Shared library: [libXdmcp.so.6] > 0x0001 (NEEDED) Shared library: [libpthread.so.0] > 0x0001 (NEEDED) Shared library: [libudev.so.0] > 0x0001 (NEEDED) Shared library: [librt.so.1] > 0x0001 (NEEDED) Shared library: [libdl.so.2] > 0x0001 (NEEDED) Shared library: [libdrm.so.2] > 0x0001 (NEEDED) Shared library: [libc.so.6] > > In the list above, I cannot see libXext.so, yet "xext" appears in > Requires.private package list... Also, I don't know if there is any need for > certain library versions (see libdrm here). > > Anyway, I can start looking into the EMGD .so files and come up with some pc > files. Hopefully, they'll work. > > Thanks, > Laurentiu Hi Laurentiu, Thanks for looking into this. As EMGD is closed source, we will not be able to look into it's sources. The best we can do is reverse engineering what you are already doing. I understand it is hard to get it perfect from this way. But I guess we can get something working at least. And improve it as we go forward. BTW I am also pinging the EMGD team who develops the EMGD packages, to start looking into these pkgconfig issues. If we can get some pkgconfig files from them, then we can avoid all this guess work. But I am not expecting anything from them quickly. Nitin ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On 12 March 2013 09:25, Laurentiu Palcu wrote: > This approach might be trickier than I first thought... And that's > because, apart from the usual fields (like Cflags, Libs) which are easy > to fill in, there are a few harder ones: Require, Require.private, > Libs.private. I'm not 100% I can do that without having access to EMGD > project source code... I can inspect the .so file to see the libraries > it depends on but, again, I cannot guarantee I'll have it perfectly right. You'll soon discover when stuff doesn't link, so just leave those lines out for now. Generally they're only used for static linking. Ross ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Tue, Mar 12, 2013 at 05:10:08PM +0200, Kamble, Nitin A wrote: > > Hi Laurentiu, > You can create the patch for the affected libraries as Ross has mentioned > in the other email on this thread. > If more .pc fixes are needed for EMGD, I will take look at that. > > Thanks, > Nitin This approach might be trickier than I first thought... And that's because, apart from the usual fields (like Cflags, Libs) which are easy to fill in, there are a few harder ones: Require, Require.private, Libs.private. I'm not 100% I can do that without having access to EMGD project source code... I can inspect the .so file to see the libraries it depends on but, again, I cannot guarantee I'll have it perfectly right. For example I've been looking at the mesa EGL implementation and, from the .pc file, I have this: Requires.private: libdrm >= 2.4.24 x11 xext xdamage xfixes x11-xcb xcb-glx >= 1.8.1 xxf86vm Libs.private: -lm -lpthread -ldl Inspecting the libEGL.so, I get the following list: 0x0001 (NEEDED) Shared library: [libX11-xcb.so.1] 0x0001 (NEEDED) Shared library: [libxcb-dri2.so.0] 0x0001 (NEEDED) Shared library: [libxcb-xfixes.so.0] 0x0001 (NEEDED) Shared library: [libxcb-render.so.0] 0x0001 (NEEDED) Shared library: [libxcb-shape.so.0] 0x0001 (NEEDED) Shared library: [libgbm.so.1] 0x0001 (NEEDED) Shared library: [libglapi.so.0] 0x0001 (NEEDED) Shared library: [libX11.so.6] 0x0001 (NEEDED) Shared library: [libxcb.so.1] 0x0001 (NEEDED) Shared library: [libXau.so.6] 0x0001 (NEEDED) Shared library: [libXdmcp.so.6] 0x0001 (NEEDED) Shared library: [libpthread.so.0] 0x0001 (NEEDED) Shared library: [libudev.so.0] 0x0001 (NEEDED) Shared library: [librt.so.1] 0x0001 (NEEDED) Shared library: [libdl.so.2] 0x0001 (NEEDED) Shared library: [libdrm.so.2] 0x0001 (NEEDED) Shared library: [libc.so.6] In the list above, I cannot see libXext.so, yet "xext" appears in Requires.private package list... Also, I don't know if there is any need for certain library versions (see libdrm here). Anyway, I can start looking into the EMGD .so files and come up with some pc files. Hopefully, they'll work. Thanks, Laurentiu ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
> -Original Message-
> From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
> boun...@yoctoproject.org] On Behalf Of Laurentiu Palcu
> Sent: Friday, March 08, 2013 12:58 AM
> To: Burton, Ross
> Cc: meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
>
>
>
> On 03/07/2013 09:00 PM, Burton, Ross wrote:
> > On 7 March 2013 12:57, Laurentiu Palcu
> wrote:
> >> Hmmm, it seems that libva-egl package is not built because, in the
> >> new version, the check for egl availability is done using pkg-config.
> >> And the emgd-driver-bin does not provide an egl.pc file...
> >>
> >> There are 4 solutions to this:
> >> * make libva use the old method of detecting egl, so it builds
> >> libva-egl anyway;
> >> * override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately
> to configure.
> >>I tested it and it worked fine adding the following snippet to libva
> >> recipe:
> >>
> >> do_configure_prepend () {
> >> export EGL_CFLAGS="-I${STAGING_INCDIR}"
> >> export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
> >> }
> >>
> >> * we talk with the egmd maintainers to include *.pc file in the
> >> package;
> >> * we create the *.pc files ourselves;
> >>
> >> What do you guys think?
> >
> > More than this will be looking for egl.pc, so create it ourselves in
> > the short term and talk to the EMGD guys so they add it for the long
> > term.
> I can create the egl.pc file, no problem. The problem is the egmd-driver-bin
> package bundles another 14 libraries, besides libEGL...
> We should write a .pc file for each, if we want to be thorough and conform to
> pkg-config guide: "Each file is best used to describe a single library, so
> each
> package should have at least as many pkg-config files as they do installed
> libraries".
>
> However, I'm not familiar with all those libraries and I cannot guarantee the
> .pc files will be correct.
>
> If you only want the egl.pc file, no problem.
>
> Laurentiu
Hi Laurentiu,
You can create the patch for the affected libraries as Ross has mentioned in
the other email on this thread.
If more .pc fixes are needed for EMGD, I will take look at that.
Thanks,
Nitin
>
> >
> > Ross
> >
> ___
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On 8 March 2013 08:57, Laurentiu Palcu wrote: > I can create the egl.pc file, no problem. The problem is the > egmd-driver-bin package bundles another 14 libraries, besides libEGL... > We should write a .pc file for each, if we want to be thorough and > conform to pkg-config guide: "Each file is best used to describe a > single library, so each package should have at least as many pkg-config > files as they do installed libraries". We just need to match what Mesa does here and is relevant to EMGD, so gl.pc glesv2.pc gles1_cm.pc egl.pc. Ross ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On 03/07/2013 09:00 PM, Burton, Ross wrote:
> On 7 March 2013 12:57, Laurentiu Palcu wrote:
>> Hmmm, it seems that libva-egl package is not built because, in the new
>> version, the check for egl availability is done using pkg-config. And
>> the emgd-driver-bin does not provide an egl.pc file...
>>
>> There are 4 solutions to this:
>> * make libva use the old method of detecting egl, so it builds libva-egl
>> anyway;
>> * override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately to
>> configure.
>>I tested it and it worked fine adding the following snippet to libva
>> recipe:
>>
>> do_configure_prepend () {
>> export EGL_CFLAGS="-I${STAGING_INCDIR}"
>> export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
>> }
>>
>> * we talk with the egmd maintainers to include *.pc file in the package;
>> * we create the *.pc files ourselves;
>>
>> What do you guys think?
>
> More than this will be looking for egl.pc, so create it ourselves in
> the short term and talk to the EMGD guys so they add it for the long
> term.
I can create the egl.pc file, no problem. The problem is the
egmd-driver-bin package bundles another 14 libraries, besides libEGL...
We should write a .pc file for each, if we want to be thorough and
conform to pkg-config guide: "Each file is best used to describe a
single library, so each package should have at least as many pkg-config
files as they do installed libraries".
However, I'm not familiar with all those libraries and I cannot
guarantee the .pc files will be correct.
If you only want the egl.pc file, no problem.
Laurentiu
>
> Ross
>
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
> -Original Message-
> From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
> boun...@yoctoproject.org] On Behalf Of Tom Zanussi
> Sent: Thursday, March 07, 2013 6:53 AM
> To: Palcu, Laurentiu
> Cc: meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
>
> On Thu, 2013-03-07 at 14:57 +0200, Laurentiu Palcu wrote:
> > On Wed, Mar 06, 2013 at 03:11:19PM -0600, Tom Zanussi wrote:
> > >
> > > OK, freedesktop.org is back, but now get this in do_rootfs, for
> > > crownbay:
> > >
> > >
> > > | Computing transaction...error: Can't install
> > > | va-intel-1.0-r1@core2: no
> > > package provides libva-egl
> > > |
> > > | Saving cache...
> > > |
> > > | ERROR: Function failed: do_rootfs
> > > (see
> > > /usr/local/dev/yocto/nitin-test/build/tmp/work/crownbay-poky-linux/c
> > > ore-image-sato/1.0-r0/temp/log.do_rootfs.3779 for further
> > > information)
> > > ERROR: Task 7
> > > (/usr/local/dev/yocto/nitin-test/meta/recipes-sato/images/core-image-
> sato.bb, do_rootfs) failed with exit code '1'
> > >
> > > poky/master is at:
> > >
> > > commit 6663b79452bcdd95fc69e1ec853baae6c5297ab2
> > > Author: Andreas Oberritter
> > > Date: Tue Mar 5 18:56:40 2013 +0100
> > >
> > > libpcap: fix description variable
> > >
> > > in local.conf:
> > >
> > > MACHINE ??= "crownbay"
> > > LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16
> commercial"
> > >
> > > Tom
> > >
> > Hmmm, it seems that libva-egl package is not built because, in the new
> > version, the check for egl availability is done using pkg-config. And
> > the emgd-driver-bin does not provide an egl.pc file...
> >
> > There are 4 solutions to this:
> > * make libva use the old method of detecting egl, so it builds
> > libva-egl anyway;
> > * override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately
> to configure.
> >I tested it and it worked fine adding the following snippet to libva
> > recipe:
> >
> > do_configure_prepend () {
> > export EGL_CFLAGS="-I${STAGING_INCDIR}"
> > export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
> > }
> >
> > * we talk with the egmd maintainers to include *.pc file in the
> > package;
> > * we create the *.pc files ourselves;
> >
> > What do you guys think?
> >
>
> I'll leave it up to Nitin since he's the one who's been working with emgd
> lately
> and requested this upgrade, but it seems to me it would be good to do
> something we could 'upstream' to the emgd team, so how about the last
> option (create the *.pc files ourselves) and send the results to the emgd
> maintainers and see if they'd be interested?
>
> Tom
>
> > Thanks,
> > Laurentiu
Laurentiu,
You can provide a patch, and I will review it.
Thanks,
Nitin
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On 7 March 2013 12:57, Laurentiu Palcu wrote:
> Hmmm, it seems that libva-egl package is not built because, in the new
> version, the check for egl availability is done using pkg-config. And
> the emgd-driver-bin does not provide an egl.pc file...
>
> There are 4 solutions to this:
> * make libva use the old method of detecting egl, so it builds libva-egl
> anyway;
> * override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately to
> configure.
>I tested it and it worked fine adding the following snippet to libva
> recipe:
>
> do_configure_prepend () {
> export EGL_CFLAGS="-I${STAGING_INCDIR}"
> export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
> }
>
> * we talk with the egmd maintainers to include *.pc file in the package;
> * we create the *.pc files ourselves;
>
> What do you guys think?
More than this will be looking for egl.pc, so create it ourselves in
the short term and talk to the EMGD guys so they add it for the long
term.
Ross
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Thu, 2013-03-07 at 14:57 +0200, Laurentiu Palcu wrote:
> On Wed, Mar 06, 2013 at 03:11:19PM -0600, Tom Zanussi wrote:
> >
> > OK, freedesktop.org is back, but now get this in do_rootfs, for
> > crownbay:
> >
> >
> > | Computing transaction...error: Can't install va-intel-1.0-r1@core2: no
> > package provides libva-egl
> > |
> > | Saving cache...
> > |
> > | ERROR: Function failed: do_rootfs
> > (see
> > /usr/local/dev/yocto/nitin-test/build/tmp/work/crownbay-poky-linux/core-image-sato/1.0-r0/temp/log.do_rootfs.3779
> > for further information)
> > ERROR: Task 7
> > (/usr/local/dev/yocto/nitin-test/meta/recipes-sato/images/core-image-sato.bb,
> > do_rootfs) failed with exit code '1'
> >
> > poky/master is at:
> >
> > commit 6663b79452bcdd95fc69e1ec853baae6c5297ab2
> > Author: Andreas Oberritter
> > Date: Tue Mar 5 18:56:40 2013 +0100
> >
> > libpcap: fix description variable
> >
> > in local.conf:
> >
> > MACHINE ??= "crownbay"
> > LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16 commercial"
> >
> > Tom
> >
> Hmmm, it seems that libva-egl package is not built because, in the new
> version, the check for egl availability is done using pkg-config. And
> the emgd-driver-bin does not provide an egl.pc file...
>
> There are 4 solutions to this:
> * make libva use the old method of detecting egl, so it builds libva-egl
> anyway;
> * override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately to
> configure.
>I tested it and it worked fine adding the following snippet to libva
> recipe:
>
> do_configure_prepend () {
> export EGL_CFLAGS="-I${STAGING_INCDIR}"
> export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
> }
>
> * we talk with the egmd maintainers to include *.pc file in the package;
> * we create the *.pc files ourselves;
>
> What do you guys think?
>
I'll leave it up to Nitin since he's the one who's been working with
emgd lately and requested this upgrade, but it seems to me it would be
good to do something we could 'upstream' to the emgd team, so how about
the last option (create the *.pc files ourselves) and send the results
to the emgd maintainers and see if they'd be interested?
Tom
> Thanks,
> Laurentiu
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Wed, Mar 06, 2013 at 03:11:19PM -0600, Tom Zanussi wrote:
>
> OK, freedesktop.org is back, but now get this in do_rootfs, for
> crownbay:
>
>
> | Computing transaction...error: Can't install va-intel-1.0-r1@core2: no
> package provides libva-egl
> |
> | Saving cache...
> |
> | ERROR: Function failed: do_rootfs
> (see
> /usr/local/dev/yocto/nitin-test/build/tmp/work/crownbay-poky-linux/core-image-sato/1.0-r0/temp/log.do_rootfs.3779
> for further information)
> ERROR: Task 7
> (/usr/local/dev/yocto/nitin-test/meta/recipes-sato/images/core-image-sato.bb,
> do_rootfs) failed with exit code '1'
>
> poky/master is at:
>
> commit 6663b79452bcdd95fc69e1ec853baae6c5297ab2
> Author: Andreas Oberritter
> Date: Tue Mar 5 18:56:40 2013 +0100
>
> libpcap: fix description variable
>
> in local.conf:
>
> MACHINE ??= "crownbay"
> LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16 commercial"
>
> Tom
>
Hmmm, it seems that libva-egl package is not built because, in the new
version, the check for egl availability is done using pkg-config. And
the emgd-driver-bin does not provide an egl.pc file...
There are 4 solutions to this:
* make libva use the old method of detecting egl, so it builds libva-egl
anyway;
* override pkg-config by providing EGL_CFLAGS and EGL_LIBS separately to
configure.
I tested it and it worked fine adding the following snippet to libva recipe:
do_configure_prepend () {
export EGL_CFLAGS="-I${STAGING_INCDIR}"
export EGL_LIBS="-L${STAGING_LIBDIR} -lEGL"
}
* we talk with the egmd maintainers to include *.pc file in the package;
* we create the *.pc files ourselves;
What do you guys think?
Thanks,
Laurentiu
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Wed, 2013-03-06 at 09:55 -0600, Tom Zanussi wrote:
> On Wed, 2013-03-06 at 10:58 +0200, Laurentiu Palcu wrote:
> > Ping!
> >
>
> Yeah, trying to build this, looks like freedesktop.org is down, will
> have to wait for it to come back...
>
> ERROR: Fetcher failure: Fetch command failed with exit code 8, output:
> http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.1.0.tar.bz2:
> 2013-03-06 09:38:32 ERROR 503: Service Unavailable.
>
OK, freedesktop.org is back, but now get this in do_rootfs, for
crownbay:
| Computing transaction...error: Can't install va-intel-1.0-r1@core2: no
package provides libva-egl
|
| Saving cache...
|
| ERROR: Function failed: do_rootfs
(see
/usr/local/dev/yocto/nitin-test/build/tmp/work/crownbay-poky-linux/core-image-sato/1.0-r0/temp/log.do_rootfs.3779
for further information)
ERROR: Task 7
(/usr/local/dev/yocto/nitin-test/meta/recipes-sato/images/core-image-sato.bb,
do_rootfs) failed with exit code '1'
poky/master is at:
commit 6663b79452bcdd95fc69e1ec853baae6c5297ab2
Author: Andreas Oberritter
Date: Tue Mar 5 18:56:40 2013 +0100
libpcap: fix description variable
in local.conf:
MACHINE ??= "crownbay"
LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16 commercial"
Tom
> ERROR: Function failed: Fetcher failure for URL:
> 'http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.1.0.tar.bz2'.
> Unable to fetch URL from any source.
> ERROR: Logfile of failure stored in:
> /usr/local/dev/yocto/nitin-test/build/tmp/work/core2-poky-linux/libva/1.1.0-r1.0/temp/log.do_fetch.18404
> ERROR: Task 2307
> (/usr/local/dev/yocto/nitin-test/meta-intel/common/recipes-multimedia/libva/libva_1.1.0.bb,
> do_fetch) failed with exit code '1'
>
>
> > On 02/27/2013 12:35 PM, Laurentiu Palcu wrote:
> > > Laurentiu Palcu (2):
> > > libva-intel-driver: upgrade to 1.0.19
> > > libva: upgrade to 1.1.0
> > >
> > > ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> > > ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> > > .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> > > 3 files changed, 4 insertions(+), 4 deletions(-)
> > > rename common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> > > libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC1-and-H264-vid.patch
> > > (100%)
> > > rename common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> > > libva-intel-driver_1.0.19.bb} (64%)
> > > rename common/recipes-multimedia/libva/{libva_1.0.16.bb =>
> > > libva_1.1.0.bb} (47%)
> > >
> > ___
> > meta-intel mailing list
> > meta-intel@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-intel
>
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
> -Original Message-
> From: Zanussi, Tom
> Sent: Wednesday, March 06, 2013 9:16 AM
> To: Kamble, Nitin A
> Cc: Palcu, Laurentiu; meta-intel@yoctoproject.org; Darren Hart
> (dvh...@linux.intel.com)
> Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
>
> On Wed, 2013-03-06 at 11:14 -0600, Kamble, Nitin A wrote:
> > Hi Tom, Darren,
> > These commits are still not pulled in. And seems like Laurentiu did not
> > get
> any feedback as well.
> > I guess these patches got lost in the ELC time. Is there any reason to
> holding these commits?
> > If not can these be merged upstream?
> >
>
> I sent a reply a little while ago - freedesktop.org is down so I can't test
> these -
> I will once it's back up.
>
Thanks for the update Tom. Looks like the meta-intel ML is slow in delivering
emails. I still have not received your earlier response.
Nitin
> Tom
>
> > Thanks,
> > Nitin
> >
> >
> > > -Original Message-
> > > From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
> > > boun...@yoctoproject.org] On Behalf Of Laurentiu Palcu
> > > Sent: Wednesday, March 06, 2013 12:59 AM
> > > To: meta-intel@yoctoproject.org
> > > Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva &
> > > libva-intel-driver
> > >
> > > Ping!
> > >
> > > On 02/27/2013 12:35 PM, Laurentiu Palcu wrote:
> > > > Laurentiu Palcu (2):
> > > > libva-intel-driver: upgrade to 1.0.19
> > > > libva: upgrade to 1.1.0
> > > >
> > > > ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> > > > ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> > > > .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> > > > 3 files changed, 4 insertions(+), 4 deletions(-) rename
> > > > common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> > > > libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playin
> > > > g-VC 1-and-H264-vid.patch (100%) rename
> > > > common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> > > > libva-intel-driver_1.0.19.bb} (64%) rename
> > > > common/recipes-multimedia/libva/{libva_1.0.16.bb =>
> > > > libva_1.1.0.bb}
> > > > (47%)
> > > >
> > > ___
> > > meta-intel mailing list
> > > meta-intel@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/meta-intel
>
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Wed, 2013-03-06 at 11:14 -0600, Kamble, Nitin A wrote:
> Hi Tom, Darren,
> These commits are still not pulled in. And seems like Laurentiu did not get
> any feedback as well.
> I guess these patches got lost in the ELC time. Is there any reason to
> holding these commits?
> If not can these be merged upstream?
>
I sent a reply a little while ago - freedesktop.org is down so I can't
test these - I will once it's back up.
Tom
> Thanks,
> Nitin
>
>
> > -Original Message-
> > From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
> > boun...@yoctoproject.org] On Behalf Of Laurentiu Palcu
> > Sent: Wednesday, March 06, 2013 12:59 AM
> > To: meta-intel@yoctoproject.org
> > Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
> >
> > Ping!
> >
> > On 02/27/2013 12:35 PM, Laurentiu Palcu wrote:
> > > Laurentiu Palcu (2):
> > > libva-intel-driver: upgrade to 1.0.19
> > > libva: upgrade to 1.1.0
> > >
> > > ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> > > ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> > > .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> > > 3 files changed, 4 insertions(+), 4 deletions(-) rename
> > > common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> > > libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC
> > > 1-and-H264-vid.patch (100%) rename
> > > common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> > > libva-intel-driver_1.0.19.bb} (64%) rename
> > > common/recipes-multimedia/libva/{libva_1.0.16.bb => libva_1.1.0.bb}
> > > (47%)
> > >
> > ___
> > meta-intel mailing list
> > meta-intel@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-intel
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
Hi Tom, Darren,
These commits are still not pulled in. And seems like Laurentiu did not get
any feedback as well.
I guess these patches got lost in the ELC time. Is there any reason to holding
these commits?
If not can these be merged upstream?
Thanks,
Nitin
> -Original Message-
> From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel-
> boun...@yoctoproject.org] On Behalf Of Laurentiu Palcu
> Sent: Wednesday, March 06, 2013 12:59 AM
> To: meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
>
> Ping!
>
> On 02/27/2013 12:35 PM, Laurentiu Palcu wrote:
> > Laurentiu Palcu (2):
> > libva-intel-driver: upgrade to 1.0.19
> > libva: upgrade to 1.1.0
> >
> > ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> > ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> > .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> > 3 files changed, 4 insertions(+), 4 deletions(-) rename
> > common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> > libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC
> > 1-and-H264-vid.patch (100%) rename
> > common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> > libva-intel-driver_1.0.19.bb} (64%) rename
> > common/recipes-multimedia/libva/{libva_1.0.16.bb => libva_1.1.0.bb}
> > (47%)
> >
> ___
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
On Wed, 2013-03-06 at 10:58 +0200, Laurentiu Palcu wrote:
> Ping!
>
Yeah, trying to build this, looks like freedesktop.org is down, will
have to wait for it to come back...
ERROR: Fetcher failure: Fetch command failed with exit code 8, output:
http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.1.0.tar.bz2:
2013-03-06 09:38:32 ERROR 503: Service Unavailable.
ERROR: Function failed: Fetcher failure for URL:
'http://www.freedesktop.org/software/vaapi/releases/libva/libva-1.1.0.tar.bz2'.
Unable to fetch URL from any source.
ERROR: Logfile of failure stored in:
/usr/local/dev/yocto/nitin-test/build/tmp/work/core2-poky-linux/libva/1.1.0-r1.0/temp/log.do_fetch.18404
ERROR: Task 2307
(/usr/local/dev/yocto/nitin-test/meta-intel/common/recipes-multimedia/libva/libva_1.1.0.bb,
do_fetch) failed with exit code '1'
> On 02/27/2013 12:35 PM, Laurentiu Palcu wrote:
> > Laurentiu Palcu (2):
> > libva-intel-driver: upgrade to 1.0.19
> > libva: upgrade to 1.1.0
> >
> > ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> > ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> > .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> > 3 files changed, 4 insertions(+), 4 deletions(-)
> > rename common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> > libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC1-and-H264-vid.patch
> > (100%)
> > rename common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> > libva-intel-driver_1.0.19.bb} (64%)
> > rename common/recipes-multimedia/libva/{libva_1.0.16.bb => libva_1.1.0.bb}
> > (47%)
> >
> ___
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
Ping!
On 02/27/2013 12:35 PM, Laurentiu Palcu wrote:
> Laurentiu Palcu (2):
> libva-intel-driver: upgrade to 1.0.19
> libva: upgrade to 1.1.0
>
> ...for-concurrently-playing-VC1-and-H264-vid.patch |0
> ...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
> .../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
> rename common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
> libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC1-and-H264-vid.patch
> (100%)
> rename common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
> libva-intel-driver_1.0.19.bb} (64%)
> rename common/recipes-multimedia/libva/{libva_1.0.16.bb => libva_1.1.0.bb}
> (47%)
>
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
[meta-intel] [PATCH 0/2] upgrade libva & libva-intel-driver
Laurentiu Palcu (2):
libva-intel-driver: upgrade to 1.0.19
libva: upgrade to 1.1.0
...for-concurrently-playing-VC1-and-H264-vid.patch |0
...iver_1.0.18.bb => libva-intel-driver_1.0.19.bb} |4 ++--
.../libva/{libva_1.0.16.bb => libva_1.1.0.bb} |4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
rename common/recipes-multimedia/libva/{libva-intel-driver-1.0.18 =>
libva-intel-driver-1.0.19}/0001-Workaround-for-concurrently-playing-VC1-and-H264-vid.patch
(100%)
rename common/recipes-multimedia/libva/{libva-intel-driver_1.0.18.bb =>
libva-intel-driver_1.0.19.bb} (64%)
rename common/recipes-multimedia/libva/{libva_1.0.16.bb => libva_1.1.0.bb}
(47%)
--
1.7.9.5
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel
