[Buildroot] [V4 1/2] A20-OLinuXino-Lime: new board (mainline)

François Perrad francois.perrad at gadz.org
Sat Jun 27 06:58:24 UTC 2015


2015-06-26 18:27 GMT+02:00 Luca Ceresoli <luca at lucaceresoli.net>:
> Dear Francois,
>
> Francois Perrad wrote:
>>
>> config device tree / mainline (4.0.5)
>>
>> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout at mind.be>
>> Signed-off-by: Francois Perrad <francois.perrad at gadz.org>
>> ---
>>   board/olimex/a20_olinuxino_lime/boot.cmd      |  5 ++
>>   board/olimex/a20_olinuxino_lime/post-build.sh |  8 +++
>>   board/olimex/a20_olinuxino_lime/readme.txt    | 86
>> +++++++++++++++++++++++++++
>
>
> I confirm these files work for the A20-OLinuXino-Micro too, so I'd move
> them to board/olimex/a20_olinuxino/ (without the _lime suffix).
>
> I'll build support for the Micro on top of them.
>
> [...]
>>
>> diff --git a/board/olimex/a20_olinuxino_lime/boot.cmd
>> b/board/olimex/a20_olinuxino_lime/boot.cmd
>> new file mode 100644
>> index 0000000..44d9239
>> --- /dev/null
>> +++ b/board/olimex/a20_olinuxino_lime/boot.cmd
>> @@ -0,0 +1,5 @@
>> +setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait
>> panic=10 ${extra}
>> +ext4load mmc 0 0x49000000 /boot/${fdtfile}
>
>
> Using ${fdtfile} here is a good idea, it simplified my job. Thanks!
>
> [...]
>>
>> diff --git a/board/olimex/a20_olinuxino_lime/readme.txt
>> b/board/olimex/a20_olinuxino_lime/readme.txt
>> new file mode 100644
>> index 0000000..3fc9c02
>> --- /dev/null
>> +++ b/board/olimex/a20_olinuxino_lime/readme.txt
>> @@ -0,0 +1,86 @@
>> +A20-OLinuXino-LIME
>> +
>> +Intro
>> +=====
>> +
>> +This is a open hardware board,
>> +see https://www.olimex.com/Products/OLinuXino/open-source-hardware
>
>
> I still think a link to the board webpage would be informative...
>
> [...]
>>
>> diff --git a/configs/olimex_a20_olinuxino_lime_defconfig
>> b/configs/olimex_a20_olinuxino_lime_defconfig
>> new file mode 100644
>> index 0000000..62f0a4c
>> --- /dev/null
>> +++ b/configs/olimex_a20_olinuxino_lime_defconfig
>> @@ -0,0 +1,45 @@
>> +# Architecture
>> +BR2_arm=y
>> +BR2_cortex_a7=y
>> +BR2_ARM_EABIHF=y
>
>
> This SoC has NEON and VFPv4, so you should add:
> BR2_ARM_FPU_NEON_VFPV4=y
>

Dear Luca,

>From the reading of arch/Config.in.arm:
- BR2_cortex_a7 selects BR2_ARM_CPU_HAS_NEON and BR2_ARM_CPU_HAS_VFPV4
- BR2_CPU_HAS_VFPV4 choices by default BR2_ARM_FPU_VFPV4D16 as
"Floating point strategy"

BR2_ARM_FPU_NEON_VFPV4 could be another choice for this "Floating
point strategy".

As far I see, the BR defconfigs try to stay minimalist.
For me, the default settings provided by BR are good enough.

I added BR2_ARM_EABIHF because it is required by the proprietary blob
binary mali r3p0, not because it is a nice to have or a fine tuning
optimisation.

François


> I booted a Micro board with a defconfig that is very similar to yours.
> But I couldn't borrow a Lime yet, do I just build-tested it.
>
> --
> Luca
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot



More information about the buildroot mailing list