[yocto] [meta-intel][PATCH 3/3] intel-graphics-compiler: skip it if clang is not ready

Since intel-graphics-compiler depends on clang, skip it if clang is not ready Signed-off-by: Hongxu Jia --- recipes-opencl/igc/intel-graphics-compiler_1.0.6.bb | 8 1 file changed, 8 insertions(+) diff --git a/recipes-opencl/igc/intel-graphics-compiler_1.0.6.bb b/recipes-opencl/igc/in

[yocto] [meta-intel][PATCH 2/3] intel-mediasdk: check for "opengl" feature

Since comit [a78c420 libva: check for "opengl" feature] applied in oe-core, and intel-mediasdk depends on libva, it should check for "opengl" feature too. Signed-off-by: Hongxu Jia --- recipes-multimedia/mediasdk/intel-mediasdk_19.2.0.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/rec

Re: [yocto] "meta-intel" layer bad example of a "container layer"

Robert, I have updated the BSP Guide and removed all but a single instance of "container layer". You can see what I have left at the bottom of this section - https://yoctoproject.org/docs/2.8/bsp-guide/bsp-guide.html#bsp-layers. Also, the YP Reference Manual "Terms" section has been updated with

Re: [yocto] "meta-intel" layer bad example of a "container layer"

Right, meta-intel isn't a container layer. It just has two MACHINES. Ross On Thu, 2 May 2019 at 13:54, Robert P. J. Day wrote: > > > catching up with all the YP stuff i've missed over the last while > and, in the BSP guide in the layers section: > > https://www.yoctoproject.org/docs/latest/bs

[yocto] "meta-intel" layer bad example of a "container layer"

catching up with all the YP stuff i've missed over the last while and, in the BSP guide in the layers section: https://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html#bsp-layers one reads: "Some layers function as a layer to hold other BSP layers. These layers are knows as "containe

Re: [yocto] [meta-intel] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

Thanks a ton Ross, your inputs really worked :) On Tue, Jan 15, 2019 at 11:34 AM Burton, Ross wrote: > > You'll have to not install either connman or network manager. > > Ross > > On Tue, 15 Jan 2019 at 05:18, srinivasan wrote: > > > > Dear Yocto experts, > > > > I am seeing the below error when

Re: [yocto] [meta-intel] ERROR: - package networkmanager-1.10.6-r0.aarch64 conflicts with connman provided by connman-1.35-r0.aarch64

You'll have to not install either connman or network manager. Ross On Tue, 15 Jan 2019 at 05:18, srinivasan wrote: > > Dear Yocto experts, > > I am seeing the below error when I am trying to integrate the > "fsl-image-validation-imx.bb" into my custom yocto build and trigger > the build using "b

Re: [yocto] [meta-intel] fb: switching to inteldrmfb from efi vga

On Tue, 2018-11-13 at 12:30 +0300, Knoppix wrote: > yocto and meta-intel: 2.5.1/sumo > kernel=linux-yocto-4.15.18 > machine=intel-corei7-64 > distro=poky > > the problem is: > when I boot the system it comes to this message and frozees: " fb: > switching to amdgpudrmfb from efi vga" This error sa

Re: [yocto] [meta-intel] ac_nonexistent.h error in do_configure

On Wed, 3 Oct 2018 at 09:40, Anuj Mittal wrote: > This check is supposed to fail. This is a sanity test, that header isn't > supposed to exist and autoconf expects this compilation error. I don't > think this is the actual point of failure. What would be useful is the output of 'bitbake core-imag

Re: [yocto] [meta-intel] ac_nonexistent.h error in do_configure

On 10/02/2018 11:53 PM, Muhlenkamp, Lewis wrote: > configure:4485: x86_64-oe-linux-gcc -E > --sysroot=/home/lmuhlenkamp/build-target02/tmp-glibc/work/corei7-64-oe-linux/xf86-video-intel/2_2.99.917+gitAUTOINC+e4fe79cf0d-r0/recipe-sysroot >   > -m64 -march=nehalem -mtune=generic -mfpmath=sse -msse4.2

Re: [yocto] [meta-intel] Getting black screen for Install option

Hi Anuj, As per your suggestion, I have made the changes for "install option, Still I am getting black screen, Thanks, Dhanasekar On Wed, Aug 8, 2018 at 9:01 PM, Dhanasekar Jaganathan < jdhanasekar...@gmail.com> wrote: > Hi Anuj. You want me to add this change in systemd-boot..? If wron

Re: [yocto] [meta-intel] Getting black screen for Install option

Hi Anuj. You want me to add this change in systemd-boot..? If wrong , please correct me. On Wed 8 Aug, 2018, 7:10 PM Anuj Mittal, wrote: > On 08/08/2018 08:58 PM, Dhanasekar Jaganathan wrote: > > > > Hi All, > > > > I have created yocot bootable USB live image by this command "*sudo dd > > i

Re: [yocto] [meta-intel] Getting black screen for Install option

On 08/08/2018 08:58 PM, Dhanasekar Jaganathan wrote: > > Hi All, > > I have created yocot bootable USB live image by this command "*sudo dd > if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"* > " > > After power on my system, I have got three options, > > 1. boot > 2. install > 3. Reboot

[yocto] [meta-intel] Getting black screen for Install option

Hi All, I have created yocot bootable USB live image by this command "* sudo dd if=core-image-sato-intel-core2-32.hddimg of=/dev/sdb1"* " After power on my system, I have got three options, 1. boot 2. install 3. Reboot into firmware. When I select "install" to install yocto on mSata, I am gett

Re: [yocto] [meta-intel][PATCH] mce-test: add it

Hi Dengke, On 06/01/2018 05:51 PM, Dengke Du wrote: > +SRC_URI = > "git://git.kernel.org/pub/scm/linux/kernel/git/gong.chen/mce-test.git;protocol=git > \ > + file://makefile-remove-ldflags.patch \ > + " > +# Use the commit date of SRCREV in PV. > +# > +SRCREV = "b3fdfaa7a025b6

[yocto] [meta-intel][PATCH] mce-test: add it

Signed-off-by: Dengke Du --- .../mce-test/files/makefile-remove-ldflags.patch | 23 +++ recipes-kernel/mce-test/mce-test_git.bb| 48 ++ 2 files changed, 71 insertions(+) create mode 100644 recipes-kernel/mce-test/files/makefile-remove-ldflags.patch crea

Re: [yocto] [meta-intel] [PATCH] systemd-boot: fix bbappend file to suit latest version

On 03/06/2018 05:51 AM, Cal Sullivan wrote: Thanks for the patch. I assume this is needed when OE-core merges the update to v236? Thanks, Cal Yes. It's needed when OE-core merges the update to v237. Best Regards, Chen Qi On 03/04/2018 06:03 PM, Chen Qi wrote: Fix the bbappend file to sui

Re: [yocto] [meta-intel] [PATCH] systemd-boot: fix bbappend file to suit latest version

Thanks for the patch. I assume this is needed when OE-core merges the update to v236? Thanks, Cal On 03/04/2018 06:03 PM, Chen Qi wrote: Fix the bbappend file to suit the latest systemd version. As systemd has now dropped autotools support, using ninja instead of make in do_compile. Signed-o

[yocto] [meta-intel][PATCH] systemd-boot: fix bbappend file to suit latest version

Fix the bbappend file to suit the latest systemd version. As systemd has now dropped autotools support, using ninja instead of make in do_compile. Signed-off-by: Chen Qi --- recipes-bsp/systemd-boot/systemd-boot_%.bbappend | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/

Re: [yocto] [meta-intel] meta-intel has been split into meta-dpdk and meta-intel-qat

On Thu, 2017-09-28 at 11:32 +0800, Lai Eddy wrote: > is this mean I don't need meta-intel anymore? (but still can be found > in the git) > just choose to use meta-dpdk and/or meta-intel-qat > If you are building an Intel target, I would suggest you still use meta-intel. The DPDK and QAT are speci

Re: [yocto] [meta-intel] meta-intel has been split into meta-dpdk and meta-intel-qat

is this mean I don't need meta-intel anymore? (but still can be found in the git) just choose to use meta-dpdk and/or meta-intel-qat 2017-09-28 11:27 GMT+08:00 Saul Wold : > > In an effort to create more consistency in Yocto Project layer, we are > splitting the meta-intel to remove some applicat

[yocto] meta-intel has been split into meta-dpdk and meta-intel-qat

In an effort to create more consistency in Yocto Project layer, we are splitting the meta-intel to remove some application/libraries that should really be in their own layers. The new meta-dpdk will serve as a place for the Linux Foundation's DPDK project to host meta-data. The meta-intel-qat

Re: [yocto] [meta-intel] How to build module iasImage from bzImage outside yocto

> On Jul 13, 2017, at 5:59 AM, Francesco Camarda (fcamarda) > wrote: > > Hello, > Starting from a yocto build (details below): > > $ bitbake ias-kc-pf-image > Loading cache: 100% > || > ETA: 00:00:0

Re: [yocto] [meta-intel] Installing a Yocto image to emmc

On Fri 2017-03-17 @ 11:19:30 PM, Duran, Randy G wrote: > Hello, I am trying to get information on software or procedure to flash > a Yocto image on to a Joule's emmc not using normal steps such using a > bootlable USB nor sdcard. I am attempting to automate flashing an image > on to device without

Re: [linux-yocto] [meta-intel] update kernel in local.conf

Hi, I accidentally ran into this too and looked into it a bit. There are two kernels in the package feedwhich Provides:the same functionality. The one that's built afterwards is tracked in pkgdata as runtime-reverse but the package manager has installed the other (returned by image_list_installe

Re: [yocto] [meta-intel][Galileo] Kernel configuration isn't applied on linux-yocto-rt

Hi, in order to isolate this issue I removed every layer with the exception of poky and compiled linux-yocto-rt for "qemux86" with success. (CONFIG_64BIT was set to n) Then I added the meta-intel layer and compiled the real time kernel for "intel-core2-32" also with success. (CONFIG_64BIT=n) How

[yocto] [meta-intel][Galileo] Kernel configuration isn't applied on linux-yocto-rt

Hi, I am currently trying to compile the linux-yocto-rt kernel for a custom board (called iot2000 here) based on the Intel Galileo platform. The build fails, because the kernel configuration isn't applied. However, the bitbake environment of the linux-yocto-rt target looks good to me and everyth

[yocto] [meta-intel]: Grub file not created after building the image with bitbake -k linux-yocto

Hi all, I'm new to Yocto build environment . I have been following the documentations to start building my own image with various customizations. So, my below question may seem very basic to you, for which I apologize in advance :). I am working on Intel Galileo Gen2 I cloned the Jethro layer in

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On Thu, 04 Feb 2016 07:31:32 shubham.kum...@wipro.com wrote: > >That entry is already there in "/conf/local.conf " file as follows:- >> > ># We default to enabling the debugging tweaks. > >EXTRA_IMAGE_FEATURES = "debug-tweaks" >> > >In addition to the above, I have also added "tools-sdk" and "tool

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On Thu, 04 Feb 2016 07:31:32 shubham.kum...@wipro.com wrote: > That entry is already there in "/conf/local.conf " file as follows:- > > # We default to enabling the debugging tweaks. > EXTRA_IMAGE_FEATURES = "debug-tweaks" > > In addition to the above, I have also added "tools-sdk" and "tools-deb

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On czw, 2016-02-04 at 07:31 +, shubham.kum...@wipro.com wrote: > Hi Khem, > > Thanks for your quick response. > > That entry is already there in "/conf/local.conf " file as follows:- > > # We default to enabling the debugging tweaks. > EXTRA_IMAGE_FEATURES = "debug-tweaks" > > In addition t

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

y 4, 2016 12:48 PM To: Shubham Kumar (Product Engineering Service) Cc: yocto@yoctoproject.org; maciej.borze...@open-rnd.pl Subject: Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt On Wed, Feb 3, 2016 at 10:43 PM, wrote: > Hi Maciej, > > > I did

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

6834:0:9:7::: > > Thanks for your co-operation, Maciej. Looking forward to reaolving this issue > asap. > > > Thanks, > Shubham_K > > > > > From: Maciej Borzecki > Sent: Wednesday, February 3, 2016 10:59 PM

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

r co-operation, Maciej. Looking forward to reaolving this issue asap. Thanks, Shubham_K From: Maciej Borzecki Sent: Wednesday, February 3, 2016 10:59 PM To: Shubham Kumar (Product Engineering Service); yocto@yoctoproject.org Subject: Re: [yocto] [meta-intel]:Quark not accep

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

> Dnia 3 luty 2016 o 15:55 shubham.kum...@wipro.com napisał(a): > > > In "final_build/conf/local.conf" , EXTRA_IMAGE_FEATURES = "debug-tweaks". > > So, yes "debug-tweaks" is present. > Try running bitbake -e and check the value of IMAGE_FEATURES (and where it gets assigned). You may also want to

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

r (Product Engineering Service); yocto@yoctoproject.org Subject: Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt On śro, 2016-02-03 at 14:00 +, shubham.kum...@wipro.com wrote: > > Hi all, > > I would additionally like to mention that the same p

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

On śro, 2016-02-03 at 14:00 +, shubham.kum...@wipro.com wrote: > > Hi all, > > I would additionally like to mention that the same problem persists when > trying to boot > the Galileo with core-image-sato.  > The steps which I followed are as follows:- > Inside the poky directory, > > 1.  so

Re: [yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi all, I would additionally like to mention that the same problem persists when trying to boot the Galileo with core-image-sato. The steps which I followed are as follows:- Inside the poky directory, 1. source oe-init-build-env final_build/ Now ,Inside the final_build/ directory 2. bit

[yocto] [meta-intel]:Quark not accepting "root" username at login prompt

Hi all, I built a core-image-minimal with additions of a few packages like tools-sdk and tools-debug. With WIK tool and the kickstart file "mkgalileodisk", I created the image. Then I dd'd the image to the SD card. The Galileo booted with the image, but it's not accepting "root" as the usernam

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

. Vincent > > > -Original Message- > From: Chris Tapp [mailto:opensou...@keylevel.com] > Sent: Wednesday, November 25, 2015 7:44 AM > To: Cheah, Vincent Beng Keat > Cc: Yocto Project ; Chang, Rebecca Swee Fun > ; Paul Eggleton > ; meta-in...@yoctoproject.org &g

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

ah, Vincent Beng Keat Cc: Yocto Project ; Chang, Rebecca Swee Fun ; Paul Eggleton ; meta-in...@yoctoproject.org Subject: Re: [yocto] [meta-intel] "Crazy" Xorg memory usage after upgrading from Daisy to Fido Hi Vincent, I may have made some progress. The undesirable memory usage with

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

Hi Vincent, I may have made some progress. The undesirable memory usage within Xorg isn’t there if I create an xorg.conf file containing: Section “Device” Identifier “Intel Video” Driver “intel” Option “TearFree” “true" EndSection So it looks as if I need to enable “TearFree”. I didn’t ne

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

Hi Vincent, I’ve finally got back to being able to investigate this further. I’ve now moved on to “jethro” and I’m seeing exactly the same behaviour. I’ve tried with kernel versions 3.14.39, 3.19.5 and 4.1.8. > On 10 Jun 2015, at 03:50, Cheah, Vincent Beng Keat > wrote: > > Hi Chris, > > I

[yocto] [meta-intel] MATOM set while using yocto-bsp create i386 (Celeron M targets / ThinkIO unit)

Hello all, Why 'yocto-bsp create ... i386' (Yocto dizzy 1.7.2) is defining a kernel config with the MATOM=y even if I select the default kernel with the '586' tune (neither the 'Atom' nor the 'core2')? is this expected? Im using and old Celeron M (petium M based) I'm also using the meta-intel la

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

Hi Vincent, > On 10 Jun 2015, at 03:50, Cheah, Vincent Beng Keat > wrote: > > Hi Chris, > > I don’t have any idea with regard to the issue that you are getting below. > All the work that we are doing here so far is on CHV (yocto-kernel-3.19.5 > standard/base branch). > > From your statement

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

Hi Chris, I don’t have any idea with regard to the issue that you are getting below. All the work that we are doing here so far is on CHV (yocto-kernel-3.19.5 standard/base branch). From your statement below, it looks to me that you are upgrading meta-intel from Daisy to Fido branch which are

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

Hi Vincent, Can you help to comment on this issue mentioned by Chris? Thanks. Regards, Rebecca > -Original Message- > From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] > Sent: 09 June, 2015 12:15 AM > To: Chang, Rebecca Swee Fun > Cc: meta-in...@yoctoproject.org; Chris Tapp; Yoc

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

Rebecca, is this something you or one of your colleagues would be able to help with? Thanks, Paul On Friday 05 June 2015 08:29:00 Chris Tapp wrote: > I’ve got an application that I’ve had running nicely under Daisy for some > time. As Daisy is now a bit old, I decided to move the application to

Re: [yocto] [meta-intel]

Hi Sau! Thanks for you quick reply. I'm building it with the intel-core2-32 machine and with the core2-64 tune this morning i'll let you know if there are issues (is it correct to use the mx32 instead the m64 in this case for the D2550? is there a noticeable increase of speed?) Im using my own d

Re: [yocto] [meta-intel]

On 04/08/2015 06:28 AM, J.J. Garcia wrote: Hi all I'm trying to use the meta-intel/DIZZY branch (MACHINE defined as intel-core2-32) for an Atom D2550 unit. AFAIK the 2550 supports the 64 bits so, which is the best way to build the image for the unit? Is it recommended to go for DEFAULTTUNE="co

[yocto] [meta-intel]

Hi all I'm trying to use the meta-intel/DIZZY branch (MACHINE defined as intel-core2-32) for an Atom D2550 unit. AFAIK the 2550 supports the 64 bits so, which is the best way to build the image for the unit? Is it recommended to go for DEFAULTTUNE="core2-64" in local.conf while using the intel-c

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

On Thursday 04 December 2014 09:16:42 Ong, Boon Leong wrote: > Hi Azril, > Thank you for your question. For meta-intel related > question, you should channel them to meta-intel M/L. > Since I catch it here, I have just added it on your behalf. Thanks > > BL > > From: yocto-boun..

Re: [yocto] [meta-intel] Why won't my app use multiple threads under 'valleyisland'?

On 29 Jul 2014, at 16:41, Darren Hart wrote: > On Thu, Jul 24, 2014 at 09:45:41PM +0100, Chris Tapp wrote: >> I've got a recipe for an application. This has: >> >> 1) A main thread; >> 2) An OpenGL ('X' / EGL) graphics rendering thread created using posix >> threads; >> 3) As many threads as r

Re: [yocto] [meta-intel] Why won't my app use multiple threads under 'valleyisland'?

On Thu, Jul 24, 2014 at 09:45:41PM +0100, Chris Tapp wrote: > I've got a recipe for an application. This has: > > 1) A main thread; > 2) An OpenGL ('X' / EGL) graphics rendering thread created using posix > threads; > 3) As many threads as required from the graphics thread for GStreamer to > ser

Re: [yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

On Fri, 2014-02-14 at 19:24 +0100, Koen Kooi wrote: > When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin > is being > dragged in as a valid provider. To avoid build breakage fix it at the > source by limiting emgd-driver-bin to x86 architectures. > > Signed-off-by: Koen

Re: [yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

On 2/14/2014 1:13 PM, Khem Raj wrote: -Khem On Feb 14, 2014 10:25 AM, "Koen Kooi" > wrote: > > When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin is being > dragged in as a valid provider. To avoid build breakage fix it at the > s

Re: [yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

-Khem On Feb 14, 2014 10:25 AM, "Koen Kooi" wrote: > > When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin is being > dragged in as a valid provider. To avoid build breakage fix it at the > source by limiting emgd-driver-bin to x86 architectures. > > Signed-off-by: Koen K

Re: [yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

On 2/14/2014 10:24 AM, Koen Kooi wrote: When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin is being dragged in as a valid provider. To avoid build breakage fix it at the source by limiting emgd-driver-bin to x86 architectures. Signed-off-by: Koen Kooi Acked-By: Ni

[yocto] [meta-intel][common][dora][PATCHv2] emgd-driver-bin: limit build to x86

When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin is being dragged in as a valid provider. To avoid build breakage fix it at the source by limiting emgd-driver-bin to x86 architectures. Signed-off-by: Koen Kooi --- common/recipes-graphics/xorg-driver/emgd-driver-bin_

Re: [yocto] [meta-intel] [common][dora][PATCH] emgd-driver-bin: limit build to x86*

> -Original Message- > From: meta-intel-boun...@yoctoproject.org [mailto:meta-intel- > boun...@yoctoproject.org] On Behalf Of Darren Hart > Sent: Friday, February 14, 2014 9:26 AM > To: Koen Kooi; meta-in...@lists.yoctoproject.org > Cc: yo...@lists.yoctoproject.org > Subject: Re: [meta-in

Re: [yocto] [meta-intel] [common][dora][PATCH] emgd-driver-bin: limit build to x86*

On 2/14/14, 7:21, "Koen Kooi" wrote: >When building GL apps for non-x86 machines (e.g. raspberrypi) >emgd-driver-bin is being >dragged in as a valid provider. To avoid build breakage fix it at the >source by limiting emgd-driver-bin to x86 architectures. > >Signed-off-by: Koen Kooi >--- > common

[yocto] [meta-intel][common][dora][PATCH] emgd-driver-bin: limit build to x86*

When building GL apps for non-x86 machines (e.g. raspberrypi) emgd-driver-bin is being dragged in as a valid provider. To avoid build breakage fix it at the source by limiting emgd-driver-bin to x86 architectures. Signed-off-by: Koen Kooi --- common/recipes-graphics/xorg-driver/emgd-driver-bin_

Re: [yocto] [meta-intel] Boot failure when using meta-intel and meta-ivi

On Thu, 2013-07-25 at 11:00 +0200, Felix01 Fischer wrote: > Hi, > I haven written regarding this issues before. So maybe it sounds > familiar :-) > > I'm unable to produce a booting image when combining a machine from > the meta-intel layer with "DISTRO ?= "poky-ivi-systemd" from the > meta-ivi l

Re: [yocto] [meta-intel][PATCH] intel-gpu-tools: add new package

On 25 June 2013 23:23, Tom Zanussi wrote: > On Tue, 2013-06-25 at 17:43 +0100, Ross Burton wrote: >> This package contains numerous useful tools for working with Intel GPUs. >> Add a >> patch to install intel_panel_fitter as it's genuinely useful and not just a >> debugging tool. >> >> Signed-of

Re: [yocto] [meta-intel][PATCH] lms8: handle different host setups

On Tue, 2013-06-25 at 17:45 +0100, Ross Burton wrote: > The configure script looks at the *host* environment to decide where to > install > the init script, so it's location at packaging time can change. > > Signed-off-by: Ross Burton Pulled into meta-intel/master. Thanks, Tom > --- > commo

Re: [yocto] [meta-intel][PATCH] meta-nuc: don't install lms8 as NUC doesn't support AMT

On Tue, 2013-06-25 at 17:47 +0100, Ross Burton wrote: > The NUC doesn't support Active Management Technology, so don't install lms8 as > part of the machine recommendations. > > Signed-off-by: Ross Burton Pulled into meta-intel/master. Thanks, Tom > --- > meta-nuc/conf/machine/nuc.conf |

Re: [yocto] [meta-intel][PATCH] intel-gpu-tools: add new package

On Tue, 2013-06-25 at 17:43 +0100, Ross Burton wrote: > This package contains numerous useful tools for working with Intel GPUs. Add > a > patch to install intel_panel_fitter as it's genuinely useful and not just a > debugging tool. > > Signed-off-by: Ross Burton Nice addition. Pulled into me

[yocto] [meta-intel][PATCH] meta-nuc: don't install lms8 as NUC doesn't support AMT

The NUC doesn't support Active Management Technology, so don't install lms8 as part of the machine recommendations. Signed-off-by: Ross Burton --- meta-nuc/conf/machine/nuc.conf |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-nuc/conf/machine/nuc.conf b/meta-nuc/conf/

[yocto] [meta-intel][PATCH] lms8: handle different host setups

The configure script looks at the *host* environment to decide where to install the init script, so it's location at packaging time can change. Signed-off-by: Ross Burton --- common/recipes-bsp/amt/lms8_8.0.0-7.bb |8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/comm

[yocto] [meta-intel][PATCH] intel-gpu-tools: add new package

This package contains numerous useful tools for working with Intel GPUs. Add a patch to install intel_panel_fitter as it's genuinely useful and not just a debugging tool. Signed-off-by: Ross Burton --- .../intel-gpu-tools/files/install-fitter.patch | 26 .../intel-gpu

Re: [yocto] [meta-intel] [PATCH] tiny-init: Drop the bbappend

Pulled into meta-intel/master. Thanks, Tom On Thu, 2013-05-16 at 12:15 -0700, Darren Hart wrote: > > On 05/15/2013 09:57 PM, Khem Raj wrote: > > init file which it was providing is ditto as meta-yocto > > so bbappend is redundant plus it gets rid of following warning > > for non poky distros. >

Re: [yocto] [meta-intel][PATCH] tiny-init: Drop the bbappend

On 05/15/2013 09:57 PM, Khem Raj wrote: > init file which it was providing is ditto as meta-yocto > so bbappend is redundant plus it gets rid of following warning > for non poky distros. > > WARNING: No recipes available for: > /builds1/meta-intel/meta-fri2/recipes-core/tiny-init/tiny-init.bba

[yocto] [meta-intel][PATCH] tiny-init: Drop the bbappend

init file which it was providing is ditto as meta-yocto so bbappend is redundant plus it gets rid of following warning for non poky distros. WARNING: No recipes available for: /builds1/meta-intel/meta-fri2/recipes-core/tiny-init/tiny-init.bbappend Signed-off-by: Khem Raj CC: Darren Hart ---

Re: [yocto] [meta-intel][PATCH 1/2] ffmpeg: Remove package as nobody depends on it anymore

On Thu, 2013-01-24 at 21:10 +0200, Andrei Gherzan wrote: > Ping > Pulled into meta-intel/master. Thanks, Tom > > On Sun, Jan 13, 2013 at 6:23 PM, Andrei Gherzan > wrote: > Signed-off-by: Andrei Gherzan > --- > common/recipes-multimedia/ffmpeg/ffmpeg.inc | 110

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On Thu, 2013-01-24 at 21:06 +0200, Andrei Gherzan wrote: > On Sun, Jan 13, 2013 at 11:06 PM, Andrei Gherzan > wrote: > On Sun, Jan 13, 2013 at 10:03 PM, Ross Burton > wrote: > > On Sunday, 13 January 2013 at 19:39, Andrei Gherzan > wrote: >

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On Thu, 2013-01-24 at 22:22 +, Burton, Ross wrote: > On 24 January 2013 19:06, Andrei Gherzan wrote: > > Ping. > > Your pings are misdirected - the meta-intel patches should now be > going to meta-in...@yoctoproject.org. > Oops, yeah, I somehow missed these, sorry - let me try them out and

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On 24 January 2013 19:06, Andrei Gherzan wrote: > Ping. Your pings are misdirected - the meta-intel patches should now be going to meta-in...@yoctoproject.org. Ross ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/y

Re: [yocto] [meta-intel][PATCH 1/2] ffmpeg: Remove package as nobody depends on it anymore

Ping On Sun, Jan 13, 2013 at 6:23 PM, Andrei Gherzan wrote: > Signed-off-by: Andrei Gherzan > --- > common/recipes-multimedia/ffmpeg/ffmpeg.inc | 110 > - > common/recipes-multimedia/ffmpeg/ffmpeg_0.7.12.bb | 44 - > 2 files changed, 154 deletions(-) > de

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On Sun, Jan 13, 2013 at 11:06 PM, Andrei Gherzan wrote: > On Sun, Jan 13, 2013 at 10:03 PM, Ross Burton wrote: > >> On Sunday, 13 January 2013 at 19:39, Andrei Gherzan wrote: >> > Tested with a new sato build on master. Everything seems to be OK. >> >> glxinfo/glxgears or something that actually

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On Sun, Jan 13, 2013 at 10:03 PM, Ross Burton wrote: > On Sunday, 13 January 2013 at 19:39, Andrei Gherzan wrote: > > Tested with a new sato build on master. Everything seems to be OK. > > glxinfo/glxgears or something that actually uses the hardware? > Yes. That too. ___

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On Sunday, 13 January 2013 at 19:39, Andrei Gherzan wrote: > Tested with a new sato build on master. Everything seems to be OK. glxinfo/glxgears or something that actually uses the hardware? Ross ___ yocto mailing list yocto@yoctoproject.org https://l

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

On Sun, Jan 13, 2013 at 6:44 PM, Ross Burton wrote: > Sorry for top posting... Have you verified that GL still works with this > major version bump? > > Ross > -- > Ross Burton > Sent with Sparrow > > On Sunday, 13 January 2013 at 16:23, Andrei Gherzan wrote:

Re: [yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

Sorry for top posting... Have you verified that GL still works with this major version bump? Ross-- Ross Burton Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Sunday, 13 January 2013 at 16:23, Andrei Gherzan wrote: > Signed-off-by: Andrei Gherzan > --- > meta-fri2/conf/machine/fr

[yocto] [meta-intel][PATCH 2/2] fri2.conf: mesa-dri was updated to 9.0.1

Signed-off-by: Andrei Gherzan --- meta-fri2/conf/machine/fri2.conf |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-fri2/conf/machine/fri2.conf b/meta-fri2/conf/machine/fri2.conf index 0efba2a..07ad750 100644 --- a/meta-fri2/conf/machine/fri2.conf +++ b/meta-fri2/conf/m

[yocto] [meta-intel][PATCH 1/2] ffmpeg: Remove package as nobody depends on it anymore

Signed-off-by: Andrei Gherzan --- common/recipes-multimedia/ffmpeg/ffmpeg.inc | 110 - common/recipes-multimedia/ffmpeg/ffmpeg_0.7.12.bb | 44 - 2 files changed, 154 deletions(-) delete mode 100644 common/recipes-multimedia/ffmpeg/ffmpeg.inc delete mode 1006

Re: [yocto] [meta-intel][PATCH] layer.conf: Use .= for adding to BBPATH and += to BBFILES

On 01/03/2013 07:50 PM, Khem Raj wrote: > Fixes parsing errors which is appearing after this commit to > meta-openembedded > > http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e > > This triggers > exception NameError: name 'base_contains' is not

Re: [yocto] [meta-intel][PATCH] linux-yocto: Add a patch to resolve undefined RUSAGE_SELF for perf.

>-Original Message- >From: Darren Hart [mailto:dvh...@linux.intel.com] >Sent: Monday, January 07, 2013 8:20 AM >To: Noor, Ahsan >Cc: yocto@yoctoproject.org; meta-in...@yoctoproject.org; Bodke, Kishore K >Subject: Re: [yocto] [meta-intel][PATCH] linux-yocto: Add

Re: [yocto] [meta-intel][PATCH] layer.conf: Use .= for adding to BBPATH and += to BBFILES

On Mon, 2013-01-07 at 08:08 -0800, Darren Hart wrote: > Hi Khem, > > On 01/03/2013 07:50 PM, Khem Raj wrote: > > Fixes parsing errors which is appearing after this commit to > > meta-openembedded > > > > http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd633

Re: [yocto] [meta-intel][PATCH] layer.conf: Use .= for adding to BBPATH and += to BBFILES

On 01/07/2013 09:10 AM, Khem Raj wrote: > On Mon, Jan 7, 2013 at 8:08 AM, Darren Hart wrote: >> Hi Khem, >> >> On 01/03/2013 07:50 PM, Khem Raj wrote: >>> Fixes parsing errors which is appearing after this commit to >>> meta-openembedded >>> >>> http://cgit.openembedded.org/meta-openembedded/com

Re: [yocto] [meta-intel][PATCH] layer.conf: Use .= for adding to BBPATH and += to BBFILES

On Mon, Jan 7, 2013 at 8:08 AM, Darren Hart wrote: > Hi Khem, > > On 01/03/2013 07:50 PM, Khem Raj wrote: >> Fixes parsing errors which is appearing after this commit to >> meta-openembedded >> >> http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e >>

Re: [yocto] [meta-intel][PATCH] linux-yocto: Add a patch to resolve undefined RUSAGE_SELF for perf.

On 12/31/2012 03:56 AM, Noor, Ahsan wrote: > From: Noor Ahsan Hi Noor, > > * Perf gived compilation error > CC builtin-sched.o > builtin-sched.c: In function ‘get_cpu_usage_nsec_parent’: > builtin-sched.c:399:16: error: storage size of ‘ru’ isn’t known > * Added a patch from linux kerne

Re: [yocto] [meta-intel][PATCH] layer.conf: Use .= for adding to BBPATH and += to BBFILES

Hi Khem, On 01/03/2013 07:50 PM, Khem Raj wrote: > Fixes parsing errors which is appearing after this commit to > meta-openembedded > > http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e > > This triggers > exception NameError: name 'base_contains'

[yocto] [meta-intel][PATCH] layer.conf: Use .= for adding to BBPATH and += to BBFILES

Fixes parsing errors which is appearing after this commit to meta-openembedded http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e This triggers exception NameError: name 'base_contains' is not defined without this change Signed-off-by: Khem Raj --

[yocto] [meta-intel][PATCH] linux-yocto: Add a patch to resolve undefined RUSAGE_SELF for perf.

From: Noor Ahsan * Perf gived compilation error CC builtin-sched.o builtin-sched.c: In function ‘get_cpu_usage_nsec_parent’: builtin-sched.c:399:16: error: storage size of ‘ru’ isn’t known * Added a patch from linux kernel git repo commit id 7b78f13603c6fcb64e020a0bbe31a651ea2b657b whic

Re: [yocto] [meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

On Wed, 2012-11-21 at 15:43 +0100, Koen Kooi wrote: > Signed-off-by: Koen Kooi Pulled into meta-intel/master and meta-intel/danny-next. Thanks, Tom > --- > meta-fri2/README |8 > 1 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/meta-fri2/README b/meta-fri2/READM

Re: [yocto] [meta-intel][danny][PATCH V2] mesa-dri_8.0.4.bbappend: Remove tabs from python code

On Wed, 2012-11-21 at 12:36 -0800, Khem Raj wrote: > check for xserver to be non-empty before using it > fixed errors like > > ERROR: Failed to parse recipe: > /b/kraj/yocto/poky/meta/recipes-graphics/mesa/mesa-dri_8.0.4.bb > ERROR: Error executing a python function in : > AttributeError: 'NoneTyp

[yocto] [meta-intel][danny][PATCH V2] mesa-dri_8.0.4.bbappend: Remove tabs from python code

check for xserver to be non-empty before using it fixed errors like ERROR: Failed to parse recipe: /b/kraj/yocto/poky/meta/recipes-graphics/mesa/mesa-dri_8.0.4.bb ERROR: Error executing a python function in : AttributeError: 'NoneType' object has no attribute 'split' Signed-off-by: Khem Raj ---

[yocto] [meta-intel][danny][PATCH] mesa-dri_8.0.4.bbappend: Remove tabs from python code

Signed-off-by: Khem Raj --- .../recipes-graphics/mesa/mesa-dri_8.0.4.bbappend |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/common/recipes-graphics/mesa/mesa-dri_8.0.4.bbappend b/common/recipes-graphics/mesa/mesa-dri_8.0.4.bbappend index 6bfa968..2a49c26 100644 --

Re: [yocto] [meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

On 11/21/2012 06:43 AM, Koen Kooi wrote: Nice catch Koen, thank you. > Signed-off-by: Koen Kooi > --- > meta-fri2/README |8 > 1 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/meta-fri2/README b/meta-fri2/README > index af33c0b..b90613d 100644 > --- a/meta-fri2/RE

[yocto] [meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

Signed-off-by: Koen Kooi --- meta-fri2/README |8 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/meta-fri2/README b/meta-fri2/README index af33c0b..b90613d 100644 --- a/meta-fri2/README +++ b/meta-fri2/README @@ -93,7 +93,7 @@ bblayers.conf, e.g.: The meta-fri2 layer

  1   2   >