From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/24 v4] manual: document dependencies on atomic operations
Date: Sun, 17 Aug 2014 15:15:28 +0200 [thread overview]
Message-ID: <20140817131527.GE5274@free.fr> (raw)
In-Reply-To: <5dc49087-92a9-4ec1-a145-bcc77ecbad46@email.android.com>
Thomas, All,
On 2014-08-17 15:01 +0200, Thomas De Schampheleire spake thusly:
> "Yann E. MORIN" <yann.morin.1998@free.fr> schreef:
> >From: Anton Kolesov <anton.kolesov@synopsys.com>
> >
> >Add atomic operations to the list of generic dependencies.
> >
> >Since this is an architecture option, there is no comment string to be
> >added.
> >
> >Signed-off-by: Anton Kolesov <Anton.Kolesov@synopsys.com>
> >[yann.morin.1998 at free.fr: use the new arch-option; remove comment string]
> >Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >---
> > docs/manual/adding-packages-directory.txt | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> >diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
> >index 93e6a3e..40a81d5 100644
> >--- a/docs/manual/adding-packages-directory.txt
> >+++ b/docs/manual/adding-packages-directory.txt
> >@@ -219,6 +219,10 @@ use in the comment.
> > ** Dependency symbol: +BR2_USE_MMU+
> > ** Comment string: no comment to be added
> >
> >+* Atomic operations
> >+** Dependency symbol: +BR2_ARCH_HAS_ATOMICS+
> >+** Comment string: no comment to be added
> >+
>
> Should we provide a brief explanation, reference, or
> name of these functions to make it a bit clearer what
> is meant with 'atomic operations'?
Well, the atomics are all named differently in different architectures.
For example, armv6+ has LDREX and STREX (amon others):
http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dht0008a/ch01s02s01.html
While on x86, I don't think there are corresponding instructions, but
you can prefix some intructions with the LOCK prefix to achieve a
similar result.
So, I would not know what to put in here. Also, we do not explain what
the other options are (like MMU, for example). Why would we do that for
this specific option, and not others?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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-08-17 13:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-17 12:49 [Buildroot] [PATCH 0/24 v4] arch: move atomics to arch, not toolchain (branch yem/atomics) Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 01/24 v4] arch: add an option to specify if the arch has atomic ops Yann E. MORIN
2014-08-17 12:55 ` Thomas De Schampheleire
2014-08-17 12:57 ` Thomas Petazzoni
2014-08-17 13:04 ` Thomas De Schampheleire
2014-08-17 13:06 ` Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 02/24 v4] package/icu: use the new ARCH_HAS_ATOMICS as dependency Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 03/24 v4] package/libtorrent: " Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 04/24 v4] package/jack2: " Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 05/24 v4] package/thrift: " Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 06/24 v4] toolchain: drop the now-unused old BR2_TOOLCHAIN_HAS_ATOMIC_INTRINSICS Yann E. MORIN
2014-08-17 12:48 ` [Buildroot] [PATCH 07/24 v4] manual: document dependencies on atomic operations Yann E. MORIN
2014-08-17 13:01 ` Thomas De Schampheleire
2014-08-17 13:15 ` Yann E. MORIN [this message]
2014-08-17 13:25 ` Thomas De Schampheleire
2014-08-17 14:20 ` Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 08/24 v4] cairo: add dependency " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 09/24 v4] pulseaudio: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 10/24 v4] libftdi: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 11/24 v4] msgpack: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 12/24 v4] arch/arm: always has atomic ops Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 13/24 v4] arch/avr32: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 14/24 v4] arch/bfin: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 15/24 v4] arch/m68k: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 16/24 v4] arch/microblaze: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 17/24 v4] arch/mips: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 18/24 v4] arch/nios2: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 19/24 v4] arch/powerpc: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 20/24 v4] arch/sh: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 21/24 v4] arch/sparc: " Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 22/24 v4] arch/x86: all x86 but i386 has atomics operations Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 23/24 v4] arch/xtensa: always has atomic ops Yann E. MORIN
2014-08-17 12:49 ` [Buildroot] [PATCH 24/24 v4] arch: remove no-longer default on atomics option Yann E. MORIN
2014-08-17 13:03 ` Thomas De Schampheleire
2014-08-17 13:24 ` Yann E. MORIN
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=20140817131527.GE5274@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