Hello, I pushed following updates:
commit b5847aaf9f2bc62cb6af3e85ac462f6ca00fdeac (HEAD -> pending, m/master, github/master) Author: Otavio Salvador <[email protected]> Date: Thu Oct 15 15:18:28 2015 -0300 u-boot-fslc: Update to 982a6474 revision Update the U-Boot fork to a 2015.10-rc5 based version. This brings several fixes for i.MX and Vybrid based systems. Mainly: cf04ad3 arm: vf610twr: improve memory layout d45fd01 colibri_vf: Fix bstlen field e24bb2b mtd: nand: vf610_nfc: resync with upstream Linux version f861f51 ls102xa: Fix reset hang f532727 imx_watchdog: Add a header file for watchdog registers 040ef8f pcm052: fix MTD partitioning 61903b7 imximage: fix commands other than write_data 835c30e imximage: header.length of 4 is valid Change-Id: Ifdb607d9a94ef594f3fe37d2b6388dc9a8268106 Signed-off-by: Otavio Salvador <[email protected]> commit d119786e71ea9afd99b8dcdc34fc3e946086a76a Author: Otavio Salvador <[email protected]> Date: Wed Oct 14 15:26:53 2015 -0300 image_types_fsl.bbclass: Fail if a Device Tree file is missing When generating the rootfs we need to include all the referenced Device Tree files. The code were gracefully checking if the file existed before building the image however the expected behavior is to fail. As consequence of this change, if someone is using a very old kernel (no Device Tree based) and tries to generate an image, it will fail until the machine definition is changed to not list Device Tree files for installation. Currently all machines supported by meta-fsl-arm BSP are consistent for the default kernel in use however custom BSP may need to be changed accordingly. Change-Id: I548c65c61dfefe24154a455d097032b1598b14d3 Signed-off-by: Otavio Salvador <[email protected]> commit b42f96e6c612bf979a97b1b13014bc140790a2d9 Author: Otavio Salvador <[email protected]> Date: Thu Oct 15 15:03:31 2015 -0300 image_types_fsl.bbclass: Refactor boot image duplicated code The code which copies the boot scripts and Device Tree files is duplicated across the different image types. This patch reworks this code to avoid this duplication. Change-Id: Ib9405067a5419e1b295dfac9e3d3bd9b896d424e Signed-off-by: Otavio Salvador <[email protected]> commit d3021ffd2753fce46dfff2b12e10fdaf2931ee62 Author: Stefan Agner <[email protected]> Date: Wed Oct 14 22:28:52 2015 -0700 linux-fslc (4.1): Add Vybrid SoC to compatible machines Upstream Linux 4.1 supports the Vybrid SoC quite well, so enable linux-fslc also for Vybrid SoC's. Change-Id: I6745b67f4cc4b12ccc6f05754af9241e60731c6a Signed-off-by: Stefan Agner <[email protected]> Signed-off-by: Otavio Salvador <[email protected]> commit f33741f4cef5112f4b868188170d2f9799dcaeb3 Author: Otavio Salvador <[email protected]> Date: Wed Oct 14 14:33:07 2015 -0300 imx-base.inc: Set a default provider for u-boot-mxsboot-native The O.S. Systems Embedded Linux provides an alternative version of U-Boot and, for completeness, an alternative recipe for u-boot-mxsboot-native. The provider, in imx-base.inc, had no default thus raising a warning. This turns the u-boot-fslc-mxsboot-native as the default provider but allows custom distributions to override it. Change-Id: I46799f9ec744a074d95c383561cf0cbddb26e151 Signed-off-by: Otavio Salvador <[email protected]> commit 409b3d934986a89ed35d6a237c0c6e0b5ba16422 Author: Otavio Salvador <[email protected]> Date: Wed Oct 14 11:36:04 2015 -0300 opencv: Use the 2.4 release only The opencv 3.0 is not tested and does not have the i.MX6 specific patch ported so we disable it for the i.MX6 SoC from Quad, DualLite, SoloX and SoloLite families. The 2.4 is used instead. This fixes following warning: ,---- | NOTE: multiple providers are available for runtime opencv-samples (opencv-samples, opencv) | NOTE: consider defining a PREFERRED_PROVIDER entry to match opencv-samples `---- Change-Id: I2f897cdd31dcee9046ee7d28ef4dcadb154ae88c Signed-off-by: Otavio Salvador <[email protected]> commit 6338606d4fffd756667356ee4bca44a7b07bf726 Author: Otavio Salvador <[email protected]> Date: Wed Oct 14 11:26:01 2015 -0300 mesa-gl: Blacklist the recipe for i.MX6 SoCs with GPU The mesa-gl is not in sure for the i.MX6 SoC from Quad, DualLite, SoloX and SoloLite families. The full featured, but trimmed, mesa is used instead. This fixes following warning: ,---- | NOTE: multiple providers are available for runtime libgl-mesa-dev (mesa, mesa-gl) | NOTE: consider defining a PREFERRED_PROVIDER entry to match libgl-mesa-dev | NOTE: multiple providers are available for runtime mesa-driver-swrast (mesa, mesa-gl) | NOTE: consider defining a PREFERRED_PROVIDER entry to match mesa-driver-swrast `---- Change-Id: I082b8f7a739e4ea3cfe5f1760c7163d118e9883c Signed-off-by: Otavio Salvador <[email protected]> commit 6527bbaddcc99068596cd196eb8efe42b948abec Author: Zhenhua Luo <[email protected]> Date: Fri Oct 16 13:43:15 2015 +0800 linux-qoriq: fix gcc 5.2 build issues of ls1021atwr Cherry picked patches from future kernel versions to fix gcc5.2 build errors (Port from meta-fsl-arm rev: d4da62e1972d78a0ebfa51e6bad232732144e4b2) Signed-off-by: Chunrong Guo <[email protected]> Signed-off-by: Zhenhua Luo <[email protected]> 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 -- _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
