Re: [meta-intel] Config warning with pyro default Intel Kernel

Hi, On Thu, Sep 21, 2017 at 10:00 AM, Dominig ar Foll (Intel Open Source) < dominig.arf...@fridu.net> wrote: > Mikko, > > I would have expected that using meta-intel and base yocto configuration, > I would get a build without any warning. > I that a correct assumption ? or is there warnings when

Re: [meta-intel] [PATCH 1/2] systemd-boot: use RMC database in EFI stub

Hi, On Fri, Jan 27, 2017 at 6:05 PM, Wold, Saul wrote: > On Fri, 2017-01-27 at 15:36 +0200, Mikko Ylinen wrote: > > systemd-boot's EFI stub can be built in an EFI executable > > with the kernel, cmdline, and initrd. > > > > This commit enables the EFI stub code to use the

Re: [meta-intel] [OE-core] [PATCH 2/2] gstreamer1.0-vaapi: Import from meta-intel

Hi, On Tue, Dec 6, 2016 at 12:48 PM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 6 December 2016 at 09:57, Ylinen, Mikko <mikko.yli...@intel.com> wrote: > >> This suggests the versions should be kept in sync with the gstreamer >> versions: >> http://

Re: [meta-intel] Why libva-egl1 request x11 in a Wayland configuration

Hi Dominig, On Mon, Dec 5, 2016 at 4:39 PM, Dominig ar Foll (Intel Open Source) < dominig.arf...@fridu.net> wrote: > Jussi, > I suspect something like that as well, but I am surprised that no-one is > facing the same bug. People using Wyaland, QT and trying to build and SDK > should not be new.

Re: [meta-intel] [OE-core] [PATCH 2/2] gstreamer1.0-vaapi: Import from meta-intel

Hi, On Fri, Dec 2, 2016 at 9:32 PM, Khem Raj wrote: > Update to 1.10.1 at the same time > This suggests the versions should be kept in sync with the gstreamer versions: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=3f51f61efe93c104ba7996f54f381c6c1a5e6546

Re: [meta-intel] [PATCH] gstreamer-vaapi and libva: check for opengl feature.

Hi, On Thu, Dec 1, 2016 at 10:09 AM, Puustinen, Ismo wrote: > > While these patches are the same, I would prefer if we had 2 distinct > > patches for libva and gstreamer-vaapi. > > Ok, I'll split the patch in two. > > > Is this related to what Mikko found recently with