[meta-freescale] [CRITICAL] Boards failing to build with GCC 5.2 - Kernel patches are needed

[Tony Felice]

I will update the Phytec/Quartz board support.

On Fri, Oct 23, 2015 at 2:41 PM, Ian Coolidge <ian at boundarydevices.com>
wrote:

> I'll handle updating Boundary Device's boards. Thanks.
>
> On Fri, Oct 23, 2015 at 10:54 AM, Otavio Salvador <
> otavio.salvador at ossystems.com.br> wrote:
>
>> Hello folks,
>>
>> I have been working at stabilizing the core BSP boards (Freescale
>> reference boards) for Yocto Project 2.0 release - jethro. As most of
>> you are aware one of the changes for this release is the GCC version
>> update.
>>
>> The vendors needing to check the boards are:
>>
>> Boundary Devices
>> CompuLab
>> Congatec
>> Crystalfontz
>> DENX
>> Device Solutions
>> Phytec
>> SolidRun
>> Wandboard.org
>>
>> These vendors are responsible for one, or more, of the following boards:
>>
>> imx6qsabrelite (Boundary Devices i.MX6Q SABRE Lite)
>> nitrogen6sx (Boundary Devices Nitrogen6SX)
>> nitrogen6x (Boundary Devices Nitrogen6X)
>> nitrogen6x-lite (Boundary Devices Nitrogen6X Lite)
>> cm-fx6 (CompuLab CM-FX6)
>> cgtqmx6 (Congatec Qmx6)
>> cfa10036 (Crystalfontz CFA-10036)
>> cfa10037 (Crystalfontz CFA-10037)
>> cfa10049 (Crystalfontz CFA-10049)
>> cfa10055 (Crystalfontz CFA-10055)
>> cfa10056 (Crystalfontz CFA-10056)
>> cfa10057 (Crystalfontz CFA-10057)
>> cfa10058 (Crystalfontz CFA-10058)
>> quartz (Device Solutions Quartz Vybrid Development Kit)
>> ventana (i.MX6Q/DL Ventana Platform)
>> pcl052 (Phytec Cosmic Vybrid Development Kit)
>> pcm052 (Phytec phyCORE Vybrid Development Kit)
>> cubox-i (SolidRun CuBox-i and HummingBoard)
>> wandboard (Wandboard i.MX6 Wandboard Quad/Dual/Solo)
>> m28evk (DENX M28 SoM Evaluation Kit)
>> m53evk (DENX M53 SoM Evaluation Kit)
>>
>> For i.MX6 based boards, the linux-fslc-mx6 kernel has the patches
>> applied as it is updated with the Linux 3.14 stable releases.
>> Following patches are worth checking:
>>
>>  - allow the Vivante GPU kernel module to work:
>>
>> https://github.com/Freescale/linux-fslc/commit/22f692548037e39809c32759b5600ee066ef59e9.patch
>>
>>  - GCC 5.2 fixes :
>>
>> https://github.com/Freescale/linux-fslc/commit/aeea3592a13bf12861943e44fc48f1f270941f8d.patch
>>
>> https://github.com/Freescale/linux-fslc/commit/76ae03828756bac2c1fa2c7eff7485e5f815dbdb.patch
>>
>> For other SoCs the linux-fslc 4.1 branch seems to be a good option to
>> avoid the local recipe and this maintenance burden.
>>
>> WARNING: I will REMOVE boards which are kept broken so please respond
>> to this email with a plan for fixing it.
>>
>> Best 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
>>
>
>


-- 
Tony Felice
Vybrid Technical Lead
Timesys Corporation
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20151023/20862801/attachment.html>