Re: [meta-intel] [poky] Yocto kernel compilation issues

f this (and many other things) for you. I guess you based your recipe on linux-dummy.bb, but that recipe is special and shouldn't be used as a template for a real kernel. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre --

Re: [meta-intel] Issue with ovmf license under Pyro

I sync on meta-intel agin. > > > > Any help would be welcome. > > Log and corrective patches are bellow. > > > That's not really an acceptable patch for this situation. > > Sau! > > > Any help would be welcome. > > > -- Paul E

Re: [meta-intel] [PATCH] meta-intel.inc: Avoid installing thermald on poky-tiny

h things. > > > And Distro's don't know what a BSP might pull in, so they can't > directly _remove or exclude them somehow. They should - the distro is where you make all of these kinds of decisions, if you're creating the distro then you will have some idea of w

Re: [meta-intel] meta-mono build boot kernel panic

and then you can completely specify the value of IMAGE_INSTALL. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH] conf: set recipe maintainers

, so this file having the same name as the one in meta-poky might mask that one out depending on the order of BBLAYERS. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctopro

Re: [meta-intel] [PATCH] IGT: update 1.14 -> 1.15

nge, not when the change is applied. If you want to see the full history including renames, use the --follow option. Saul is correct, use of PV in the recipe filename is standard OE practice and we don't want to be deviating from that - besides which I'm not sure we have much to gain by doing so. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [meta-intel-iot-devkit][PATCH 1/3] local.conf.sample: drop hob-iot references

Since we're no longer using a fork of poky we don't have the customised Hob UI, so remove configuration for it from local.conf.sample. Signed-off-by: Paul Eggleton --- conf/local.conf.sample | 7 --- 1 file changed, 7 deletions(-) diff --git a/conf/local.conf.sam

[meta-intel] [meta-intel-iot-devkit][PATCH 3/3] conf/distro/include/iot-devkit.inc: drop cache path manipulation

; you should be able to just move the old sstate-cache directory to the default location and let the rest be re-generated. Signed-off-by: Paul Eggleton --- conf/distro/include/iot-devkit.inc | 4 1 file changed, 4 deletions(-) diff --git a/conf/distro/include/iot-devkit.inc b/conf/distro/includ

[meta-intel] [meta-intel-iot-devkit][PATCH 0/3] Tidy up some old cruft

git://git.yoctoproject.org/poky-contrib paule/iot-devkit-cleanup http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/iot-devkit-cleanup Paul Eggleton (3): local.conf.sample: drop hob-iot references Drop locked sstate configuration files and references conf/distro/include

Re: [meta-intel] [dizzy][PATCH 2/2] meta-crystalforest: rename zlib-qat recipe

his shouldn't cause a problem, the underscore is where it will split PN and PV. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] "Crazy" Xorg memory usage after upgrading from Daisy to Fido

Are there any significant changes between XOrg under Daisy and Fido that > could be causing this? > > Could this be related to the meta-intel video drivers? > > Any feedback / comments would be really appreciated. > > Thanks :-) > > -- > > Chris Tapp > opens

[meta-intel] [meta-intel-iot-devkit][PATCH 5/5] README: make some clarifications

zilla entries, so let's explicitly state that Signed-off-by: Paul Eggleton --- README | 21 - 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/README b/README index a18b7b2..451cfbf 100644 --- a/README +++ b/README @@ -2,16 +2,16 @@ meta-intel-

[meta-intel] [meta-intel-iot-devkit][PATCH 3/5] opencv: just use = to set PACKAGECONFIG

We're choosing the PACKAGECONFIG value as distro policy, so we should just set it with = rather than weakly defaulting it with ??=. Signed-off-by: Paul Eggleton --- recipes-support/opencv/opencv_2.%.bbappend | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-su

[meta-intel] [meta-intel-iot-devkit][PATCH 4/5] iot-devkit.inc: set more appropriate MAINTAINER value

Signed-off-by: Paul Eggleton --- conf/distro/include/iot-devkit.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/distro/include/iot-devkit.inc b/conf/distro/include/iot-devkit.inc index 9ebbb4c..bebfac5 100644 --- a/conf/distro/include/iot-devkit.inc +++ b/conf

[meta-intel] [meta-intel-iot-devkit][PATCH 1/5] iot-devkit-image: remove some cruft

ilib-lib32 at the configuration level and doesn't really affect the image itself anyway Signed-off-by: Paul Eggleton --- recipes-core/images/iot-devkit-image.bb | 7 --- 1 file changed, 7 deletions(-) diff --git a/recipes-core/images/iot-devkit-image.bb b/recipes-core/images/iot-

[meta-intel] [meta-intel-iot-devkit][PATCH 2/5] openssh: drop inherit systemd

The openssh recipe already inherits systemd so we don't need to do that here as well. Signed-off-by: Paul Eggleton --- recipes-connectivity/openssh/openssh_%.bbappend | 1 - 1 file changed, 1 deletion(-) diff --git a/recipes-connectivity/openssh/openssh_%.bbappend b/recipes-connect

[meta-intel] [meta-intel-iot-devkit][PATCH 0/5] Misc tidy-ups for IoT DevKit

://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/iot-devkit-fixes Paul Eggleton (5): iot-devkit-image: remove some cruft openssh: drop inherit systemd opencv: just use = to set PACKAGECONFIG iot-devkit.inc: set more appropriate MAINTAINER value README: make some clarifications README

Re: [meta-intel] [meta-intel-galileo] [PATCH 2/3] launcher.sh: start clloader only on galileo

+ > > > +galileo_board=false > > > +type dmidecode > /dev/null 2>&1 || die "dmidecode not installed" > > > +board=$(dmidecode -s baseboard-product-name) case "$board" in > > > +*"Galileo" ) > > >

Re: [meta-intel] [PATCH 1/1 daisy/dizzy] meta-crystalforest: Initial Intel QAT recipe

service was available and recommended for PR increments in daisy. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 0/1 daisy/dizzy]: meta-crystalforest:Initial Intel QAT-core Implementation

-dh89xxcc" > > PACKAGES += "${PN}-dbg-dh895xcc > > -dbg has a specific meaning in yocto and impacts the QA checks and other > packaging routines. I believe these should properly be named: > > ${PN}-dh89xxcc-dbg This is correct, although strictly speaking we try

Re: [meta-intel] [yocto] GStreamer1.0 : gstreamer1.0-plugins-* doesn't extract the codec libraries into GStreamer library path

won't actually install any plugins. There is a -meta package for each of these which does pull in all of the plugin packages (e.g. gstreamer1.0-plugins-good-meta), or alternatively you can specify plugin packages individually if you want more control. Cheers, Paul -- Paul Eggleton Intel Op

Re: [meta-intel] [PATCH 1/1] README: Documentation of hardware features

Hi Nitin, On Friday 03 October 2014 16:33:28 Kamble, Nitin A wrote: > On 10/3/14, 4:15 AM, "Paul Eggleton" wrote: > >On Thursday 02 October 2014 14:14:41 nitin.a.kam...@intel.com wrote: > >> From: Nitin A Kamble > >> > >> Starting a new docume

Re: [meta-intel] [PATCH 1/1] README: Documentation of hardware features

gies.) Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/1] README.hardware: Documentation of hardware features

Darren ack first. AIUI README.hardware is supposed to be for "how do I make use of artifacts built from this BSP on the hardware", which is not really what this is. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 2/3] meta-intel/common: Upgrade DPDK to v1.7.0

;compilation of these examples. > >> > > Hi Sreeju, > > > > Why not add dependency recipes to get it fully functional? > > fuse is in meta-filesystems, so the best practises here would be some > form of enable/disable variable to control whether its enabled or not. PACKAGE

Re: [meta-intel] meta-iot-devkit Maintainer

you have a look at that when you can? Thanks, Paul [1] https://lists.yoctoproject.org/pipermail/meta-intel/2014-August/002426.html -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctop

Re: [meta-intel] Use of overrides in linux-yocto bbappends

On Friday 11 April 2014 17:38:46 Chris Tapp wrote: > On 11 Apr 2014, at 16:37, Paul Eggleton > wrote: > > ... > > I can throw together a patch to fix it, but we'll also need to make sure > > new BSPs added in future use overrides as well. Any suggestions on

Re: [meta-intel] Use of overrides in linux-yocto bbappends

On Friday 11 April 2014 08:49:17 Darren Hart wrote: > On 4/11/14, 8:37, "Paul Eggleton" wrote: > >Koen reported that with a recent change to meta-minnow where > >LINUX_VERSION = > >"something" changed to LINUX_VERSION_minnow = "something" (whic

[meta-intel] Use of overrides in linux-yocto bbappends

suggestions on how to handle the latter? Is this a documentation issue? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCHv2 4/5] meta-valleyisland: add kernel recipe for valleyisland

On Monday 24 March 2014 15:16:56 Darren Hart wrote: > On 3/24/14, 15:11, "Paul Eggleton" wrote: > >On Monday 24 March 2014 15:07:10 Darren Hart wrote: > >> On 3/24/14, 10:57, "rebecca.swee.fun.ch...@intel.com" > >> > >> wrote: > >>

Re: [meta-intel] [PATCHv2 4/5] meta-valleyisland: add kernel recipe for valleyisland

another recommendation here... What concerns you about using = here? I would have thought it was OK in this situation; ?= is only really helpful where you want to apply a default where a value that should override the default may already have been set (e.g. in local.conf where a desired value mi

Re: [meta-intel] gpio sus configuration as interrupt

df > > And I think there is video. but I can't seem to find it. Perhaps your > google foo will prove superior ;-) http://www.youtube.com/watch?v=IZuNCN7wkqs (I watched it recently - great presentation BTW :) Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre --

Re: [meta-intel] File missing in corei7 bsp

ere; conf/machine/include/tune-corei7.inc is part of the master branch of OE-Core (and therefore also Poky). You won't be able to use a BSP that relies upon it with earlier stable branches, unless you also add the tune files - Darren, is this supported? Cheers, Paul -- Paul E

[meta-intel] [meta-minnow][PATCH] dmidecode: remove

OE-Core has version 2.12 of this recipe in the dora and master branches. Signed-off-by: Paul Eggleton --- recipes-core/dmidecode/dmidecode_2.11.bb | 26 -- 1 file changed, 26 deletions(-) delete mode 100644 recipes-core/dmidecode/dmidecode_2.11.bb diff --git a/recipes

[meta-intel] [PATCH] yasm: remove

This is now in OE-Core. Signed-off-by: Paul Eggleton --- common/recipes-support/yasm/yasm_1.1.0.bb | 17 - 1 file changed, 17 deletions(-) delete mode 100644 common/recipes-support/yasm/yasm_1.1.0.bb diff --git a/common/recipes-support/yasm/yasm_1.1.0.bb b/common/recipes