Re: [linux-yocto] [PATCH] meta-yocto-bsp: bump to linux-yocto 4.1 for the non-x86 BSPs

On 29 September 2015 at 10:42, Kevin Hao wrote: > Boot test for all these boards. > If I build the edgerouter kernel I get this warning: WARNING: Section not found: .comment I've no idea if this is bad or not... Ross --

[linux-yocto] [PATCH] meta-yocto-bsp: bump to linux-yocto 4.1 for the non-x86 BSPs

Boot test for all these boards. Signed-off-by: Kevin Hao --- meta-yocto-bsp/conf/machine/beaglebone.conf | 2 +- meta-yocto-bsp/conf/machine/edgerouter.conf | 2 +- meta-yocto-bsp/conf/machine/mpc8315e-rdb.conf| 2 +-

Re: [yocto] [opkg-devel] [PATCH] opkg-utils: Fix crash on dependency error

> On Sep 29, 2015, at 9:10 AM, Alejandro del Castillo > wrote: > > On 05/21/2015 06:27 PM, Haris Okanovic wrote: >> Fix crash on exception in opkg-show-deps when generating an >> 'unsatisfied dependency' error. process_dep() function was >> referencing a missing

[yocto] PSPLASH PPC Colors

All, Has anyone else noticed that the splash screen colors are wrong on PPC? I installed a custom splash screen with modified colors. It looks fine on qemuarm but on qemuppc the splash screen color are all wrong. Whites and blacks are all yellow, blues are red etc. Is there an endianness

Re: [yocto] PSPLASH PPC Colors

On 2015-09-29 14:26, Smith, Daniel W wrote: All, Has anyone else noticed that the splash screen colors are wrong on PPC? I installed a custom splash screen with modified colors. It looks fine on qemuarm but on qemuppc the splash screen color are all wrong. Whites and blacks are all

Re: [yocto] PSPLASH PPC Colors

> Does this happen on qemuppc or only on real hardware? I have only tried it on qemuppc & qemuarm at this point. The colors are all correct once busybox is running, so I suspect it is an edianness issue with images generated on a PC and then installed on a PPC. -Daniel Smith This

Re: [yocto] PSPLASH PPC Colors

This is a known bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7236 Juro > -Original Message- > From: yocto-boun...@yoctoproject.org [mailto:yocto- > boun...@yoctoproject.org] On Behalf Of Smith, Daniel W > Sent: Tuesday, September 29, 2015 1:57 PM > To: Gary Thomas;

Re: [linux-yocto] [poky] [PATCH] meta-yocto-bsp: bump to linux-yocto 4.1 for the non-x86 BSPs

On Tue, Sep 29, 2015 at 10:18:00AM -0700, Khem Raj wrote: > > On Sep 29, 2015, at 3:01 AM, Burton, Ross wrote: > > > On 29 September 2015 at 10:42, Kevin Hao wrote: > > Boot test for all these boards. > > > If I build the

[linux-yocto] [PATCH 0/3] i915 graphics driver bug fixes for Braswell

Hi, This patches are bug fixes patch backported from upstream mainline kernel. We encountered GPU hang issue during MediaSDK encoding. The patches will remove redundant gen8_ppgtt_unmap_pages and set up a page table making all pt entries pointing to the scratch page before mapping to avoid out

[linux-yocto] [PATCH 3/3] drm/i915/gen8: Initialize page tables

From: Michel Thierry Similar to gen6, while setting up a page table, make all entries of the pt point to the scratch page before mapping; this is to be safe in case of out of bound access or proactive prefetch. Systems without LLC require an explicit flush. v2:

[linux-yocto] [PATCH 2/3] drm/i915: Remove unnecessary gen8_ppgtt_unmap_pages

From: Michel Thierry We are already unmapping them in gen8_ppgtt_free. This function became redundant since commit 06fda602dbca9c59d87db7da71192e4b54c9f5ff ("drm/i915: Create page table allocators"). Cc: Mika Kuoppala Signed-off-by:

[yocto] How to create and install a library in yocto -- Hello Library

Hello to all, I have searching for a way to include a library-only in yocto. I found couple links with suggestions but I was unsuccessful in the to package it in the final image. Reading the yocto documentation, I see a paragraph mentioning about static libraries but there is no examples.

[yocto] Release Candidate Build for yocto-1.8.1.rc1.rc1 now available.

-e A release candidate build for yocto-1.8.1.rc1 is now available at: http://autobuilder.yoctoproject.org/pub/releases/yocto-1.8.1.rc1 Please begin QA on this build as soon as possible. Build hash information: meta-intel : ead0a5c115e632015d8358f4f304ec8908732f5f meta-fsl-arm :

Re: [yocto] Packages in packagegroup are not installed in image

Randy, It works perfectly now. :) Thanks so much for your advice. Warm regards, Mei Yeen -Original Message- From: Randy Witt [mailto:randy.e.w...@linux.intel.com] Sent: Wednesday, August 26, 2015 4:05 AM To: Ng, Mei Yeen; yocto@yoctoproject.org Cc: Hart, Darren; Witt, Randy E

Re: [yocto] yocto Digest, Vol 60, Issue 78

On 2015-09-29 03:38, Stuart Weaver wrote: Many thanks for your answers Gary/Daniel, Gary- I've tried: SRC_URI_append_image-name2 = "file://XYZ.patch" But no luck, when building the image it seems to skip over it with no patching occurring. I can't use the ${MACHINE}

Re: [yocto] yocto Digest, Vol 60, Issue 78

> On Sep 29, 2015, at 2:38 AM, Stuart Weaver > wrote: > > Many thanks for your answers Gary/Daniel, > > Gary- I've tried: >SRC_URI_append_image-name2 = "file://XYZ.patch” the override you are deploying is wrong so this assignment in effect is

[yocto] Documentation and Scope

Hi everyone- I've been reading the reference manual, and have noticed that none of the defines have their scope mentioned anywhere. For variables such as PREFERRED_VERSION, this means that it is impossible to tell if this could be used from within a recipe vs only being able to be used in the