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 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 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 00/17] enable YP v3.8 kernel for metal-intel BSPs + misc
On Tue, 2013-03-05 at 17:06 -0800, nitin.a.kam...@intel.com wrote: > From: Nitin A Kamble > > Here is a pull request to enable v3.8 of linux-yocto kernel for these > meta-intel BSPs: > crownbay, crownbay-noemgd > fri2, fri2-noemgd, > emenlow, emenlow-noemgd, > sys940x, sys940x-noemgd, > chiefriver, > nuc, > sugarbay, > jasperforest > > These commits have been built & tested to work as expected on the > respective BSPs. > > Also one more commit for gst-va-intel recipe is made to avoid > a build warning. > Pulled into meta-intel/master (and added a fix for a missed warning for va-intel). Thanks, Tom > Thanks, > Nitin > > The following changes since commit 570ab0c828cec1aa8e4d6bb6b16b456483d23601: > > sys940x: linux-yocto-dev recipe extension (2013-03-04 16:55:34 -0600) > > are available in the git repository at: > git://git.yoctoproject.org/meta-intel-contrib nitin/misc > http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc > > Nitin A Kamble (17): > chiefriver: linux-yocto_3.8 recipe extension > crownbay: linux-yocto_3.8 recipe extension > emenlow: linux-yocto_3.8 recipe extension > fri2: linux-yocto_3.8 recipe extension > nuc: linux-yocto_3.8 recipe extension > sugarbay: linux-yocto_3.8 recipe extension > sys940x: linux-yocto_3.8 recipe extension > jasperforest: linux-yocto_3.8 recipe extension > chiefriver: move BSP to the v3.8 kernel > crownbay crownbay-noemgd: move BSPs to the v3.8 kernel > emenlow emenlow-noemgd: move BSPs to the v3.8 kernel > fri2 fri2-noemgd: move BSPs to the v3.8 kernel > jasperforest: move BSP to the v3.8 kernel > nuc: move BSP to the v3.8 kernel > sugarbay: move BSP to the v3.8 kernel > sys940x sys940x-noemgd: move BSPs to the v3.8 kernel > gst-va-intel: avoid warning regarding ALLOW_EMPTY > > .../recipes-multimedia/gstreamer/gst-va-intel.bb |6 - > meta-chiefriver/conf/machine/chiefriver.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 10 + > meta-crownbay/conf/machine/crownbay-noemgd.conf|2 +- > meta-crownbay/conf/machine/crownbay.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 20 ++ > meta-emenlow/conf/machine/emenlow-noemgd.conf |2 +- > meta-emenlow/conf/machine/emenlow.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 20 ++ > meta-fri2/conf/machine/fri2-noemgd.conf|2 +- > meta-fri2/conf/machine/fri2.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 20 ++ > meta-jasperforest/conf/machine/jasperforest.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend |9 > meta-nuc/conf/machine/nuc.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 12 ++ > meta-sugarbay/conf/machine/sugarbay.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend |9 > meta-sys940x/conf/machine/sys940x-noemgd.conf |2 +- > meta-sys940x/conf/machine/sys940x.conf |2 +- > .../recipes-kernel/linux/linux-yocto_3.8.bbappend | 22 > > 21 files changed, 139 insertions(+), 13 deletions(-) > create mode 100644 > meta-chiefriver/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 > meta-crownbay/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 meta-emenlow/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 meta-fri2/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 > meta-jasperforest/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 meta-nuc/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 > meta-sugarbay/recipes-kernel/linux/linux-yocto_3.8.bbappend > create mode 100644 meta-sys940x/recipes-kernel/linux/linux-yocto_3.8.bbappend > ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] [Patch v2 0/1] fix for fri2-noemgd BSP's X
On Tue, 2013-02-05 at 15:18 -0800, nitin.a.kam...@intel.com wrote: > From: Nitin A Kamble > > This v2 pull request adds to commit message some information about > different firmwares available on the FRI2 systems, as it relates > to the issue. > Pulled into meta-intel/master. Thanks, Tom > Thanks, > Nitin > > The following changes since commit 706a62e662dde79bc4e7ec0f81b76890e49f4beb: > > fri2: use EMGD version 1.16 instead of 1.14 (2013-02-01 09:52:33 -0600) > > are available in the git repository at: > git://git.yoctoproject.org/meta-intel-contrib nitin/misc > http://git.yoctoproject.org/cgit.cgi/meta-intel-contrib/log/?h=nitin/misc > > Nitin A Kamble (1): > fri2-noemgd: use fbdev X driver > > meta-fri2/conf/machine/fri2-noemgd.conf|2 +- > .../xserver-xf86-config/fri2-noemgd/xorg.conf |2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > ___ 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
