[meta-freescale] Updates to meta-fsl-arm (master) in 2014-09-05

[Otavio Salvador]

Hello,

I pushed following updates:

commit d1763d3ae70a8c7d123ae5caa4fb8c0533fb5438 (HEAD, yocto/master, pending)
Author: Otavio Salvador <otavio at ossystems.com.br>
Date:   Thu Sep 4 21:05:06 2014 -0300

    gpu-viv-bin-mx6q: Fix libOpenVG link when building for mx6sl
    
    The ab83159 (gpu-viv-bin-mx6q: Include sololite changes to remove 3Dx
    libraries.) reworked the libraries available for mx6sl case however
    the symbolic link was wrong. It points to the work instalation directory.
    
    This resulted in:
    
    ,----
    | ibOpenVG_355.so
    | ibOpenVG.so -> .../tmp/work/.../image/usr/lib/libOpenVG_355.so
    `----
    
    While the expected is:
    
    ,----
    | libOpenVG_355.so
    | libOpenVG.so -> libOpenVG_355.so
    `----
    
    This patch fixes is to use a relative link, fixing OpenVG based
    application builds from a clean tmp directory or using rm_work class.
    
    Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>

commit 3d5151a453cd08f356b2161c37303e07c6b1798d
Author: Otavio Salvador <otavio at ossystems.com.br>
Date:   Thu Sep 4 20:30:16 2014 -0300

    imx-base.inc: Add virtual/libopenvg to MACHINE_{ARCH,SOCARCH}_FILTER
    
    The virtual/libopenvg is provided by the GPU packages and needs to be
    used for the dynamic package architecture.
    
    The issue has been identified while debugging a build failure in
    fsl-gpu-sdk. It was using the common architecture instead of the right
    architecture.
    
    Now mx6q, mx6dl and mx6sx use MACHINE_SOCARCH and mx6sl MACHINE_ARCH
    for all packages depending on virtual/libopenvg.
    
    Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>

commit 6169078f3c1d36bed3a4ce60fd8c1d2d1d7b7020
Author: Christopher Larson <chris_larson at mentor.com>
Date:   Wed Sep 3 10:49:40 2014 -0700

    imx-{lib,vpu}: obey CFLAGS, LDFLAGS
    
    This quiets GNU_HASH warnings when building with an external toolchain.
    
    Signed-off-by: Christopher Larson <chris_larson at mentor.com>
    Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>

commit 7b734e2094bc594e9a17e7dfdae6a9564fb7819a
Author: Carlos Rafael Giani <dv at pseudoterminal.org>
Date:   Thu Sep 4 19:49:00 2014 +0200

    chromium: Update bbappend to version 37.0.2062.94
    
    Also update chromium-imx revision to support newer v5 Vivante drivers
    (used in 3.10.31 Beta release). These do not use "GL_VIV_direct_texture"
    as the name for the Vivante texture extension, but "GL_VIV_tex_direct"
    instead. v4 drivers (3.10.17 GA release and older) are still supported.
    
    Signed-off-by: Carlos Rafael Giani <dv at pseudoterminal.org>
    Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>

commit 19f9ecc3e624caad58a788be8c150f2c871823ef (code/master-next)
Author: Otavio Salvador <otavio at ossystems.com.br>
Date:   Tue Sep 2 15:54:45 2014 -0300

    linux-mfgtool.inc: Fix dynamic packages handling
    
    In case we have kernel modules, a runtime dependency or recommendation
    can break the dependency resolution algorithm of BitBake resulting on
    a conflict like:
    
    ,----[ Provider conflict error ]
    | ERROR: Trying to resolve runtime dependency kernel-module-nfs resulted
    |     in conflicting PREFERRED_PROVIDER entries being found.
    | The providers found were:
    |     ['.../meta-customer/recipes-kernel/linux/linux-customer-mfgtool_3.10.17.bb',
    |      '.../meta-customer/recipes-kernel/linux/linux-customer_3.10.17.bb']
    | The PREFERRED_PROVIDER entries resulting in this conflict were:
    |     ['PREFERRED_PROVIDER_linux-mfgtool = mfgtool-linux-customer',
    |      'PREFERRED_PROVIDER_virtual/kernel = linux-customer']
    `----
    
    To fix this, we need to rename the dynamic packages and hence change
    the built binaries, solving the conflict.
    
    Change-Id: I8becb8a4a839494720711f60f51515aba0140c68
    Signed-off-by: Otavio Salvador <otavio at ossystems.com.br>

Regards,

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750