Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] [V4 1/2] A20-OLinuXino-Lime: new board (mainline)
Date: Sun, 28 Jun 2015 21:54:25 +0200	[thread overview]
Message-ID: <559050F1.1030101@lucaceresoli.net> (raw)
In-Reply-To: <CAB0FRstYj+N0T20YcFmUv+U5_HB1S1HuGtmoh-=jrzxu2HNCjQ@mail.gmail.com>

Dear Fran?ois,

thanks for your patches, which are now on master. I'll base my
A20-OLinuXino-MICRO patches on top of you good work.

A comment below about minimal defconfigs.

Fran?ois Perrad wrote:
[...]
>>> 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.

I understand your argument.

However, my understanding of the "minimal defconfig" choice is only
that they should not include unneeded packages (i.e. everything but
busybox) in the root filesystem.

I don't see any advantage of configuring toolchain and target options in
a sub-optimal way.

In fact, we have several Cortex-A defconfigs that enable NEON (5 out of
26) and EABIHF (9 out of 26):

$ git grep -l  cortex_a -- configs/ |wc
      26      26     878
$ git grep -l  cortex_a -- configs/ | xargs grep -l EABIHF|wc
       9       9     308
$ git grep -l  cortex_a -- configs/ | xargs grep -l NEON|wc
       5       5     158
$

But as I said, my understanding might be wrong.

Any authoritative opinions on this?
I'd be glad to update the docs with whatever is "official".

-- 
Luca

  reply	other threads:[~2015-06-28 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 10:06 [Buildroot] [V4 0/2] A20-OLinuXino-Lime: new board Francois Perrad
2015-06-26 10:06 ` [Buildroot] [V4 1/2] A20-OLinuXino-Lime: new board (mainline) Francois Perrad
2015-06-26 16:27   ` Luca Ceresoli
2015-06-27  6:58     ` François Perrad
2015-06-28 19:54       ` Luca Ceresoli [this message]
2015-06-28 20:24         ` Thomas Petazzoni
2015-07-07 20:32           ` Arnout Vandecappelle
2015-06-26 10:06 ` [Buildroot] [V4 2/2] A20-OLinuXino-Lime: new board (mali) Francois Perrad
2015-06-28 13:33 ` [Buildroot] [V4 0/2] A20-OLinuXino-Lime: new board Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=559050F1.1030101@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox