[Buildroot] [PATCH V2 1/1] Arcturus uCLS1012A-SOM support

Oleksandr G Zhadan oleks at arcturusnetworks.com
Thu Jun 8 19:53:01 UTC 2017


Hello,
Please see in-line:
On 06/08/2017 03:21 PM, Thomas Petazzoni wrote:
> Hello,
>
> On Thu, 8 Jun 2017 12:14:13 -0400, Oleksandr G Zhadan wrote:
>
>> Looks like I can correct all things you pointed to, except last one:
>> My personal preferences as well is to build toolchains from the sources
>> and we already tried to do it , but, from our experience, in situation
>> with aarch64 ls1012a support to generate "correct code" we MUST use
>> EXTERNAL toolchain from Linaro
> What is the problem that you encounter with the Buildroot generated
> toolchain? It should definitely work, and if it doesn't, we have a
> serious problem.
>
> At least, we know it builds a toolchain capable of building a kernel +
> userspace that boots under Qemu.
We have tried couple different versions of gcc as well as different 
libraries on two different modules, one was NXP FRDM-1012A and one was 
ours uCLS1012A-SOM.
Yes, it builds everything OK, but when we run, then on some applications 
we got SIGSEGV.
I didn't remember exactly on which one and is this was on our local 
build system or on buildroot, but we have been testing/investgating for 
a while (at least 3-4 monts) and finaly make a decision to stay with 
Linaro's toolchain on ours and buildroot's  build systems, at least for now.
I couldn't tell you about other Layerscape CPUs, but we do had that 
issue with regular GNU toolchain on modules with  ls1012a CPU.

>
>> (and BTW this one is the first/default  choice for aarch64).
> No: the default for AArch64 is an internal Buildroot toolchain.
Sorry, I meant that Linaro is the default choice for EXTERNAL toolchain.
>
>> And one question:
>> When I will change the commit title should I send it as a new commit or
>> as v3 of my previous patches ?
> A v3 of your previous patches.
OK.
>
> Thanks!
>
> Thomas
Thanks,
Oleks


-- 
Oleksandr Zhadan
Sr. Software Engineer
Arcturus Networks
T 416 621-0125 x235
F 416 621-0190




More information about the buildroot mailing list