[meta-freescale] [meta-freescale-layer][PATCH v2] remove qemu-usermode from MACHINE_FEATURES for e6500 targets

Currently qemu doesn't support ppce6500, accordingly gobject-introspection oesn't build for e6500 when introspection-data is enabled. Remove qemu-usermode from MACHINE_FEATURES to disable introspection-data for gobject-introspection build. The e6500 support issue of qemu is tracked by:

[meta-freescale] [Documentation][PATCH] Update to Krogoth

From: Thomas Thorne Replace 'Jethro' with 'Krogoth' and '2.0' with '2.1' Signed-off-by: Thomas Thorne --- FAQ/source/conf.py | 6 +++--- release-notes/source/conf.py | 2 +- user-guide/source/conf.py| 6 +++---

Re: [meta-freescale] [meta-freescale PATCH 3/3] qoriq-base.inc: Use 'fsl-dynamic-packagearch' class

Thanks, I can reproduce the issue and understand the solution now. Best Regards, Zhenhua > -Original Message- > From: Otavio Salvador [mailto:otavio.salva...@ossystems.com.br] > Sent: Wednesday, September 21, 2016 5:57 PM > To: Zhenhua Luo > Cc: Otavio Salvador

[meta-freescale] [meta-fsl-arm] Please do something about broken chromium .bbappend

It's been broken for weeks :-( ERROR: No recipes available for: /local/poky-cutting-edge/meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium_48.0.2548.0.bbappend If you can't update the .bbappend, at least delete it until you can. --

Re: [meta-freescale] [meta-fsl-arm] Please do something about broken chromium .bbappend

On 2016-09-22 11:51, Otavio Salvador wrote: On Thu, Sep 22, 2016 at 4:41 AM, Gary Thomas wrote: It's been broken for weeks :-( ERROR: No recipes available for: /local/poky-cutting-edge/meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium_48.0.2548.0.bbappend If

[meta-freescale] [meta-freescale-layer][PATCH] remove gobject-introspection-data feature which is not needed

Currently qemu doesn't support ppce6500, accordingly gobject-introspection oesn't build for e6500 targets. Since the gobject-introspection-data feature is not needed for e6500, remove it from default build list. The e6500 support issue of qemu is tracked by:

Re: [meta-freescale] [meta-fsl-arm] Please do something about broken chromium .bbappend

On Thu, Sep 22, 2016 at 4:41 AM, Gary Thomas wrote: > It's been broken for weeks :-( > > ERROR: No recipes available for: > > /local/poky-cutting-edge/meta-fsl-arm/browser-layer/recipes-browser/chromium/chromium_48.0.2548.0.bbappend > > If you can't update the .bbappend, at

Re: [meta-freescale] [meta-fsl-arm] Please do something about broken chromium .bbappend

On Thu, Sep 22, 2016 at 6:56 AM, Gary Thomas wrote: > On 2016-09-22 11:51, Otavio Salvador wrote: >> >> On Thu, Sep 22, 2016 at 4:41 AM, Gary Thomas wrote: >>> >>> It's been broken for weeks :-( >>> >>> ERROR: No recipes available for: >>> >>> >>>

Re: [meta-freescale] fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot

On Thu, Sep 22, 2016 at 9:30 AM, Shrikant Bobade wrote: > I am also facing similar DRM lock error issue. Please try to reproduce the issue removing the 'wayland' distro feature. So it is going to use pure X11. -- Otavio Salvador O.S.

Re: [meta-freescale] fsl-community-bsp (master): fsl-image throws error: "drm_lock_take] *ERROR* 1 holds heavyweight lock" during reboot

Hi, I am also facing similar DRM lock error issue. @Ping Please advise updates if any. Thanks Shrikant Hello Prabhu, > > On Fri, Aug 26, 2016 at 12:30 PM, srikanth krishnakar > wrote: > > I have been building fsl-image-multimedia master branch of > fsl-community-bsp >

Re: [meta-freescale] [meta-freescale-layer][PATCH] remove gobject-introspection-data feature which is not needed

On Thu, Sep 22, 2016 at 7:18 AM, Burton, Ross wrote: > > On 22 September 2016 at 09:40, Zhenhua Luo wrote: >> >> Currently qemu doesn't support ppce6500, accordingly gobject-introspection >> oesn't build for e6500 targets. Since the

[meta-freescale] [Documentation][PATCH] Include rootfs.tar.gz Method In Build and boot steps

From: Thomas Thorne Many Yocto build systems, including the one for the ls1021a-twr do not generate .sdcard bianry images. This changeset adds some instructions on inflaiting a tar'ed and gzip'ed root filesystem image onto an SD card and then copying over the kernel