From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] arc: add explicit selection of CPU templates ARC 750D and ARC770D
Date: Sat, 1 Nov 2014 20:55:31 +0100 [thread overview]
Message-ID: <20141101195531.GI10189@free.fr> (raw)
In-Reply-To: <1414677449-15937-2-git-send-email-abrodkin@synopsys.com>
Alexey, All,
On 2014-10-30 16:57 +0300, Alexey Brodkin spake thusly:
> This separation allows to specify unique options and features for each
> CPU.
>
> For example ARC 770D has LLOCK/SCOND instructions built-in by default.
"built-in by default": does that mean some cores might not have atomics?
Does it make sense to disable atomics for 770D at all, or should they
always be enabled?
If it makes sense to disable atomics for 770D, then this code has my:
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
However, if it does not make sense to disable atomics for 770D, then we
should do it a little bit differently, like (untested):
choice
bool "Target CPU"
config BR2_arc750d
bool "ARC 750D"
select BR2_ARC_MAYBE_ATOMIC_EXT
config BR2_arc770d
bool "ARC 770D"
select BR2_ARC_ATOMIC_EXT
endchoice
config BR2_ARC_MAYBE_ATOMIC_EXT
bool
config BR2_ARC_ATOMIC_EXT
bool
prompt "Atomic extension (LLOCK/SCOND instructions)" if BR2_ARC_MAYBE_ATOMICS
config BR2_ARCH_HAS_ATOMICS
default y if BR2_ARC_ATOMIC_EXT
Regards,
Yann E. MORIN.
> Also this new scheme simplifies selection of proper configuration for
> users - preconfigured options now match templates for ARC CPUs.
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Anton Kolesov <akolesov@synopsys.com>
> ---
> arch/Config.in.arc | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/arch/Config.in.arc b/arch/Config.in.arc
> index fcb5d7d..b31b141 100644
> --- a/arch/Config.in.arc
> +++ b/arch/Config.in.arc
> @@ -1,6 +1,22 @@
> -# Choise of atomic instructions presence
> +choice
> + prompt "Target CPU"
> + depends on BR2_arc
> + default BR2_arc770d
> + help
> + Specific CPU to use
> +
> +config BR2_arc750d
> + bool "ARC 750D"
> +
> +config BR2_arc770d
> + bool "ARC 770D"
> +
> +endchoice
> +
> +# Choice of atomic instructions presence
> config BR2_ARC_ATOMIC_EXT
> bool "Atomic extension (LLOCK/SCOND instructions)"
> + default y if BR2_arc770d
>
> config BR2_ARCH_HAS_ATOMICS
> default y if BR2_ARC_ATOMIC_EXT
> @@ -18,4 +34,5 @@ config BR2_ENDIAN
> default "BIG" if BR2_arceb
>
> config BR2_GCC_TARGET_CPU
> - default "arc700"
> + default "arc700" if BR2_arc750d
> + default "arc700" if BR2_arc770d
> --
> 1.9.3
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-11-01 19:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 13:57 [Buildroot] [PATCH 0/3] arc: introduce more CPU versions for selection Alexey Brodkin
2014-10-30 13:57 ` [Buildroot] [PATCH 1/3] arc: add explicit selection of CPU templates ARC 750D and ARC770D Alexey Brodkin
2014-11-01 19:55 ` Yann E. MORIN [this message]
2014-11-01 22:25 ` Yann E. MORIN
2014-11-02 21:24 ` Peter Korsgaard
2014-10-30 13:57 ` [Buildroot] [PATCH 2/3] uclibc: add explicit setup of ARC-specific options Alexey Brodkin
2014-11-01 19:28 ` Yann E. MORIN
2014-11-02 21:24 ` Peter Korsgaard
2014-10-30 13:57 ` [Buildroot] [PATCH 3/3] arc: add support of ARC HS38 core Alexey Brodkin
2014-11-01 21:47 ` Yann E. MORIN
2014-11-01 22:26 ` Yann E. MORIN
2014-11-02 21:25 ` Peter Korsgaard
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=20141101195531.GI10189@free.fr \
--to=yann.morin.1998@free.fr \
--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